You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This page describes the release process of Apache Flink.

 

Verifying a Release Candidate

  • Check if checksums and GPG files match the corresponding release files
  • Check if the source archive contains any binaries

 

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 ./create_release_files.sh
  • Usually the create_release_files.sh script needs to be adopted a bit depending on the used linux distribution
  • Close the staging repository in repository.apache.org (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 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

  • 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.
  • Update Flink website with updated download URLs and Maven artifacts. Manually update the index.html of the website.
  • Publish release announcement blog post
  • Email to dev, news, user  AT flink.a.o; also announce AT apache.
  • No labels