<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Following up on yesterday's email: I put together a draft second proposal and shopped it around some, and now I want to bring that back into the main discussion.<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">The bullet point version of this is:<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">* Add a binary field that components can use, TRIAGED (Y/N, T/F, +,-)<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">* In the case of Firefox related components, have a consistent definition of P1-P5 and make sure that triaged bugs have a Priority assigned<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">This has a couple of implications:<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">This means I have to have a plan in place for dealing with Priority going from ad-hoc to one set of meanings for bugs in Firefox components.<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">If any of you have worked with longitudinal social sciences data sets, this is a common thing. Values for fields change over time, and researcher consult documentation so that code consuming the data would work with the discontinuities. Some of this can be handled through bugzilla UI, so that components using the TRIAGED flag would display the description corresponding to P1-P5 and other components would not. <br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">We also need to go through all the existing whiteboard, keywords, and custom flags we are using for e10s and other projects that are being used to indicate importance.<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">I'd like to finish up feedback on by the end of the working day Thursday the 6th (PST.) <br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Then we'll get to work on a solid specification for the work so we can start implementation sometime in Q2.<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Thanks. <br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">-- Emma <br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 5, 2016 at 5:27 PM, Emma Humphries <span dir="ltr"><<a href="mailto:emma@mozilla.com" target="_blank">emma@mozilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">It's been a week since I asked for your comments on the plan for triage, thank you. <br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">I'm going reply to some general comments on the plan, and outline next steps. <br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Ekt and others said that up to now, individual teams have owned how they triage and prioritized bugs. Mozilla has made commitments to how we are going to follow up with people filing bugs. Thus we need consistent decisions across all the components that go into Firefox about bugs that we can share back to non-Mozillans on bugs they file, so that we can get them to contribute more high-quality bugs, and participate in other efforts in support of the project and the Open Web. I'm aware I'm asking teams with existing process to make a change, but it's for a global gain.<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Several people pointed out all the fields in Bugzilla that have and could be used to manage priorities, such as priority and rank. But we don't use the priority field consistently across the project. I've asked for teams to document how they use Priority, <a href="https://wiki.mozilla.org/Bugmasters/Projects/Folk_Knowledge/Priority_Field" target="_blank">https://wiki.mozilla.org/Bugmasters/Projects/Folk_Knowledge/Priority_Field</a>, and you'll see how that varies. <br><br>When I checked how the Priority field was used in Firefox-related components, that distribution was:<span class=""><br><br><span style="font-family:monospace,monospace">--- 460,362<br></span><div class="gmail_default"><span style="font-family:monospace,monospace">P1 14,304<br></span></div><div class="gmail_default"><span style="font-family:monospace,monospace">P2 15,971<br></span></div><div class="gmail_default"><span style="font-family:monospace,monospace">P3 37,933<br></span></div><div class="gmail_default"><span style="font-family:monospace,monospace">P4 4,204<br></span></div><span style="font-family:monospace,monospace">P5 2,913<br><br></span></span>The bulk of bugs in Firefox-related components are P3, most likely because we have a bug filing form that defaults to P3 and that needs to be fixed if it's still in use.<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Having to make what seemed like snap-decisions on bugs was also a point of concern, but that's something the proposal had a work around for, using needinfo? to defer a triage decision on a bug until enough questions were answered. And since we made a commitment to make decisions on bugs, we need back pressure on untriaged bugs.<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">But from what I read, y'all are amenable to standardizing the priority flag's use in Triage. Doing that would create a discontinuity in historical data, but that's not an insurmountable problem, and we can document that breakage for researchers using historical data.<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">So next step is a second proposal, simplified, using Priority to represent triage decisions. <br><br>In addition, I'll want to remove several fields which are not useful, or superfluous from the bug entry wizards. Priority is a field that should be set by people triaging bugs, not entering them. We have a keyword vocabulary which is more expressive than severity. And our bug entry forms don't show the version affected, or the STR (steps to reproduce) flags which means it's an extra edit to get the information relman needs into a bug.<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Thank you again for your time and consideration as we make Bugzilla and Firefox better for everyone.<span class="HOEnZb"><font color="#888888"><br><br></font></span></div><span class="HOEnZb"><font color="#888888"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">-- Emma Humphries<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div></font></span><div class="gmail_extra"><div class="gmail_quote"><span class="">On Tue, Mar 29, 2016 at 1:07 PM, Emma Humphries <span dir="ltr"><<a href="mailto:emma@mozilla.com" target="_blank">emma@mozilla.com</a>></span> wrote:<br></span><div><div class="h5"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace"><h1 dir="ltr" style="line-height:1.38;margin-top:20pt;margin-bottom:6pt"><span style="font-size:26.6667px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline">tl;dr</span></h1><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:14.6667px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline">In Quarter Two I'm implementing the work we’ve been doing to improve triage, make actionable decisions on new bugs, and prevent us from shipping regressions in Firefox.</span></p><br><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:14.6667px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline">Today I’m asking for feedback on the plan which is posted at:</span></p><br><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><a href="https://docs.google.com/document/d/1FFrtS0u6gNBE1mxsGJA9JLseJ_U6tW-1NJvHMq551ko" style="text-decoration:none" target="_blank"><span style="font-size:14.6667px;font-family:Arial;color:rgb(17,85,204);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline">https://docs.google.com/document/d/1FFrtS0u6gNBE1mxsGJA9JLseJ_U6tW-1NJvHMq551ko</span></a></p><br><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:14.6667px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline">Allowing bugs to sit around without a decision on what we will do about them sends the wrong message to Mozillans about how we treat bugs, how we value their involvement, and reduces quality.</span></p><br><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:14.6667px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline">The Firefox quality team (myself, Mike Hoye, Ryan VanderMeulen, Mark Cote, and Benjamin Smedberg) want to make better assertions about the quality of our releases by giving you tools to make clear decisions about which bugs must be fixed for each release (urgent) and actively tracking those bugs.</span></p><h1 dir="ltr" style="line-height:1.38;margin-top:20pt;margin-bottom:6pt"><span style="font-size:26.6667px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline">What We Learned From The Pilot Program</span></h1><br><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:14.6667px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline">During the past 6 weeks, we have prototyped and tested a triage process with the DOM, Hello, and Developer Tools teams. </span></p><br><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:14.6667px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline">Andrew Overholt, who participated in the pilot for the DOM team, said, “A consistent bug triage process can help us spread the load of watching incoming bugs and help avoid issues falling through the cracks." </span></p><br><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:14.6667px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline">During the pilot, the DOM team uncovered critical bugs quickly so that people could be assigned to them.</span></p><br><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:14.6667px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline">The pilot groups also found that the triage process needs to be fast and have tooling to make going through bugs fast. It’s easy to fall behind on triage for a component, but if you stay up to date it will take no more than 15 minutes a day. </span></p><br><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:14.6667px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline">You can find the bugs we triaged during the pilot by looking for whiteboard tags containing ‘btpp-’.</span></p><br><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:14.6667px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline">It is also important to have consistent, shared definitions for regression across components so triagers do not waste effort on mis-labeled bugs.</span></p><h1 dir="ltr" style="line-height:1.38;margin-top:20pt;margin-bottom:6pt"><span style="font-size:26.6667px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline">Comments?</span></h1><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:14.6667px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline">I am posting this plan now for comment over the next week. I intend to finalize the triage plan for implementation by Tuesday, April 5th. Feedback and questions are welcome on the document, privately via email or IRC (where I’m emceeaich) or on the <a href="mailto:bugmasters@mozilla.org" target="_blank">bugmasters@mozilla.org</a> mailing list.</span></p><h1 dir="ltr" style="line-height:1.38;margin-top:20pt;margin-bottom:6pt"><span style="font-size:26.6667px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline">Timeline</span></h1><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:14.6667px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline">January: finish finding component responsible parties</span></p><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:14.6667px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline">February: pilot review of NEW bugs with four groups of components, draft new process</span></p><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:14.6667px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:700;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline">Now</span><span style="font-size:14.6667px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline">: comment period for new process, finalize process</span></p><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:14.6667px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline">Q2: implement new process across all components involved in shipping Firefox</span></p><span style="font-size:14.6667px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline">Q3: all newly triaged bugs following the new process<br><br></span></div><div class="gmail_default" style="font-family:monospace,monospace"><span style="font-size:14.6667px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline">-- Emma Humphries, Bugmaster<br></span></div></div>
</blockquote></div></div></div><br></div></div>
</blockquote></div><br></div>