Confirm
2,615
edits
Changes
New page: == Thunderbird Drivers == Thunderbird-driving is intended to be a low-overhead process to make sure that Thunderbird converges on releases that have the important bugs fixed and high-impac...
== Thunderbird Drivers ==
Thunderbird-driving is intended to be a low-overhead process to make sure that 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].
Currently Active Drivers
* David Ascher (dascher)
* Magnus Melin (mkmelin)
* Dan Mosedale (dmose)
* Phil Ringnalda (philor)
=== Flags ===
The main tool of thunderbird-drivers is a rough prioritization of bugs done with a couple of flags:
; Blocking: bugs that we think we would actually hold a release for, rather than ship without. Note that as new information appears and time passes, the bugs that are considered blocking+ are likely to change. If you think a specific bug is likely to be important enough that we shouldn't ship without it, please nominate it to block the appropriate release. Do keep in mind, however, that there are many more desirable bugs features than can possibly be shipped in any given release.
; Wanted: most likely to be things that thunderbird-drivers think would be nice to have, but that we would probably ship without. Because we'd like driving to be a low-touch process, we'd generally discourage people from requesting wanted flags directly, though it currently is allowed.
=== 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.
Thunderbird-driving is intended to be a low-overhead process to make sure that 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].
Currently Active Drivers
* David Ascher (dascher)
* Magnus Melin (mkmelin)
* Dan Mosedale (dmose)
* Phil Ringnalda (philor)
=== Flags ===
The main tool of thunderbird-drivers is a rough prioritization of bugs done with a couple of flags:
; Blocking: bugs that we think we would actually hold a release for, rather than ship without. Note that as new information appears and time passes, the bugs that are considered blocking+ are likely to change. If you think a specific bug is likely to be important enough that we shouldn't ship without it, please nominate it to block the appropriate release. Do keep in mind, however, that there are many more desirable bugs features than can possibly be shipped in any given release.
; Wanted: most likely to be things that thunderbird-drivers think would be nice to have, but that we would probably ship without. Because we'd like driving to be a low-touch process, we'd generally discourage people from requesting wanted flags directly, though it currently is allowed.
=== 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.
