Release procedure

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

Add WebDav config As Codehaus has now forbidden shell access we'll need to configure WebDav deployment before we can release the next version of Cargo.

1. There are several artifacts which have separate release cycles: parent-pom, resources, core, extensions/ant, extensions/maven and extensions/maven2.
   1. Core depends on a given version of resources, this is defined by setting the resources version in the property cargo.resources.version in core/pom.xml.
   2. Extensions depend on a given version, this is defined by setting the core version in the property cargo.core.version in extensions/pom.xml
   3. Parent pom version is declared in resources/pom.xml, core/pom.xml and extensions/pom.xml.
2. Releases are done with the maven release plugin. Please do a dry-run before doing the actual release to ensure there aren't any problems. You can supply your credentials on the command line (-Dusername=<username> -Dpassword=<password>), or keep them in your settings.xml file (in your .m2 directory or in your user home directory. Here's an example settings.xml:
3. Log onto Cargo JIRA, release the current version and add the next version
4. 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. modify the Downloads and Archived Downloads pages to update the download links
   3. create a release notes page for the new version
   4. export the wiki to a zipped HTML file and add it the Downloads page
   5. modify the Cargo version in the Navigation page on the wiki
5. Send an announcement email to Cargo mailing lists (and to other relevent sites)
6. Create a blog post