Thunderbird/Release Driving: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(massive update :))
 
(20 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<small>[[Thunderbird|<< Back to Thunderbird]]</small>
<small>[[Thunderbird|<< Back to Thunderbird]]</small>


== Thunderbird Drivers ==
== Thunderbird Release 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 implementedWe may or may not achieve this initially; if you have suggestions about how we can do better, please let us know.
Thunderbird drivers are primarily concerned with ensuring the quality, stability and security of the Thunderbird releases. This responsibility covers beta and release channelsThunderbird drivers may decide to advance or delay release dates and features or fixes through the release train if it affects quality, stability or security.


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].
The active team that is primarily responsible for Thunderbird releases is:
* Wayne Mery (:wsmwk, Release Manager)
* Jörg Knobloch (:jorgk, Release Driver)  
* Joe Sabash (:joes, Quality Assurance Lead)


Currently Active Drivers
Jörg has permissions to grant or deny tracking and approvals on bugs and patches.
* David Ascher (davida)
The Thunderbird drivers list (thunderbird-drivers@mozilla.org) consists of the active team as well as those involved in producing Thunderbird releases, and appropriate advisers. At the team's discretion, it also contains third parties who are responsible for producing distributed builds of Thunderbird, primarily Linux distributions, so that they are advised as to build and release progress, timing and issues.
* David Bienvenu (bienvenu)
* Bryan Clark (clarkbw)
* Magnus Melin (mkmelin)
* Dan Mosedale (dmose)
* Phil Ringnalda (philor)


=== Flags ===
== Managing Releases ==
The main tool of thunderbird-drivers is a rough prioritization of bugs done with a couple of flags:


; Blocking: a bug that, if it were the last unfixed bug, we would hold a release for, rather than ship without. Note that this implies that fixing the bug is worth the time-value of not having the rest of the release in hands of users for that much longer.
=== 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.


; Wanted: a restricted set of things that thunderbird-drivers think would be nice to have, but that we would be willing to ship without.  Note that wanted- doesn't mean that we wouldn't accept a patch; it means that we're not actively devoting energy to driving this into Thunderbird 3.
Thunderbird Drivers request that when a bug is marked as fixed, its milestone is updated to be the match the next trunk release milestone.


Note that as new information appears and time passes, the bugs that are considered blocking+ and wanted+ are likely to change somewhat.
== 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.


=== Target Milestones &amp; Priorities ===
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].


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.
== For Release Drivers ==


=== How to use flags ===
* [[Thunderbird/Release_Driving/Rapid_Release_Activities|Rapid Release Driving]]
* [[Thunderbird/Driver Meetings|Driver meeting info/notes]]
* [[Thunderbird/Release_Driving/Checklists#Obsolete_pages|Obsolete documents]]


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:
[[Category:Thunderbird|*]]
 
;3.0: [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=blocking-thunderbird3%3F&sharer_id=1537 blocking?] [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=blocking-thunderbird3%2B&sharer_id=1537 blocking+] [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=wanted-thunderbird3%2B&sharer_id=1537 wanted+] [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=wanted-thunderbird3%3F&sharer_id=1537 wanted?]
 
'''Note''': If you want quick access to these links, you can edit your [https://bugzilla.mozilla.org/userprefs.cgi?tab=saved-searches saved searches] preferences in bugzilla and check them - then they'll be at the bottom of all bugzilla pages.
 
=== Triage ===
The hope is to set up some sort of weekly drivers meeting where we can work through untriaged nominations.
 
We'll 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.
 
As part of keeping this a low-touch process, we'd like individual drivers to feel empowered to go through nominations on their own and use their best judgment to make calls.  As explained above, people can renominate if they disagree.
 
=== 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.
 
[[category:Thunderbird|*]]

Latest revision as of 17:07, 25 August 2017

<< Back to Thunderbird

Thunderbird Release Drivers

Thunderbird drivers are primarily concerned with ensuring the quality, stability and security of the Thunderbird releases. This responsibility covers beta and release channels. Thunderbird drivers may decide to advance or delay release dates and features or fixes through the release train if it affects quality, stability or security.

The active team that is primarily responsible for Thunderbird releases is:

  • Wayne Mery (:wsmwk, Release Manager)
  • Jörg Knobloch (:jorgk, Release Driver)
  • Joe Sabash (:joes, Quality Assurance Lead)

Jörg has permissions to grant or deny tracking and approvals on bugs and patches. The Thunderbird drivers list (thunderbird-drivers@mozilla.org) consists of the active team as well as those involved in producing Thunderbird releases, and appropriate advisers. At the team's discretion, it also contains third parties who are responsible for producing distributed builds of Thunderbird, primarily Linux distributions, so that they are advised as to build and release progress, timing and issues.

Managing Releases

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.

For Release Drivers