...
- Decide to release
- Prepare for the release
- Build a release candidate
- Vote on the release candidate
- If necessary, fix any issues and go back to step 3.
- Finalize the release
- Promote the release
- Update flink-shaded dependencies in other repositories
Decide to release
Deciding to release and selecting a Release Manager is the first step of the release process. This is a consensus-based decision of the entire community.
...
- Website pull request to list the release merged
- Release recorded in reporter.apache.org.
- Release announced on the dev@ mailing list.
- Prepare for the next development iteration by creating/merging a PR bumping the flink-shaded version (e.g. 725c0caf3ab)
Update flink-shaded dependency in other repositories
Repositories that have the flink-shaded dependency included and need updates (flink-shaded
and shaded dependency versions):
Improve the process
It is important that we improve the release processes over time. Once you’ve finished the release, please take a step back and look what areas of this process and be improved. Perhaps some part of the process can be simplified. Perhaps parts of this guide can be clarified.
...