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

TBD: No release yet, please change it to real process

This article describes the steps to follow when building a DuckHawk release.

Notify developers that you are about to make a release.

At least 24 hours before building a release. This should allow them to ensure their fixes are in the code base.

Here is a sample email.

We will start the process of building a new DuckHawk release in
24 hours. Could everyone please ensure that all code is committed.
Once we start, please don't commit any files until the release is
completed.
Check all code back into Subversion

If you have not done so already, check all the code you have been editing into Subversion.

$ svn commit -m "Fixed xxx bugs" <filenames>
Update the CHANGES file

Update and commit CHANGES file with updates between the last release and this one. These files should be in the base directory.

These can be found in the Project Plan

Commit CHANGES back into SVN

$ svn commit -m "Prepared CHANGES for release <release-number>" CHANGES
Get latest updates from SVN

Ensure you have the latest files from SVN.

$ cd /<duckhawk development directory>
$ svn update -r HEAD
Tag the release

Tag the files that should be in the release. (Usually, not all files in SVN are included in a release).

The <tag> should be of the form: duckhawk-[number]-[status]

For example:

  • duckhawk-0_1
  • duckhawk-0_1-rc3
  • duckhawk-0_2-alpha1
$ svn copy https://svn.codehaus.org/duckhawk/trunk https://svn.codehaus.org/duckhawk/tags/<version>
Export the release

This may be performed as the anonymous SVN user.

$ mkdir \~/tmp
$ cd \~/tmp
$ svn export [https://svn.codehaus.org/duckhawk/tags/]<tag>/duckhawk duckhawk
Build the distribution
$ cd \~/tmp/duckhawk/
$ mvn package
Get signoff from DuckHawk developers

Copy the release to a tmp directory (where?) and give duckhawk-dev 24 hours to check.

Upload to Download director

TBD: This process still to be fleshed out

Update release tags in JIRA

TBD: Link to JIRA Version Manager

Set the release date for the current release. Any issues which were tagged to be fixed in this release should be moved to the next release.

Update Web Pages

Update notice at: http://docs.codehaus.org/display/DH/Download and http://docs.codehaus.org/display/DH/Home

Announce

Notify mailing lists.

Labels
  • None