...

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.

...