This page last changed on Apr 30, 2005 by vmassol.
- Perform a clean SVN checkout
- Edit top level project.xml and modify <currentVersion> tag. Ex: from 0.3-SNAPSHOT to 0.3
- 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 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:
- modify the status on the home page about the delivery
- export the wiki to a zipped HTML file and add it the Downloads page
- 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 dev and Cargo user mailing lists (and to any other onsite site, magazines, etc)
- Create a blog post
- Modify again project.xml and modify <currentVersion> for the next version
|