Making Releases
When it's time to cut a new release of jactiveresource, here's the steps:
- Make sure all the tickets in the release are either closed or moved to another release
- Change the version number in pom.xml and commit it
- Tag the release in subversion
- Change the version in pom.xml on the trunk to be {nextversion}-SNAPSHOT and commit it
- Checkout the tag
- Do a nice clean build and package:
$ mvn clean $ mvn package -DskipTests
- Copy packages to the web server
- Update the Download page with the new release
- Update the milestone to have a summary and the links to the downloads
- Make the javadocs by:
$ mvn javadoc:javadoc
- Copy the javadocs to the web server
- Update the wiki start page to add the api documentation links
Some of these steps can be automated with the maven release plugin, see http://www.vineetmanohar.com/2009/10/how-to-automate-project-versioning-and-release-with-maven/ for details.
We also need to teach mvn deploy how to copy the files to the web server in the proper location. This may be able to be done with http://docs.atlassian.com/maven-upload-plugin/1.1/usage.html, although it looks like it hasn't been updated in a while.
