Setting up the signing keys
Before you do a release you'll need a signing key that is registered with apache. If you already have one, you can skip this section. Otherwise, here are the steps to do:
- use gpg2 --gen-key to generate a new key. Make sure that the key size is 4096 bits, the key doesn't expire, and use CODE SIGNING KEY for the comment.
- Now you need to register your key at http://pgp.mit.edu/ using the output of gpg --armor --export <keyid>
- Add your key to the KEYS file:
- check out http://svn.apache.org/repos/asf/zookeeper/dist
- edit the KEYS file
- add the output of gpg2 --armor --fingerprint --list-sigs <keyid> and gpg2 --armor --export <keyid> to the file
- commit
Support is now available for pushing the jar artifacts to the Apache maven repository.
1) sign the jar/pom files using gpg
2) copy the jar/pom/etc... into the appropriate directory
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/hadoop/zookeeper/
full details here:http://www.apache.org/dev/repository-faq.html
the files are sync'd daily, and ivy finds it.
maven metadata files have to be updated manually
Smoke Tests
Before the release, run the following smoke tests (at least).
- Run unit tests on different hardwares: mac, windows, linux.