Release procedure

Create a branch in SVN so that others can keep working on the trunk. Create the branch in svn+ssh://svn.cargo.codehaus.org/home/projects/cargo/scm/cargo/branches/<version> and check it out on your local machine
Change all references to the SNAPSHOT version to the version to be released. For example, edit the top level project.xml file and modify <currentVersion> tag. Ex: from 0.3-SNAPSHOT to 0.3. Do a search to ensure you're not missing anything
Do the same on the SVN trunk by incrementing the version (for ex from 0.6-SNAPSHOT to 0.7-SNAPSHOT)
Run maven at top level to generate the distribution
Run maven cargo:site to generate the development site. Check the result. If ok, run maven cargo:site-deploy to deploy the site to beaver.codehaus.org. You'll need the following properties set up in your build.properties (replace with your own data):
- maven.username = vmassol
- maven.ssh.executable = tortoiseplink
- maven.scp.executable = pscp
Upload the Cargo jar and the Cargo Maven plugin by running maven cargo:deploy. You'll need the following properties set up in your build.properties (replace with your own data):
- maven.repo.list = codehaus
- maven.repo.codehaus.username = vmassol
- maven.repo.codehaus.privatekey = C:/Documents and Settings/Vincent Massol/My Documents/.ssh/vmassol.ssh2
- maven.repo.codehaus.passphrase =
Log onto Cargo JIRA, release the current version and add the next version
Check that the Cargo wiki is up to date. Specifically, perform the following updates:
1. modify the status on the home page about the delivery
2. export the wiki to a zipped HTML file and add it the Downloads page
3. modify the Downloads page to include the latest download links
Tag SVN by copying the HEAD to svn+ssh://svn.cargo.codehaus.org/home/projects/cargo/scm/cargo/tags/<version>
Send an announcement email to Cargo mailing lists (and to other relevent sites)
Create a blog post