Changes between Version 2 and Version 3 of BranchesAndTags


Ignore:
Timestamp:
Nov 21, 2012, 4:41:00 AM (6 years ago)
Author:
tom.prince
Comment:

Add some documentation about bugfix pN releases.

Legend:

Unmodified
Added
Removed
Modified
  • BranchesAndTags

    v2 v3  
    55The commit on master *after* the release branch begins is tagged with the next version and {{{-pre}}}, e.g., {{{v0.8.3-pre}}}.  This means that builds from trunk will have versions {{{v0.8.3-pre-NN-HHHHHH}}}.  If plans change and the expected next release version changes (e.g., to 0.9.0 or, dare I imagine it, 1.0.0?), then just re-tag the master at that time with a new {{{-pre}}} tag.
    66
    7 Release branches are left open forever in case a security release needs to be made.  In that case, the relevant fix is committed to the branch, a new tag is made (with a {{{pN}}} suffix), and a distribution package created.  Note that, aside from critical security patches, we do not support any release but the most recent.
     7Release branches are left open forever in case a security release needs to be made.  In that case, the relevant fix is committed to the branch, a new tag is made (with a {{{pN}}} suffix), and a distribution package created.  Note that, aside from critical security patches, we do not support any release but the most recent. Bugfixes for a given release are also made on the release branches, particularly for bugs that break significant functionality. These are typically released as {{{pN}}} release, shortly after the main release.