Boost Release Procedures

Introduction
Procedure Overview
Procedures for Developers
Procedures for the Release Manager

Introduction

Each release of Boost software is overseen by a release manager, who coordinates release activities via the Boost mailing list, as well as performing the detailed procedures for the release.

Boost developers assist the release manager by reviewing regression test logs, and committing and tagging fixes into CVS.

Release Procedure Overview

• Discussion on the main Boost mailing list to determine the target date for initial release tagging of the CVS main trunk.
   
• Release manager performs initial release tagging.  Subsequent CVS working copy updates for the tag retrieve the release candidate.
   
• Regression tests run on release candidate.
   
• Developers commit and retag fixed files.
   
• Repeat previous two steps until release manager is satisfied.
   
• Release manager rolls out the actual release.

Release Procedures for Developers

• As the initial release tagging approaches (as announced on the main mailing list), bring the main trunk CVS files you are responsible for into a stable state.
   
• If you know of changes in either your code or its dependencies, start checking regression test results to ensure your tests still pass.  Don't necessarily wait for the initial release tagging.
   
• After the release manager has announced completion of the initial CVS tagging for the release, check the latest regression test results to be sure your tests haven't broken.
   
• If you fix a problem after the initial release tagging, and you want the fix included in the release, you are responsible for updating the tag.  The tag is what determines which file revision is included in the release.

Boost release tags are in the form: Version_1_26_2.  Here is how to re-tag an updated file so that the newer version will be included in the release.  First commit all changes, then:

• Via the command line: cvs tag -F Version_1_26_2 filename.
   
• Via WinCVS: Select the files to be retagged, then Modify | Create tag on selection... | Create tag settings | New tag name: Version_1_26_2, check Overwrite existing tags, click OK.

• Note that developers can continue working on main trunk code changes after the initial tagging. There is no need to wait until the release.  Modified files committed to CVS will not be included in the release unless the developer explicitly tags them for inclusion.

Release Procedures for the Release Manager

(To be supplied)

Revised: 21 January, 2002