Login | Register
My pages Projects Community openCollabNet

repoguard
Wiki: ReleaseManagement

Edit this page | Links to this page | Page information | Attachments | Refresh page

 

Release Number Format

RepoGuard releases are uniquely named using the following template:

repoguard-<major number>.<minor number>.<patch number>

Examples

  • repoguard-0.2.0
  • repoguard-0.3.0.dev-r92

<!> The increment of one of these numbers has a specific meaning:

  • Increment of the major number: Indicates a major release which provides large changes (e.g., many new features or incompatibilities concerning the configuration format).

  • Increment of the minor number: Indicates a minor release which provides a number of new features and bug fixes.

  • Increment of the patch number: Indicates a patch release which provides critical bug fixes. An update is always recommend.

  • To indicate in development / snapshot releases, the suffix .dev-r<Subversion Revision Number> is added.

Release Planning

The detailed release planning is done using the milestones feature of the Tigris issue tracker. Here you find a detailed overview about all releases.

The Roadmap provides a high-level overview of the releases and the corresponding schedule.

Release Creation

As soon as all issues of a milestone have been resolved, the release process starts. The release stabilization is performed either on the trunk or on a specific stabilization branch (naming pattern: <major number>.<minor number>.<patch number>-RB. However, you should ensure that only bug fixes or documentation improvements are committed to it. In addition, you have to configure the release build (activate it, configure the repository URL).

The release can be published when the following conditions are met:

  • All unit and integration tests are passed.
  • The release has been successfully tested in a production environment.
  • The user documentation is up-to-date.

To finish the release, perform the following tasks:

  • Trigger the release build.
  • Upload the package to the release folder and to PyPI.

  • Set the status of all related issues to "closed".
  • Create a Subversion tag (naming pattern: <major number>.<minor number>.<patch number>) and merge back required changes to the trunk if required.

  • Publish release announcements.

ReleaseManagement (last edited 2012-03-14 20:22:19 -0800 by ?schlauch)