THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
--------------------------------------------------------------------------------------------------------
Review and update documentation
There are a few pages in the documentation that need to be reviewed and updated for each release.
- Ensure that there exists a release notes page for each non-bugfix release (e.g., 1.5.0) in
./docs/release-notes/, that it is up-to-date, and linked from the start page of the documentation. - Upgrading Applications and Flink Versions: https://ci.apache.org/projects/flink/flink-docs-master/ops/upgrading.html
- please extend this list.
Unless the pages have not been updated before, please create a JIRA ticket and mark it as release blocker.
--------------------------------------------------------------------------------------------------------
...
- Release Manager’s GPG key is published to dist.apache.org
- Release Manager’s GPG key is configured in git configuration
- Release Manager has org.apache.hudi listed under Staging Profiles in Nexus
- Release Manager’s Nexus User Token is configured in settings.xml
- JIRA release item for the subsequent release has been created
- All test failures from branch verification have associated JIRA issues
- There are no release blocking JIRA issues
- Release branch has been created
- Release Notes have been audited and added to RELEASE_NOTES.md
- // Add an entry to documentation ?
Build a release candidate
...