Release Procedures

This checklist should help build a release, and make it available for the public. It is the responsible of the QA to have the release done.

Development release

Phase 1. Initiate code freeze

Ensure all committed code since last release is reviewed. Simply go through each commit, and check in the review table that this commit is reviewed.
Ensure all bugs since last release have been evaluated not to block release. Simply go through each bug and check if it has been evaluated.
Ensure all fixed bugs can be set to status CLOSED. A bug can be set to closed if it has been fixed and reviewed, and has the needed unit tests to verify it is fixed.
Update dk.netarkivet.common.Constants.BUILDSTATUS to CODEFREEZE
Commit file to SVN
Send mail to netarchivesuite-users mailing list about state of code. The mail should contain guidelines to what is allowed and expected during code freeze, and a brief list of important features of the upcoming release.

Phase 2. Release test

Phase 3.

Basically you need to do the same as when doing a development release, with the following changes and exceptions: