Bugzilla:Release Process: Difference between revisions

Jump to navigation Jump to search
→‎When to Release: Blocking flags
(→‎Version Numbers: Even vs odd minor version numbers)
(→‎When to Release: Blocking flags)
Line 11: Line 11:
== When to Release ==
== When to Release ==


In [[Bugzilla:Meetings:2014-05-28|May 2014]] we decided to try to release approximately every 6 months with whatever is ready at the time.  This gets new features out the door more quickly.  Branching should be done when master is relatively stable, but sometimes branching with known bugs is acceptable if it allows other large, potentially unstable features to land (for the next release).  If there are bugs related to new features in the release branch, the feature should be backed out of the release branch (if it's very recent), or fixes should be committed to both the release branch and master.
In [[Bugzilla:Meetings:2014-05-28|May 2014]] we decided to try to release approximately every 6 months with whatever is ready at the time.  This gets new features out the door more quickly.  Branching should be done when master is relatively stable, but sometimes branching with known bugs is acceptable if it allows other large, potentially unstable features to land (for the next release).  If there are bugs related to new features in the release branch, the feature should be backed out of the release branch (if it's very recent), or fixes should be committed to both the release branch and master.  Bugs blocking release should be denoted with a blocking<version> flag, e.g. blocking5.0.


The version number will be determined at time of branching depending on the changes included, as per the section above.  Note that this means we may have back-to-back major releases.
The version number will be determined at time of branching depending on the changes included, as per the section above.  Note that this means we may have back-to-back major releases.
Confirmed users
1,927

edits

Navigation menu