Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Once the release has been finalized, the last step of the process is to promote the release within the project and beyond. Please wait for 24h after finalizing the release in accordance with the ASF release policy.

Update japicmp configuration

Update the japicmp reference version and enable API compatibility checks for @PublicEvolving  APIs on the corresponding SNAPSHOT branch.

For new major release (x.y.0), run the same command also on the master branch for updating the japicmp reference version.

Code Block
languagebash
tools $ NEW_VERSION=$RELEASE_VERSION releasing/update_japicmp_configuration.sh
tools $ cd ..
$ git add *
$ git commit -m "Update japicmp configuration for $RELEASE_VERSION"

Merge website pull request

...

  1. Website pull request to list the release merged
  2. Release announced on the user@ mailing list.
  3. Blog post published, if applicable.
  4. Release recorded in reporter.apache.org.
  5. Release announced on social media.
  6. Completion declared on the dev@ mailing list.
  7. Update Homebrew: https://docs.brew.sh/How-To-Open-a-Homebrew-Pull-Request
  8. Update quickstart scripts in flink-web, under the q/ directory
  9. Updated the japicmp configuration
    • corresponding SNAPSHOT branch japicmp reference version set to the just released version, and API compatibiltity checks for @PublicEvolving  was enabled
    • (major only) master branch japicmp reference version set
    Update the reference Flink version in the japicmp maven plugin for the API stability checks
    • to the just released version
    .
  10. Update the list of previous version in docs/_config.yml on the master branch.
  11. Set show_outdated_warning: true in docs/_config.yml in the branch of the previous Flink version
  12. Update stable and master alias in flink.conf found in https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects
  13. Update docs to "stable" in docs/_config.yml in the branch of the just-released version:
  14. (major/minor only) Update migration tests in master to cover migration from new version: (search for usages of MigrationVersion)
    • AbstractOperatorRestoreTestBase
    • CEPMigrationTest
    • BucketingSinkMigrationTest
    • FlinkKafkaConsumerBaseMigrationTest
    • ContinuousFileProcessingMigrationTest
    • WindowOperatorMigrationTest
    • StatefulJobSavepointMigrationITCase
    • StatefulJobWBroadcastStateMigrationITCase

...