Release procedure

Releases are now performed using Maven 2 so you need to have Maven 2 installed (see the building page).

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. Example:
On the SVN trunk change all references of (N)-SNAPSHOT by (N+1)-SNAPSHOT (for ex from 0.6-SNAPSHOT to 0.7-SNAPSHOT). Perform this by doing a global search and replace.
In the new branch, do the same and replace all references of (N)-SNAPSHOT by (N) (Ex: from 0.3-SNAPSHOT to 0.3).
Delete all the (N)-SNAPSHOT artifacts from your local maven repositories to have a clean slate.
Run mvn install at the top level of the release branch to build the different artifacts and ensure everything is ok
Run mvn assembly:assembly in core/uberjar of the release branch. Note: in the future this will be done automatically when you call mvn install.
Deploy everything by typing mvn deploy at the top level of the release branch. For this to work you'll need to create a settings.xml file (in your .m2 directory or in your user home directory. Inside you'll need to define your credentials and more. Here's an example settings.xml:
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
4. create a release notes page for the new version
Tag the branch created in step 1 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