Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 32 Next »

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

  1. Create a branch in SVN so that others can keep working on the trunk. Create the branch in svn+ssh://<version> and check it out on your local machine. Example:
  2. On the SVN trunk change all references of (N)-SNAPSHOT by (N+1)-SNAPSHOT (for ex from 0.6-SNAPSHOT to 0.7-SNAPSHOT) and commit. Perform this by doing a global search and replace. Note: You may want to perform a clean before doing the search and replace to avoid changing all the build target directories.
  3. In the new branch, do the same and replace all references of (N)-SNAPSHOT by (N) and commit (Ex: from 0.3-SNAPSHOT to 0.3).
  4. Delete all the (N)-SNAPSHOT artifacts from your local maven repositories to have a clean slate.
  5. Run mvn install at the top level of the release branch to build the different artifacts and ensure everything is ok
  6. 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.
  7. 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:
  8. Log onto Cargo JIRA, release the current version and add the next version
  9. 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
  10. Tag the branch created in step 1 to svn+ssh://<version>
  11. Send an announcement email to Cargo mailing lists (and to other relevent sites)
  12. Create a blog post
  • No labels