Releasing the SOSI library

Preparing the release

1. First ensure that nobody has uncommitted changes
2. Check that all metrics and reports show "good numbers" on the generated Maven site (under CruiseControl)
3. Edit modules/changes.txt to document all interesting changes, additions, compatability problems etc.
4. Commit modules/changes.txt
5. Ensure that pom.xml files version numbers is increased to the new version (modules, seal, testtools, demo/provider, demo/client, demo/axis2-module, demo/client-axis2, demo/provider-axis2)
6. Check that everything compiles and runs under JDK-1.5.0, JDK-1.6.0
7. Commit any changes

Making the release

1. Remove your previous SVN checkout (entirely!)
2. Make a clean checkout from SVN
3. Run the command builddist.sh from the root of the /modules directory

Testing the release

1. Unzip the release from releases/<releasenumber>/sosi-<releasenumber>-complete.zip
2. Start a command prompt and change to <unzip directory>/sosi/bin
3. Run the runtests.sh command and check that no tests fails under JDK-1.5.0, JDK-1.6.0

Publishing the release

1. Commit release folder and edit the sosi.dk and softwareborsen site with the new release
2. Make a tag of trunk
3. Commit
4. Update versions in pom.xml to next version number
5. Commit
6. Send e-mail to all that are using the library

-- ChristianGasser - 2011-04-15