Versions Compared

Key

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

...

Review all staged artifacts (https://repository.apache.org/). They should contain all relevant parts for each module, including pom.xml, jar, test jar, source, test source, javadoc, etc. Carefully review any new artifacts.

Close the staging repository on Apache Nexus. When prompted for a description, enter “Apache Flink, version X, release candidate Y”.

Stage source release on dist.apache.org

Copy the source release to the dev repository of dist.apache.org.

...

Finally, we create the binary convenience release files:

Code Block
languagebash
tools 

...

Make a directory for the new release:

$ RELEASE_VERSION=$RELEASE_VERSION releasing/create_binary_release.sh

If you want to run this step in parallel on a remote machine could have to make the release commit available there (for example by pushing to a repository). This is important: the commit inside the binary builds has to match the commit of the source builds and the tagged release commit. When building remotely, you can skip gpg signing by also setting  GPG_SKIP=true. You would then sign the files manually after downloading them to your machine:

Code Block
languagebash
$ for f in flink-*-bin*.tgz; gpg --armor --detach-sig $f; end

 

Stage source and binary releases on dist.apache.org

Copy the source release to the dev repository of dist.apache.org.

  1. If you have not already, check out the Flink section of the dev repository on dist.apache.org via Subversion. In a fresh directory:

    Code Block
    languagebash
     svn co https://dist.apache.org/repos/dist/dev/flink
  2. Make a directory for the new release:

    mkdir flink/${VERSION} cd flink/${VERSION}
    Copy Flink source distribution, hashes, and GPG signature:
    Code Block
    languagebash
    cp ${FLINK_ROOT}/target/flink-${VERSION}-source-release.tar.gz .
    cp ${FLINK_ROOT}/target/flink-${VERSION}-source-release.tar.gz.asc .

    Create hashes for source files 

    Code Block
    languagebash
    sha512sum mkdir flink-/${VERSION}-source-release.tar.gz >
     cd flink-/${VERSION}-source-release.tar.gz.sha
    md5sum flink-${VERSION}-source-release.tar.gz > flink-${VERSION}-source-release.tar.gz.md5
    
  3. Add and commit all the files.

    Code Block
    languagebash
     svn add flink/${VERSION}
     svn commit
  4. Verify that files are present.
  5. Copy Flink source/binary distributions, hashes, and GPG signature:
  6. Add and commit all the files.

    Code Block
    languagebash
     svn add flink/${VERSION}
     svn commit
  7. Verify that files are present.

Info

Alternatively, you can stage the source and binary releases on home.apache.org, i.e. sftp <apache-id>@home.apache.org, which would be available at http://people.apache.org/~<apache-id>. You would store the files in a sub folder of public_html that has the version and RC encoded, i.e. flink-1.3.2-rc2.

 

Propose a pull request for website updates

...