aXSL: Release Mechanics

Contents

• Before
• Build
• After

This page is a checklist of things that should be done for each code release.

Before

Build

1. In addition to releasing the build through sourceforge, we now make aXSL modules available through the Maven Central repository, using the Sonatype OSS Maven Repository as the staging and deployment mechanism.
2. Run the "distribution" target of the build script. The distributable output should be in build/ant/distribution.
3. Make sure the output contains a file "axsl-[version]-java.zip" where "[version]" is the release version number. Make sure this file contains the following:
   • a "readme.txt" file in the root directory
   • a "src/java/axsl-[version]-src.zip" file from the root directory
   • a "lib" directory whose contents include the following:
     • the built jar file: axsl-[version].jar
     • the built dev jar file: axsl-dev-[version].jar
     • the contents of the lib directory
     • the axsl license file
   • a "javadoc-api" directory containing the entire javadoc build.

After

1. Tag the repository. The general form of the copy is: Copy From: https://axsl.svn.sourceforge.net/svnroot/axsl/trunk Copy To: https://axsl.svn.sourceforge.net/svnroot/axsl/tags/rel-0.2
2. Unlock the repository, if it was locked above.
3. Upload distribution file to sourceforge.
4. Update the web site from the repository content.
5. Set the build file property "version" to the next level, appended with "-dev".
6. Verify that the maven artifacts are available at the central repository (The Sonatype servers synchronize to maven central hourly. The maven central index is updated each Saturday morning.)
7. Post the distribution javadocs to the web site.
8. Announce the release at:
   1. Send an email to the maintainer of the W3C XSL page.
   2. the axsl-user mailing list
   3. Add "News" item to the SourceForge system announcing the release.
   4. Consider adding "News" item to the project home page.