This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.
This page describes the steps that a release manager needs to take to perform a release of Apache CloudStack's CloudMonkey CLI tool.
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.
Once it appears that any outstanding blockers have been addressed, you can proceed to the next step.
Update your local git repo's master branch from the ASF repository:
Make sure your local copy exactly matches the remote repo:
Then run the source build script (Replacing the parameters: X.X.X=your official version number for the release; CCCC=the GPG Key to sign both the artifacts and the git tag with):
( optionally specifying your local directory layout - see performrelease.sh -h for details )
This will automatically commit (the -c) to the cloudstack dist dev folder.
Get the commit-sh to vote against for your VOTE email (comes from the command above in a line like this: completed. use commit-sh of b25d27d80b62de3408041821aa99e68712ae2728 when starting the VOTE thread )
Test the Build
Follow the instructions documented in your release branch's test procedures wiki page.
If your personal tests pass, you are ready to propose the release to the community.
Email the firstname.lastname@example.org mailing list, using the following template:
SUBJECT: [VOTE] Release Apache CloudStack CloudMonkey X.X.X
After 72 hours, the vote can be closed.
If (after tallying the vote) the binding +1 votes are not in the majority, the issues noted need to be addressed and process starts again. You need to send out a results email (or a less formal abort email) for the VOTE thread.
If the vote passes, then send a [RESULTS] vote to the dev list. Template below:
SUBJECT: [RESULT][VOTE] Apache CloudStack X.X.X
Edit cloudmonkey/config.py to set the new version number.
The release should have already been tagged in your local repo when you used the build_asf.sh script (the -t option). However, you need to push that tag once the VOTE passes:
Move the release artifacts into place (replace X.X.X with the release number, and replace Y.Y.Y with the previous release number):
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.
Remove the prior release from the release dist area (it's still archived):
First, make sure that you are a package owner of the cloudmonkey package on pypi. Ask a current owner to add you if you aren't one yet.
Build from the tag:
Now log into pypi and create a new release (source artifact).
Be sure to include the dist/cloudmonkey-X.X.X.tar.gz.asc file as the signature.
Edit the _version_ variable at the top of cloudmonkey/config.py and then commit / push the change.
After waiting 24 hours for the ASF mirrors to catch up, the release is ready to be announced. Send separate announcement emails to email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org and email@example.com. This is best done using your apache.org address, so that the announcement gets moderated through to the lists.
The contents of the message should have been discussed on firstname.lastname@example.org first.