Consider the following to be something of a checklist.
Turbine's release process consists of tagging one or more version
control modules (Turbine and its dependencies). For the 2.x
development path, the module list to consider for tagging consists
of the following:
After tagging the release (or each module), take a few minimal steps
to assure that the archives are in the expected place and valid.
Announce your release via news outlets such as web page changes,
email announcements, press releases, etc. For instance, many Apache
projects update the jakarta-site2/xdocs/site/news.xml
document and their Freshmeat
Tagging an individual module
Send email to the development mailing list announcing a version
control freeze for tagging.
Check out fresh working copy of CVS module you're going to tag.
Set the release version number in Maven project.xml and/or Ant
default.properties. For example, 3.0-dev would become 3.0-b1 or
Update any dependency changes (possibly caused by previous module
tagging). For Maven, this consists of modifying the
jar attributes of each
Perform a successful build and test suite execution, and run the
clean target to remove any generated files.
Commit your changes to the version control repository.
Tag the release via
cvs -q tag
PROJECT_VERSION_MODIFIER. An example release tag is
TURBINE_2_2_B1 or TURBINE_3_0_RC1.
Set the next development version number in Maven project.xml
and/or Ant default.properties and commit the change to the version
control repository. For example, 3.0-b1 would become 3.0-b2-dev.
Send email to the development mailing list announcing completion
of the tag.