CLONE - CLONE - 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:

   $ svn checkout https://dist.apache.org/repos/dist/dev/flink --depth=immediates
   

2. Make a directory for the new release and copy all the artifacts (Flink source/binary distributions, hashes, GPG signatures and the python subdirectory) into that newly created directory:

   $ mkdir flink/flink-${RELEASE_VERSION}-rc${RC_NUM}
   $ mv <flink-dir>/tools/releasing/release/* flink/flink-${RELEASE_VERSION}-rc${RC_NUM}
   

3. Add and commit all the files.

   $ cd flink
   flink $ svn add flink-${RELEASE_VERSION}-rc${RC_NUM}
   flink $ svn commit -m "Add flink-${RELEASE_VERSION}-rc${RC_NUM}"
   

4. Verify that files are present under https://dist.apache.org/repos/dist/dev/flink.
5. Push the release tag if not done already (the following command assumes to be called from within the apache/flink checkout):

   $ git push <remote> refs/tags/release-${RELEASE_VERSION}-rc${RC_NUM}
   

Expectations

• Maven artifacts deployed to the staging repository of repository.apache.org
• Source distribution deployed to the dev repository of dist.apache.org
• Check hashes (e.g. shasum -c *.sha512)
• Check signatures (e.g. gpg --verify flink-1.2.3-source-release.tar.gz.asc flink-1.2.3-source-release.tar.gz)
• grep for legal headers in each file.
• If time allows check the NOTICE files of the modules whose dependencies have been changed in this release in advance, since the license issues from time to time pop up during voting. See Verifying a Flink Release "Checking License" section.