...
- 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.
...
- Create the source release archive
- Deploy jar artifacts to the Apache Nexus Repository, which is the staging area for deploying the jars to Maven Central
- Note: Please do not use VPN or change your IP address when stage artifacts to Apache Nexus Repository, it may lead to multiple staging repositories which is unexpected.
Code Block | ||
---|---|---|
| ||
# tag release commit git tag -s ${TAG} -m "${TAG}" # create source release cd ${FLINK_SHADED_DIR}/tools RELEASE_VERSION=$RELEASE_VERSION releasing/create_source_release.sh # stage maven artifacts cd ${FLINK_SHADED_DIR}/tools releasing/deploy_staging_jars.sh cd ${FLINK_SHADED_DIR} |
...
- 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.
...