Thunderbird/Release Driving: Difference between revisions

Jump to navigation Jump to search
no edit summary
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 mozilla.dev.apps.thunderbird and/or mozilla.dev.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].
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)


=== Flags ===
== Managing Releases ==
 
Flags are the main tracking tool of thunderbird-drivers for releases.
 
Detailed descriptions can be found on the [[Thunderbird/Release Driving/Flags|Flags]] page.
 
=== Attachment Flags ===
When we are locked down in a restricted phase in the lead up to a release we will restrict checkins to the tree to be approvals-only.


The currently available flag is approval-thunderbird3. You only need to request approval when the tree status (as shown on the tinderbox page) or other notices states that you must. If in doubt, ask.
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:


To request approval:
* 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.


* Go to the attachment page of the patch you want to request approvals for (click the details link).
== Flags and how they are used ==
* On that page:
** Set 'approval-thunderbird3' to '?'.
** In the comments field enter reasons why this should be accepted for the next release.
*** Include an assessment of risk.
*** Mention other significant things such as performance improvements.


Patches which are tidy up only or high risk are unlikely to be accepted. For other patches it depends on the level of risk, the particular release the freeze is for and the time remaining until the release/freeze.
* 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 & Priorities ===
== Target Milestones ==


These two fields will be used in combination with blocking & wanted to help organize what work happens when. The intent is that the ownership of these fields is shared between thunderbird-drivers and the developer who is working on the bug.  All parties should feel free to set the field as appropriate, but at the same time being prepared for possible polite dialog when disagreements occur.
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.


=== How to use flags ===
Thunderbird Drivers request that when a bug is marked as fixed, its milestone is updated to be the match the next trunk release milestone.


To nominate a bug for blocking or wanted status, set the appropriate flag to ? in Bugzilla.  The drivers will then approve or deny the nomination.  To check the current blocking and wanted bugs see the following lists:
== Triage ==


* [http://hg.mozilla.org/users/bugzilla_standard8.plus.com/drivertools/raw-file/default/bugtracking/index.html?branch=3.0 Thunderbird 3.0.x]
One or more of the Thunderbird drivers will regularly triage nominations and other status flags, consulting with other drivers and relevant parties as necessary.
* [http://hg.mozilla.org/users/bugzilla_standard8.plus.com/drivertools/raw-file/default/bugtracking/index.html?branch=3.1 Thunderbird 3.1]


=== Triage ===
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].
Each Bugzilla component in the Mail/News Core and Thunderbird products has a driver (see the [[Thunderbird:Release Driving:Components|list of component drivers]]) in charge of triaging that component from time to time.
Drivers are encouraged to try and give a one or two sentence explanation when we mark a nomination as + or -; this will allow everyone to detect mistakes and renominate with an explanation.


=== Fundamental Fact: Scarcity ===
=== Fundamental Fact: Scarcity ===
canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,628

edits

Navigation menu