Once your Apache ID has been set up you can configure your account and add ssh keys and setup an email forwarding address at
Additional instructions for setting up your new committer email can be found at
http://www.apache.org/dev/user-email.html
The recommended setup is to configure all services (mailing lists, JIRA, ReviewBoard) to send emails to your @apache.org email address.
The following will guide you through the steps to create a release candidate, vote, and finally an official Apache Aurora release. Before starting your gpg key should be in the KEYS file and you must have access to commit to the dist.a.o repositories.
Ensure that all issues resolved for this release candidate are tagged with the correct Fix Version in Jira, the changelog script will use this to generate the CHANGELOG in step #2.
Create a release candidate. This will automatically update the CHANGELOG and commit it, create a branch and update the current version within the trunk. To create a minor version update and publish it run
./build-support/release/release-candidate -l m -p
Update, if necessary, the draft email created from the release-candidate script in step #2 and send the [VOTE] email to the dev@ and private@ mailing lists. You can verify the release signature and checksums by running
./build-support/release/verify-release-candidate
Wait for the vote to complete. If the vote fails address any issues and go back to step #1 and run again, this time you will use the -r flag to increment the release candidate version. This will automatically clean up the release candidate rc0 branch and source distribution.
./build-support/release/release-candidate -l m -r 1 -p
Once the vote has successfully passed create the release
./build-support/release/release
Update the draft email created fom the release script in step #5 to include the Apache ID's for all binding votes and send the [RESULT][VOTE] email to the dev@ and private@ mailing lists.