justinmclean commented on code in PR #159: URL: https://github.com/apache/otava/pull/159#discussion_r3255787004
########## docs/RELEASE.md: ########## @@ -90,8 +123,12 @@ Here, the key ID is the 8-digit hex string in the pub line: 845E6689. Now, add your Apache GPG key to the Otava's KEYS file in the [release](https://dist.apache.org/repos/dist/release/incubator/otava/KEYS) repository at [dist.apache.org](https://dist.apache.org/repos/dist/). 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 members can refer to the following scripts to add your Apache GPG key to the KEYS in the release repository. ```bash -svn co https://dist.apache.org/repos/dist/release/incubator/otava otava-dist-release-repo -cd otava-dist-release-repo +# Checkout both the dev and release repositories up front +svn co https://dist.apache.org/repos/dist/dev/incubator/otava $OTAVA_SVN_DEV +svn co https://dist.apache.org/repos/dist/release/incubator/otava $OTAVA_SVN_REL + +# For GPG key we always use the dist/release repo: +cd $OTAVA_SVN_REL (gpg --list-sigs <YOUR_KEY_ID> && gpg --armor --export <YOUR_KEY_ID>) >> KEYS svn ci -m "[otava] Add <YOUR_NAME>'s public key" ``` Review Comment: this only needs to be done once per release manager -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
