Release process.

Note: The firstrelease candidate is rc0. The following documented process assumes rc0, but replace it with the appropriate rc number as required.

Create a Release Tag from the release branch

svn copy https://svn.apache.org/repos/asf/incubator/ambari/branches/branch-x.y https://svn.apache.org/repos/asf/incubator/ambari/tags/release-x.y.z-rc0 -m "Ambari x.y.z Release Candidate"

Make sure it passes the apache rat tool.

...

The artifacts then need to be copied over to public_html/ambari-release-name-rc_i_rc0/

Call for a vote on the ambari-dev mailing list and CC general@incubator.apache.org with something like this:

...

https://svn.apache.org/repos/asf/incubator/ambari/tags/release-1x.2y.1z-rc0

Staging site: http://people.apache.org/user_name/ambari-***

...

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Once the vote passes/fails, send out an email with subject like "\[RESULT\] \[VOTE\] Apache Ambari

 x.

y.

z rc0" to general@incubator.apache.org and ambari-dev@incubator.apache.org.  For the vote to pass, 3 +1 votes are required from IPMC members.

After the vote passes:

Copy the bits to distribution folder for Apache Ambari:

ssh people.apache.org

cd /www/www.apache.org/dist/incubator/ambari/

mkdir ambari-{release_num}

cp ~/public_html/ambari-{release}/* ambari-{release_num}
ln -sf ambari-{release_num} stable

svn move https://svn.apache.org/repos/asf/incubator/ambari/tags/release-x.y.z-rc{rc_num}rc0  https://svn.apache.org/repos/asf/incubator/ambari/tags/release-x.y.z -m "Release x.y.z"

Note that it takes 24 hours for the changes to propagate to the mirrors.
After waiting Wait 24 hours and verifying verify that the bits are available in the mirrors , send out before sending an announcement.

Send out Announcement to ambari-dev@incubator.apache.org and ambari-user@incubator.apache.org.

Suject: \[ANNOUNCE\] Apache Ambari x.y.z.

The Apache Ambari team is proud to announce Apache Ambari version x.y.z

...