Release Process

...Checklist...

The following actions should be performed when releasing a new version of drools.

After deploying the release, take a few moments to verify that the files were all posted as expected. Verify that the new release does download from the links provided.

...Checklist...

  1. Send email to the development mailing list announcing a version control freeze for tagging.
  2. Check out fresh working copy of CVS module you're going to tag.
  3. Convert all SNAPSHOT jars in project.xml to concrete timestamped or versioned jar references.
  4. Ensure that build.xml agrees with project.xml with respect to dependent jars names.
  5. Update xdocs/releases.xml to reflect the current build version.
  6. Set the release version number in Maven project.xml . For example, 2.0-beta-9-dev would become 2.0-beta-9
  7. Perform a successful build and test suite execution, and run the clean target to remove any generated files using maven. Repeat this process using ant.
  8. Commit your changes to the version control repository.
  9. Tag the release via cvs -q tag PROJECT_VERSION_MODIFIER . An example release tag is DROOLS_2_0_BETA_9 .
  10. Deploy the drools maven-generated project site.
  11. 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, 2.0-beta-9 would become 2.0-beta-10-dev
  12. Send email to the development mailing list announcing completion of the tag.