Page History

...

1. Decide to release
2. Prepare for the release
3. Build a release candidate
4. Vote on the release candidate
5. If necessary, fix any issues and go back to step 3.
6. Finalize the release
7. Promote the release
8. 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.

...

1. Website pull request to list the release merged
2. Release recorded in reporter.apache.org.
3. Release announced on the dev@ mailing list.
4. 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:

• apache/flink:pom.xml (not only the <flink.shaded.version/>  property but also the dependencies have to be updated)
• apache/flink-benchmarks:pom.xml

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.

...