Page History

...

1. Ensure that the "Release Manager" has a GPG key or generate a new one, e.g., using gpg --gen-key. Make sure to generate a RSA key with at least 4096 bits.

   Info
   icon false
   smarella:~/myriad$ gpg --gen-key .... Please select what kind of key you want: (1) RSA and RSA (default) (2) DSA and Elgamal (3) DSA (sign only) (4) RSA (sign only) Your selection? 1 RSA keys may be between 1024 and 4096 bits long. What keysize do you want? (2048) 4096 Requested keysize is 4096 bits ....

2. Add your GPG public key to the Apache Myriad dist repository in the KEYS file.

   Info
   icon false
   a) Fetch the svn repository: svn co https://dist.apache.org/repos/dist/dev/incubator/myriad/ b) Append your public key using one of methods described in KEYS: (gpg --list-sigs <your name> && gpg --armor --export <your name>) >> KEYS c) Push the commit: svn ci

3. Submit your GPG public key to a keyserver, e.g. MIT PGP Public Key Server.

4. Add your GPG fingerprint to your Apache account.

   Info
   icon false
   smarella:~/myriad$ gpg --list-keys --fingerprint /home/smarella/.gnupg/pubring.gpg --------------------------------- pub 4096R/B26811FB 2015-10-20 Key fingerprint = 5FB7 1C05 A37A 7818 BA60 915E 095F 054C B268 11FB uid Santosh Marella <marella@gmail.com> sub 4096R/5E42CE0D 2015-10-20

Just before a release

1. Ensure all the outstanding PRs are merged.
2. (Re)Read Apache's Release Check List.
3. It is recommended to download the latest master and run Apache RAT tool on the to-be-released code base to fix any missing Apache License headers.

...