Page History

...

1. Bulk update Jira to unassign from this release all issues that are open non-blockers and send follow-up notification to the developer list that this was done.
2. run 'ant rat' to and examine the generated report for any files, specially .java files should be having apache license headers. Add the license header to any file that is missing it (open a jira and submit a patch).
3. Update copyright date in NOTICE . If the components mentioned in them have updated version, you would need to update the copyright dates for those. (Thejas comment: It sounds like entries are needed in NOTICE only if the license requires such attribution . See - http://www.apache.org/legal/src-headers.html#notice^{Image Removed})

Branching

Skip this section if this is NOT the first release in a series (i.e. release X.Y.0).

...

1. Build the release (binary and source versions) after running unit tests. Note that this will generate MD5 checksum files automatically.

   No Format
   % ant -Dversion=X.Y.Z clean test tar binary

2. Verify that the MD5 checksums are valid:

   No Format
   % md5sum -c hive-X.Y.Z.tar.gz.md5 hive-X.Y.Z.tar.gz: OK % md5sum -c hive-X.Y.Z-bin.tar.gz.md5 hive-X.Y.Z-bin.tar.gz: OK

3. Check that release file looks ok - e.g. install it and run examples from tutorial.
4. Setup your PGP keys for signing the release, if you don't have it
   1. See http://www.apache.org/dev/release-signing.html^{Image Removed}
5. Sign the release (see Step-By-Step Guide to Mirroring Releases for more information).

   No Format
   % gpg --armor --output hive-X.Y.Z.tar.gz.asc --detach-sig hive-X.Y.Z.tar.gz % gpg --armor --output hive-X.Y.Z-bin.tar.gz.asc --detach-sig hive-X.Y.Z-bin.tar.gz

6. Copy release files to a public place.

   No Format
   % ssh people.apache.org mkdir public_html/hive-X.Y.Z-candidate-0 % scp -p hive-X.Y.Z*.tar.gz* people.apache.org:public_html/hive-X.Y.Z-candidate-0

7. Publish Maven artifacts to the Apache staging repository:

   No Format
   % ant -Dversion=X.Y.Z -Dmvn.publish.repo=staging maven-build % ant -Dversion=X.Y.Z -Dmvn.publish.repo=staging maven-publish

8. Login to the Apache Nexus server and "close" the staged repository. This makes the artifacts available at a temporary URL.

Voting and verifying the artifacts

1. Call a release vote on dev at hive.apache.org.

   No Format

   From: you@apache.org To: dev@hive.apache.org Subject: [VOTE] Apache Hive X.Y.Z Release Candidate N Apache Hive X.Y.Z Release Candidate N is available here: http://people.apache.org/~you/hive-X.Y.Z-candidate-N Maven artifacts are available here: https://repository.apache.org/content/repositories/orgapachehive-121/ Source tag for RCN is at: http://svn.apache.org/viewvc/hive/tags/release-X.Y.Z-RCN/ Voting will conclude in 72 hours. Hive PMC Members: Please test and vote. Thanks.

Verifying the release candidate

1. verifying the PGP signature

   No Format
   #get the hive committers keys file wget http://www.apache.org/dist/hive/KEYS or wget https://people.apache.org/keys/group/hive.asc gpg --import <keys file> gpg --verify hive-X.Y.Z-bin.tar.gz.asc hive-X.Y.Z-bin.tar.gz gpg --verify hive-X.Y.Z.tar.gz.asc hive-X.Y.Z.tar.gz

2. verifying the md4 checksum
   See the step under building

Publishing

Once three PMC members have voted for a release, it may be published.

...