Page History

...

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. 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

5. 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

6. 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

7. Login to the Apache Nexus server and "close" the staged repository. This makes the artifacts available at a temporary URL.
8. Call a release vote on dev at hive.apache.org.

...