THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- 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> src-release
- Test the tar file by unpacking the release and
- building hcatalog.jar:
ant
- running unit tests
ant test
- building hcatalog.jar:
- . This builds a source release artifact, then builds a binary release from that source release, and runs unit tests. Auxiliary files such as MD5 checksums and the releaseaudit report are also generated by the release script. Generate the MD5 checksum of the release file:
Code Block cd buildFORREST_HOME=/path/to/apache/forrest \ md5sum hcatalog-HCAT_RELEASE_VERSION='X.Y.Z-incubating.tar.gz > hcatalog-X.Y.Z-incubating.tar.gz.md5' \ ./build-support/scripts/release.sh
- 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
- 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
- Copy release files to a public place (usually into public_html in your home directory):
TheCode 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
rat_report
is the report generated in the Updating Release Branch section above. - 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
- 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.
...