THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Follow Apache guidelines on setting up your GPG keys and ensure that your fingerprint is updated at id.apache.org.Also, append your keys to the KEYS file at https://dist.apache.org/repos/dist/release/tez/KEYS as well as the KEYS file at the top of the source tree.
Code Block |
---|
gpg --armor --fingerprint --list-sigs <keyid> gpg --armor --export <keyid> |
...
Code Block |
---|
gpg --keyserver pgp.mit.edu --send-key <keyid>
gpg --keyserver keyserver.ubuntu.com --send-key <keyid>
gpg --keyserver pool.sks-keyservers.net --send-key <keyid>
|
Adding PGP Keys to Tez source tree and distribution repository. KEYS file in tez distribution repository will be used for release verification in release candidate voting
Code Block | ||||
---|---|---|---|---|
| ||||
# Append PGP Key to KEYS file in https://gitbox.apache.org/repos/asf/tez.git
$ svn co https://dist.apache.org/repos/dist/release/tez/ tez-dist/
# copy KEYS file from gitbox tez/KEYS to tez-dist/KEYS and verify difference
$ svn diff
# Commit the changes (no jira required) with a useful message substituting apache user name as appropriate
$ svn ci -m "Add <apache user name> public key to KEYS file" |
Creating a Release Candidate
...