...

1. Ensure that you are working on the correct branch
2. Set the release version # for the branch in cloudmonkey/config.py
3. Confirm that the information in README.md is current
4. Confirm that the information in LICENSE and NOTICE are current
5. Update the CHANGES file with the critical changes introduced in the release (Be sure to highlight any changes the break backward compatibility)
6. Remove "version has not been released" warnings from the CHANGES file
7. Ensure that the CHANGES file in your release branch is synced with the version in the master branch (which may have a future release already in it)

Getting Community

...

Consensus

Prior to an official vote, start a thread on the cloudstack-dev mailing list, specifically asking for comments on the project's readiness to cut a release.

...

Update your local git repo's master branch from the ASF repository:

git fetch origin

Check out the release branch:

git checkout X.X.X

...

origin

...

Make sure your local copy exactly matches the remote repo:

git reset --hard HEAD
git clean -qfxd
git rebase origin/X.X.Xmaster

Then run the source build script (Replacing the parameters: X.X.X=your official version number for the release; B.B=the branch (can be master) that the release is coming from; CCCC=the GPG Key to sign both the artifacts and the git tag with):

./performrelease.sh -v X.X.X -b B.B -c -t

( optionally specifying your local directory layout - see performrelease.sh -h for details )

...

Wait 24 hours for the mirrors to catch up. Note that only a PMC member can move the artifact to the release location.

Update http://cloudstack.apache.org/downloads.html to point to the new release, and add the older release to the archive list.

...