Page History

...

1. Build the release and run unit tests:

   Code Block
   ant clean ant test ant -Dversion=X.Y.Z -Dforrest.home=<Forrest installation dir> tar

2. Test the tar file by unpacking the release and
   1. building pig.jar: ant
   2. running unit tests ant test
3. Generate the MD5 checksum of the release file:

   Code Block
   cd build md5sum hcatalog-X.Y.Z.tar.gz > hcatalog-X.Y.Z.tar.gz.md5

4. If you do not have a gpg key pair, do the following steps:
   1. Generating key pair using the following command. You can simply accept all default settings and give your name, email and Passphase.

      Code Block
      gpg --gen-key

   2. Export your public key.

      Code Block
      gpg --armor --output pubkey.txt --export 'Your Name'

   3. Open pubkey.txt, copy the full text and append it to the following files by pasting, then commit these changes:

      Code Block
      https://svn.apache.org/repos/asf/pig/branches/branch-X.Y.Z/KEYS https://svn.apache.org/repos/asf/pig/trunk/KEYS

   4. Upload updated KEYS to Apache.

      Code Block
      scp KEYS people.apache.org:/www/www.apache.org/dist/pig/KEYS

   5. Export your private key, keep it with you.

      Code Block
      gpg --export-secret-key -a "Your Name" > private.key

5. Sign the release (see Step-By-Step Guide to Mirroring Releases for more information).

   Code Block
   gpg --armor --output pig-X.Y.Z.tar.gz.asc --detach-sig pig-X.Y.Z.tar.gz

6. Verify gpg signature.

   Code Block
   gpg --import KEYS (if necessarily) gpg --verify pig-X.Y.Z.tar.gz.asc pig-X.Y.Z.tar.gz

7. Copy release files to a public place (usually into public_html in your home directory):

   Code Block
   ssh people.apache.org mkdir public_html/hcatalog-X.Y.Z-candidate-0 scp -p hcatalog-X.Y.Z.tar.gz* people.apache.org:public_html/hcatalog-X.Y.Z-candidate-0 cd .. scp RELEASE_NOTES.txt people.apache.org:public_html/hcatalog-X.Y.Z-candidate-0 scp rat_report people.apache.org:public_html/hcatalog-X.Y.Z-candidate-0

   The rat_report is the report generated in the Updating Release Branch section above.
8. Call a release vote. The email should be sent to hcatalog-user@incubator.apache.org. The mail should:

   • Wiki Markup
     have a subject line "\[VOTE\] Release HCatalog X.Y.Z (candidate a)" where X.Y.Z is the version number and {{a}} is the candidate number for this release.

   • State what is new in this release.
   • Tell where the keys used to sign the release can be found.
   • State where the release, md5 signature, gpg signature, and rat report can be found.
   • Request that users and developers download it, test it, and vote.
   • State when the vote closes. The vote must remain open for at least 72 hours. It can be longer at your discretion (e.g. around major holidays).
     Here is a sample email:

     Code Block

     Subject: [VOTE] Release HCatalog 0.1.0 (candidate 0) Hi, I have created a candidate build for HCatalog 0.1.0. This is the initial release of HCatalog. Keys used to sign the release are available at http://svn.apache.org/viewvc/pig/trunk/KEYS?view=markup. Please download, test, and try it out: http://people.apache.org/~you/hcatalog-0.1.0-candidate-0 The release, md5 signature, gpg signature, and rat report can all be found at the above address. Should we release this? Vote closes on Thursday, June 16th. Me

...