Page History

...

Now, add your Apache GPG key to the Flink’s KEYS file in the release repository at dist.apache.org. Follow the instructions listed at the top of these files. (Note: Only PMC members have write access to the release repository. If you end up getting 403 errors ask on the mailing list for assistance.) PMC member can refer following scripts to add your Apache GPG key to the KEYS in the release repository.

svn co https://dist.apache.org/repos/dist/release/flink flink-dist-release-repo
cd flink-dist-release-repo
(gpg --list-sigs <YOUR_KEY_ID> && gpg --armor --export <YOUR_KEY_ID>) >> KEYS
svn ci -m "[flink] Add <YOUR_NAME>'s public key"

Configure git to use this key when signing code by giving it your key ID, as follows:

...

RELEASE_CANDIDATE=$RC_NUM tools/releasing/create_release_branch.sh

Update branch version:

$ OLD_VERSION=$CURRENT_SNAPSHOT_VERSION NEW_VERSION=$RELEASE_VERSION tools/releasing/update_branch_version.sh

Tag the release commit:

git tag -s ${TAG} -m "${TAG}"

...

First, we build the source release:

$ OLD_VERSION=$CURRENT_SNAPSHOT_VERSION NEW_VERSION=$RELEASE_VERSION tools/releasing/update_branch_version.sh
$ RELEASE_VERSION=$RELEASE_VERSION tools/releasing/create_source_release.sh

...

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

Finally, we create the binary convenience release files:

tools $ RELEASE_VERSION=$RELEASE_VERSION releasing/create_binary_release.sh

Stage source and binary releases on 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
   language bash
   svn checkout https://dist.apache.org/repos/dist/dev/flink --depth=immediatesdepth=immediates

   
   

2. Make a directory for the new release:

   Code Block
   language bash
   mkdir flink/flink-table-store-${RELEASE_VERSION}-rc${RC_NUM}

   Copy source distributions, hashes, and GPG signature:

   Code Block
   mv <flink-table-store-dir>/release/*

   Make a directory for the new release:

   Code Block
   language bash
   mkdir flink/flink-table-store-${RELEASE_VERSION}-rc${RC_NUM}

   Copy

   all release

   binary distributions,

   hashes,

   and

   GPG

   signature:

   Code Block
   mv <flink-table-store-dir>/tools/releasing/release/* flink/flink-table-store-${RELEASE_VERSION}-rc${RC_NUM}

   
   

3. Add and commit all the files.

   Code Block
   language bash
   cd flink svn add flink-table-store-${RELEASE_VERSION}-rc${RC_NUM} svn commit -m "Apache Flink Table Store, version ${RELEASE_VERSION}, release candidate ${RC_NUM}"

   
   

4. Verify that files are present

...

Deploy artifacts to Maven Central Repository

Use the Apache Nexus repository to release the staged binary artifacts to the Maven Central repository. In the Staging Repositories section, find the relevant release candidate orgapacheflink-XXX entry and click Release. Drop all other release candidates that are not being released.

...

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

   Code Block
   language bash
   svn checkout https://dist.apache.org/repos/dist/release/flink --depth=immediates cd flink

   
   

2. Remove files for outdated releases and commit the changes.

   Code Block
   language bash
   svn remove flink-table-store-<version_to_remove> svn commit -m "Remove old release for Apache Flink Table Store ${RELEASE_VERSION_MAJOR}"

   
   

3. Verify that files are removed

...