Currently, this is the old text from Creating a Flink Release. Slated to be updated soon.

Creating a release candidate

• Read and understand: http://www.apache.org/dev/release-publishing.html
• Read http://www.apache.org/dev/release-signing.html and create yourself a PGP key

• run the ./tools/create_release_files.sh script from the Flink repo, with the following parameters: (the call below as used to create RC1 of Flink 0.8.1

   

  sonatype_user=YOURAPACHEID sonatype_pw=YOURAPACHEIDPASSWORD NEW_VERSION=0.8.1 RELEASE_CANDIDATE="rc1" RELEASE_BRANCH=release-0.8 OLD_VERSION=0.8-SNAPSHOT USER_NAME=YOURAPACHEID GPG_PASSPHRASE=YOURGPGPASSPHRASE GPG_KEY=YOURGPGKEY  GIT_AUTHOR="`git config --get user.name` <`git config --get user.email`>" ./create_release_files.sh

   

  Note: Make sure to run the ./tools/create_release_files.sh script (in particular the "mvn deploy" call) with Java 8 to release the java8 module to mvn central as well.

• Don't forget to update the documentation configuration to the new release version
• Usually the create_release_files.sh script needs to be adopted a bit depending on the used linux distribution
• Open repository.apache.org, login in with your Apache user, and close the staging repository you created (DO NOT PRESS "RELEASE"!)
• Check that the release files are located in your people.apache.org home directory
• go to the ./tools/flink directory and push the release commit to release-x.y.z-rcn branch. (DO NOT CHANGE THE COMMIT OR COMMIT THE LOCAL CHANGES, the release commit has already been created.)
• Send the VOTE mail to the dev@flink.a.o list, containing the release commit hash, the link to your people.apache.org and to the staging repository.

Releasing a Release Candidate

• Create a git tag for the release
• Upload binaries to svn repo at: https://dist.apache.org/repos/dist/release/flink (sync needs 24 hours)
• Release staging repository https://repository.apache.org/ to Maven Central.
  • After this step, add the release to the Apache Report Helper at https://reporter.apache.org/addrelease.html?flink (if you are not a PMC member, ask one for help)
• Update Flink website with updated download URLs and Maven artifacts (by updating the _config.yml)
  • Don't forget to update the quickstarts versions
• Update list of contributors wiki page with new contributors in the release
• Update Homebrew: https://gist.github.com/EronWright/b62bd3b192a15be4c200a2542f7c9376
• Publish release announcement blog post
• Email to dev, news, user  AT flink.a.o; also announce AT apache.
• Update the reference Flink version in the japicmp maven plugin for the API stability checks to the just released major version.