Thunderbird/Release Driving: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 2: | Line 2: | ||
== Thunderbird Drivers == | == Thunderbird Drivers == | ||
Thunderbird-driving is intended to be a low-overhead process to make sure that as Thunderbird converges on releases that have the important bugs fixed and high-impact features implemented. We may or may not achieve this initially; if you have suggestions about how we can do better, please let us know. | Thunderbird-driving is intended to be a low-overhead process to make sure that as Thunderbird converges on releases that have the important bugs fixed and high-impact features implemented. We may or may not achieve this initially; if you have suggestions about how we can do better, please let us know. | ||
Most relevant discussion will happen publicly, typically in | Most relevant discussion will happen publicly, typically in [[Thunderbird/tb-planning|tb-planning]]. People who have concerns that affect driving that they're not comfortable discussing publicly should email them to [mailto:thunderbird-drivers@mozilla.org thunderbird-drivers@mozilla.org]. | ||
Currently Active Drivers | Currently Active Drivers | ||
| Line 15: | Line 16: | ||
* Phil Ringnalda (philor) | * Phil Ringnalda (philor) | ||
=== | == Managing Releases == | ||
Thunderbird-drivers track releases by the use of flags in bugzilla. There are two types of releases that are tracked which have different rules due to the nature of releases: | |||
* Next major release | |||
** This is work towards the next major release of Thunderbird. | |||
** Generally only bugs that blocking the release are tracked, but as the release becomes closer, patches that may be landed are typically restricted and require approval. | |||
* Security and Stability release | |||
** These are small security based releases to an existing release of Thunderbird. Due to the nature of these releases, only small low-risk patches are generally accepted. | |||
** All patches landing in security releases require approval. | |||
** Drivers will also track blocking and wanted bugs. | |||
== Flags and how they are used == | |||
* For the next major release, see the [[Thunderbird/Release_Driving/Next_Major_Release_Policy|next major release policy.]] | |||
* For security and stability releases, see the [[Thunderbird/Security_And_Stability_Releases/Rules|rules page]] which contains all the details about blocking and approvals. | |||
== Target Milestones == | |||
A bug is typically marked as fixed when it lands on trunk (i.e. comm-central). The only exception to this is when it does not actually apply to trunk, but only to a stable branch. | |||
Thunderbird Drivers request that when a bug is marked as fixed, its milestone is updated to be the match the next trunk release milestone. | |||
== Triage == | |||
One or more of the Thunderbird drivers will regularly triage nominations and other status flags, consulting with other drivers and relevant parties as necessary. | |||
To check the current blocking and wanted bugs for a release, we have a [http://hg.mozilla.org/users/bugzilla_standard8.plus.com/drivertools/raw-file/default/bugtracking/index.html bug tracking page here]. | |||
=== Fundamental Fact: Scarcity === | === Fundamental Fact: Scarcity === | ||
Revision as of 10:44, 17 February 2011
Thunderbird Drivers
Thunderbird-driving is intended to be a low-overhead process to make sure that as Thunderbird converges on releases that have the important bugs fixed and high-impact features implemented. We may or may not achieve this initially; if you have suggestions about how we can do better, please let us know.
Most relevant discussion will happen publicly, typically in tb-planning. People who have concerns that affect driving that they're not comfortable discussing publicly should email them to thunderbird-drivers@mozilla.org.
Currently Active Drivers
- David Ascher (davida)
- Mark Banner (Standard8)
- David Bienvenu (bienvenu)
- Bryan Clark (clarkbw)
- Magnus Melin (mkmelin)
- Dan Mosedale (dmose)
- Phil Ringnalda (philor)
Managing Releases
Thunderbird-drivers track releases by the use of flags in bugzilla. There are two types of releases that are tracked which have different rules due to the nature of releases:
- Next major release
- This is work towards the next major release of Thunderbird.
- Generally only bugs that blocking the release are tracked, but as the release becomes closer, patches that may be landed are typically restricted and require approval.
- Security and Stability release
- These are small security based releases to an existing release of Thunderbird. Due to the nature of these releases, only small low-risk patches are generally accepted.
- All patches landing in security releases require approval.
- Drivers will also track blocking and wanted bugs.
Flags and how they are used
- For the next major release, see the next major release policy.
- For security and stability releases, see the rules page which contains all the details about blocking and approvals.
Target Milestones
A bug is typically marked as fixed when it lands on trunk (i.e. comm-central). The only exception to this is when it does not actually apply to trunk, but only to a stable branch.
Thunderbird Drivers request that when a bug is marked as fixed, its milestone is updated to be the match the next trunk release milestone.
Triage
One or more of the Thunderbird drivers will regularly triage nominations and other status flags, consulting with other drivers and relevant parties as necessary.
To check the current blocking and wanted bugs for a release, we have a bug tracking page here.
Fundamental Fact: Scarcity
Keep in mind that there are orders of magnitude more bug fixes & features than can possibly be shipped in any given release. A particular bug not making the cut for this next release doesn't necessarily mean it's not important, but it _does_ mean that thunderbird-drivers feels that there other are bugs that are even more important.