Release process.
Make sure it passes the apache rat tool.
mvn clean apache-rat:check
Sign the tarball
gpg2 --armor --output ambari-{release_number}-incubating.tar.gz.asc --detach-sig ambari-{release_number}-incubating.tar.gz gpg --print-mds ambari-{release_number}-incubating.tar.gz > ambari-{release_number}-incubating.tar.gz.mds
Upload the artifacts to your apache home:
The artifacts then need to be copied over to public_html/ambari-release-name-rc_i_/
Call for a vote on the ambari-dev mailing list with something like this:
I have created a ambari-** release candidate.
SVN source tag (r***)
http://svn.apache.org/repos/asf/incubator/ambari/branches/branch-{release_number}/
Staging site: http://people.apache.org/user_name/ambari-***
PGP release keys (signed using 8EE2F25C) http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x0DFF492D8EE2F25C
One can look into the issues fixed in this release at https://issues.apache.org/jira/**
Vote will be open for 72 hours.
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)
As soon as the vote passes in the incubator call for a vote with results on incubator general mailing list. Once the vote passes/fails in incubator general, send out an email with subject: RESULT VOTE Apache Ambari 1.2.0 rc0 on the general incubator mailing list.
Once the vote passes in the incubator copy the bits to the release artifact directory:
ssh people.apache.org cd /www/www.apache.org/dist/incubator/ambari/ mkdir ambari-{release_num} cp ~/public_html/ambari-{release}/* /www/www.apache.org/dist/incubator/ambari/ambari-{release_num}/