Page History

...

1. Build the release and run unit tests:

   Code Block
   umask 0022 ant clean ant test ant -Dhcatalog.version=X.Y.Z-incubating -Dforrest.home=<Forrest installation dir> tarsrc-release

2. Test the tar file by unpacking the release and
   1. building hcatalog.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-incubating.tar.gz > hcatalog-X.Y.Z-incubating.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/incubator/hcatalog/branches/branch-X.Y.Z/KEYS https://svn.apache.org/repos/asf/incubator/hcatalog/trunk/KEYS

   4. Upload updated KEYS to Apache.

      Code Block
      scp KEYS people.apache.org:/www/www.apache.org/dist/incubator/hcatalog/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 hcatalog-X.Y.Z-incubating.tar.gz.asc --detach-sig hcatalog-X.Y.Z-incubating.tar.gz

6. Verify gpg signature.

   Code Block
   gpg --import KEYS (if necessarily) gpg --verify hcatalog-X.Y.Z-incubating.tar.gz.asc hcatalog-X.Y.Z-incubating.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-incubating-candidate-0 scp -p hcatalog-X.Y.Z-incubating.tar.gz* people.apache.org:public_html/hcatalog-X.Y.Z-incubating-candidate-0 cd .. scp RELEASE_NOTES.txt people.apache.org:public_html/hcatalog-X.Y.Z-incubating-candidate-0 scp rat_report people.apache.org:public_html/hcatalog-X.Y.Z-incubating-candidate-0

   The rat_report is the report generated in the Updating Release Branch section above.
8. Call a release vote for the Podling PMC (PPMC). This vote must receive a minimum of 3 PPMC members +1s, and more +1s than -1s. 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-incubating (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-incubating (candidate 0) Hi, I have created a candidate build for HCatalog 0.1.0-incubating. This is the initial release of HCatalog. Keys used to sign the release are available at http://svn.apache.org/viewvc/incubator/hcatalog/trunk/KEYS?view=markup. Please download, test, and try it out: http://people.apache.org/~you/hcatalog-0.1.0-incubating-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

9. If the PPMC approves the release, call an Incubator PMC (IPMC) vote. This vote must receive a minimum of 3 IPMC member +1s, and more +1s than -1s. The email sent should look similar.

...