Bug Triage: Difference between revisions

3,988 bytes added ,  19 April 2018
No edit summary
(→‎Triage Process: update link)
 
(28 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{LastUpdated}}
{{LastUpdated}}


=What we do=  
=Triage Process=


Mozilla's bugmaster develops policies and processes for managing bugs, their goal is to "leave no bug behind," and help Mozillians make crisp and actionable decisions on bugs, and enable them to follow-through on their decisions.
If you're triaging bugs in a component, [https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md Triage Process for Firefox Components in mozilla-central and Bugzilla] is the process we follow.


=Triage Process=
=Initiative Process=
 
There are a number of workflows in Bugzilla that are in addition to and often across our Component system. These initiative will modify our [https://docs.google.com/a/mozilla.com/document/d/1kZkXdeyTCUWg9KxM5I9ly_Qdo9KOMhlKuEgLtuv0jq8/edit?usp=sharing_eil&ts=59a08dbc Initiative Template] and the modified document will be linked below. Any special tagging required by these initiates will be registered as [[Bugmasters/Process/Metadata|Metadata]] and also described in the Initiative document.


If you're triaging bugs in a component, [[Bugmasters/Process/Triage|Triage for Component Leads]] is the process we follow.
* [https://docs.google.com/document/d/1L6zpmCfQP81HRPRv4Ma5Cj7fDG4qD9mtLFDgH8FHmJ4/edit#heading=h.5bzuz130e1nn Performance Initiative] - Triage and tracking of bugs we believe are essential to Firefox's responsiveness and throughput. NOTE: Update of the Quantum Flow initiative.


{{:Bugmasters/Projects/Bug Handling/Scorecard}}
{{:Bugmasters/Projects/Bug Handling/Scorecard}}
{{:Bugmasters/Projects/Bug_Handling/Bug_Husbandry}}


{{:Bugmasters/Projects/Bug Handling/Stale Bugs}}
{{:Bugmasters/Projects/Bug Handling/Stale Bugs}}
= Regular Triages =
== Core (was Platform) Regression Triage ==
[[Platform#Weekly_Regression_Triage_Meeting|Details on Platform wiki page]] (TODO: break out into module)
== Firefox::General ==
* Thursdays, 10am Pacific, Vidyo Channel Bugmasters
* [https://mzl.la/2B0kDGV Untriaged Firefox::General bugs w/o needinfo? in current release cycle].
== Product Triage ==
== Security Triage ==
== Tech Evangelism ==
* Thursdays, 8am Pacific, Vidyo Channel Compatibility
* [https://mzl.la/2H9Qzc6 Untriaged Tech Evangelism::Desktop and ::Mobile with no priority (minus P5s)]
= Per-release Triage Queries =
== Firefox 60 Queries ==
First nightly 2018-01-22
[https://mzl.la/2DB0okd P1 bugs which are affecting for Firefox 60]; these bugs should be reviewed to see if they are ''still'' P1s and if they should ''not'' be <tt>wontfix</tt>ed.
[https://mzl.la/2G9Mmos Bugs for which we don't know if they affect Firefox 60 by triage status]; un-triaged bugs should be reviewed as early in the cycle as possible.
Bugs filed later in the cycle should only be considered if they will result in a dot release if they are not addressed.
[https://docs.google.com/spreadsheets/d/1OFdnPaWpDSaWrT80P6GK5RzOYMkClAYR6wsNr3nLgpQ Triage stats for this release]
== Firefox 59 Queries ==
First nightly 2017-11-13
[https://mzl.la/2ic7j7E P1 bugs which are affecting or fix-optional for Firefox 59]; these bugs should be reviewed to see if they are ''still'' P1s and if they should ''not'' be <tt>wontfix</tt>ed.
[https://mzl.la/2Ds5Uma Bugs for which we don't know if they affect Firefox 59 by triage status]; un-triaged bugs should be reviewed as early in the cycle as possible.
Bugs filed later in the cycle should only be considered if they will result in a dot release if they are not addressed.
[https://docs.google.com/spreadsheets/d/1XCkAsmBzvzRRpTtpmKGoV_wRdcGYVgE_9tzEfBwVPqw Triage stats for this release]
== Firefox 58 Queries ==
First nightly 2017-08-03
[https://mzl.la/2h7U9vi P1 bugs which are affecting or fix-optional for Firefox 58]; these bugs should be reviewed to see if they are ''still'' P1s and if they should ''not'' be <tt>wontfix</tt>ed.
[https://mzl.la/2ze7SY1 Bugs for which we don't know if they affect Firefox 58 by triage status]; un-triaged bugs should be reviewed as early in the cycle as possible.
Bugs filed later in the cycle should only be considered if they will result in a dot release if they are not addressed.
[https://docs.google.com/spreadsheets/d/1hIJlFRTH2gQU2J8mmiF3MfEJK23w8Kwpunvh4DEgXvQ Triage stats for this release]
== Firefox 57 Queries ==
First Nightly: 2017-06-12
* [https://mzl.la/2ipcLmW P1 bugs which are affecting or fix-optional for Firefox 57]; these bugs should be reviewed to see if they are ''still'' P1s and if they should ''not'' be <tt>wontfix</tt>ed.
* [https://mzl.la/2h7sBpC Bugs for which we don't know if they affect Firefox 57 by triage status]; un-triaged bugs should be reviewed as early in the cycle as possible.
** Bugs filed later in the cycle should only be considered for fixes if they will result in a dot release if they are not addressed.
* [https://mzl.la/2Aok1I4 Bugs wontfixed for this release]
* [https://mzl.la/2j6MTQZ Bugs deferred to next release]
* [https://docs.google.com/spreadsheets/d/1k98lDyxm2g2vYMbvrCSnJ46ZTqE9FvRWLwIF-cGlmt0/edit?pli=1#gid=1956742257 Triage stats for this release]


=Who we are=
=Who we are=


* Emma Humphries (:emceeaich), Bugmaster [mailto:ehumphries@mozilla.com ehumphries@mozilla.com]
* Emma Humphries (:emceeaich), Bugmaster [mailto:ehumphries@mozilla.com ehumphries@mozilla.com]
* [[Bugmasters/Project/Bug_Handling/Triage_Leads|The individual triage leads in each bugzilla component ]]
* [[https://bugzilla.mozilla.org/page.cgi?id=triage_owners.html The individual triage leads in each bugzilla component ]]


=Projects=
=Projects=
Line 31: Line 104:
* [https://github.com/mozilla/triage-report Triage Report] - scoreboard for components with most un-triaged bugs
* [https://github.com/mozilla/triage-report Triage Report] - scoreboard for components with most un-triaged bugs


=Meetings=
=Office Hours=
The bugmaster office has no scheduled meetings at this time.
 
Wednesdays, alternating between 7 AM, Pacific and 5pm Pacific
 
In #bugmasters in IRC


=Communication=
=Communication=
Line 39: Line 115:
* The IRC channel: [irc://irc.mozilla.org#qa irc.mozilla.org#bugmasters]. Join us on IRC to say hello, introduce yourself, and talk about bugs, bugs, bugs. Questions are welcome!
* The IRC channel: [irc://irc.mozilla.org#qa irc.mozilla.org#bugmasters]. Join us on IRC to say hello, introduce yourself, and talk about bugs, bugs, bugs. Questions are welcome!
* Joining the [https://lists.mozilla.org/listinfo/bugmasters bugmaster mailing list] to be informed of all the news and the discussions.
* Joining the [https://lists.mozilla.org/listinfo/bugmasters bugmaster mailing list] to be informed of all the news and the discussions.
* If you triage bugs in a component, you should be on [https://mail.mozilla.org/listinfo/firefox-triage-leads the triage leads mailing list]


=Useful Links=
=Useful Links=