Page History

...

 cd ambari-git-x.y.z
 git clean -f -x -d
 cd ..
 cp -R ambari-git-x.y.z ambari-x.y.z-incubating
 tar --exclude=.git -zcvf ambari-x.y.z-incubating.tar.gz ambari-x.y.z-incubating 

Sign the tarball

gpg2  --armor --output ambari-{release_number}-incubating.tar.gz.asc --detach-sig ambari-{release_number}-incubating.tar.gz

Generate MD5 checksums:

md5sum ambari-X.Y.Z-incubating.tar.gz > ambari-X.Y.Z-incubating.tar.gz.md5
sha1sum ambari-X.Y.Z-incubating.tar.gz > ambari-X.Y.Z-incubating.tar.gz.sha

or

openssl md5 ambari-X.Y.Z-incubating.tar.gz > ambari-X.Y.Z-incubating.tar.gz.md5
openssl sha1 ambari-X.Y.Z-incubating.tar.gz > ambari-X.Y.Z-incubating.tar.gz.sha

Upload the artifacts to your apache home:

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

Call for a vote on the

...

dev@ambari.apache.org mailing list with something like this:

I have created an ambari-** release candidate.
GIT source tag (r***)

https://git-wip-us.apache.org/repos/asf/incubator-ambari/repo?p=incubator-ambari.git;a=log;h=refs/tags/release-x.y.z-rc0

...

Once the vote passes/fails, send out an email with subject like "[RESULT] [VOTE] Apache Ambari x.y.z rc0" to general@incubatordev@ambari.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:

Verify your PGP key is provided to Apache. Apache verifies that distributions are correctly signed.

...

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

Send out Announcement to

...

dev@ambari.apache.org and

...

user@ambari.apache.org.

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

...