<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 9/11/2012 1:47 PM, Mike Conley
wrote:<br>
</div>
<blockquote cite="mid:504F8743.2060408@mozilla.com" type="cite">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
All,<br>
<br>
I took minutes during the TB QA meeting at MozCamp.<br>
<br>
Minutes can be found here starting on line 18:<br>
<a moz-do-not-send="true"
href="https://etherpad.mozilla.org/tb-qa"><br>
https://etherpad.mozilla.org/tb-qa</a><br>
<br>
Here's a summary:<br>
<br>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div class="" id="magicdomid306"><span
class="author-g-fp2xkcspz122zccid7qs b"><b>Summary</b></span></div>
<div class="ace-line" id="magicdomid4217">
<ul class="list-bullet1">
<li><span class="author-g-fp2xkcspz122zccid7qs">The rapid
release has really changed the way we do testing.
Community involvement has dropped off.</span></li>
</ul>
</div>
<div class="ace-line" id="magicdomid4219">
<ul class="list-bullet1">
<li><span class="author-g-fp2xkcspz122zccid7qs">Ludo has no
chance of watching all of Bugzilla, and sometimes somebody
comes in with a patch, and we don't see it because they
don't set the right flags, and then it gets bitrotted and
we lose a potential contributor.</span></li>
</ul>
</div>
</blockquote>
One of the more recent bmo changes allowed more people to access
whines... if we can construct a query for all new patches without
reviewers (given Bugzilla, this might not be possible), it should be
simple enough just to have someone get whined for this sort of
stuff.<br>
<blockquote cite="mid:504F8743.2060408@mozilla.com" type="cite">
<div class="ace-line" id="magicdomid4219">
<ul class="list-bullet1">
</ul>
</div>
<div class="ace-line" id="magicdomid4191"><span
class="author-g-fp2xkcspz122zccid7qs b"><b>Action items</b></span></div>
<ol>
<li><span class="author-g-fp2xkcspz122zccid7qs">Get a list of
people watching each TB component, and make sure we've got
somebody with eyes on each one.</span></li>
<li><span class="author-g-fp2xkcspz122zccid7qs">We're going to
tackle the Papercuts list (10 bugs) to prove that we can
deal with a list.</span></li>
<li><span class="author-g-fp2xkcspz122zccid7qs">rkent(?) is
going to send out a weekly status report on the Papercuts
list, and what needs fixing, on what got fixed.</span></li>
</ol>
</blockquote>
I was under the impression that the weekly status report on The List
was going to be managed by QA / Support. It's also not clear who
will be receiving the status report on The List.<br>
<blockquote cite="mid:504F8743.2060408@mozilla.com" type="cite">
<ol start="4">
<li><span class="author-g-fp2xkcspz122zccid7qs">When the list is
empty, or close to being empty, QA is going to develop a
process for creating the list (which includes the facility
for devs to indicate that a bug is too difficult).</span></li>
<li><span class="author-g-fp2xkcspz122zccid7qs">We need to come
up with some critiera for choosing bugs like the ones on
Papercuts. Then QA / Support will build the list.</span></li>
</ol>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Joshua Cranmer
News submodule owner
DXR coauthor</pre>
</body>
</html>