Skip to end of metadata
Comment: Migrated to Confluence 4.0
Go to start of metadata

The following process should be followed when a release is made. Please follow each step carefully.

  • Check that the PicoContainer Roadmap or NanoContainer Roadmap have resolved all scheduled issues. If not, resolve them, or schedule remaining issues to a future version.
  • Send email to the development mailing list telling peopl to stay away from the SCM.
  • Set the release version number in PicoContainer's project.xml. For example, 1.0-SNAPSHOT would become 1.0-beta-1.
  • Update any other projects you control that depend on PicoContainer.
  • Make sure none of the external jar dependencies are SNAPSHOT dependencies, but releases or timestamped versions (so the release can be built in the future).
  • Update the Downloads page and add entries for the version you're about to release.
  • Update the PICO-JavaDoc Confluence shortcut http://docs.codehaus.org/admin/browseshortcuts.action. You may have to remove the old one and add it again with an updated value.
  • Make a new java/picocontainer/site/picosite.zip (using the Teleport tool - Paul has a copy). TODO should be replaced with non-proprietory tool
  • Commit your changes to the SCM.
  • Wait for Continuous Integration to complete a successful build.
    • Alternatively - do maven pico:deploy -Dmaven.remote.group=users
  • Go to the deployed site's download page and verify that the downloads work:
    • Maven builds for the source distros should work
    • The binary distro's docs should be browsable and links to javadocs should be local.
  • Tag the relevant SVN trunk via svn cp <trunk URL> <tag URL>
  • Mark the version as released in JIRA
  • Make sure JIRA has versions matching the version now declared in project.xml.
  • Update the Codehaus Blog (if you have access to it) and announce the release.
  • Send email to the development mailing list announcing the release, with a link to the blog on http://blogs.codehaus.org/
  • Reset the development version number to a snapshot of the next major.minor release in project.xml (/picocontainer/trunk) and commit the change to the SCM. For example, 1.0-beta-1 would become 1.0-SNAPSHOT.
  • Set the version of the Nano/Micro components to the new Pico release in project.properties (/nanocontainer-*/trunk) and commit the change to the SCM.
  • If this is a major release, also send announcements to TheServerside.com, FreshMeat.net and JavaLobby.org
Labels
  • None