<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi all!<br>
<div class="moz-forward-container"> <br>
We have the Tempest Bug Triage Day this Thursday and there are a
few points to start digging and investigating from now on.<br>
<br>
First let me share the guidelines link (Openstack Wiki for Bug
Triage): <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://wiki.openstack.org/wiki/BugTriage">https://wiki.openstack.org/wiki/BugTriage</a><br>
<br>
Starting from that, there are a few issues and observations to
consider for discussion:<br>
<br>
1) Confirmed and Triaged status. There seems to not have a
consistency on those status, apparently being used as synonyms.
Any thoughts on how or if we should differ them?<br>
<br>
2) <a
href="https://bugs.launchpad.net/tempest/+bugs?search=Search&field.status%3Alist=NEW&assignee_option=none"
moz-do-not-send="true">New Bugs</a>. We have 116 (and growing)
new bugs to <b>prioritize, confirm and identify duplicates</b>. <b>This
is where the team needs to put most of the effort.</b><br>
There are also 5 <a
href="https://bugs.launchpad.net/tempest/+bugs?search=Search&field.status%3Alist=NEW&orderby=assignee"
moz-do-not-send="true">New bugs assigned </a>that should be
converted to Confirmed/ In Progress.<br>
<br>
3) Confirmed and Triaged bugs: <a
href="https://bugs.launchpad.net/tempest/+bugs?search=Search&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&orderby=assignee"
moz-do-not-send="true">13 assigned</a> should be changed to In
Progress if it makes sense or removed assignees. The other <a
href="https://bugs.launchpad.net/tempest/+bugs?search=Search&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&assignee_option=none"
moz-do-not-send="true">30 confirmed/triaged</a> should be
prioritized.<br>
<br>
4) <a
href="https://bugs.launchpad.net/tempest/+bugs?search=Search&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&assignee_option=none"
moz-do-not-send="true">4 In Progress/ Fix Committed</a> bugs
should not remain unassigned. Either have someone assigned or move
it back to Confirmed and ensure importance.<br>
<br>
5) Old bugs:<br>
* <a
href="https://bugs.launchpad.net/tempest/+bugs?search=Search&field.status=In%20Progress&orderby=date_last_updated"
moz-do-not-send="true">15 In Progress</a> with last update
comments in October. Assignees should verify if the status still
makes sense. If not, the bug may be moved back to
Confirmed/Invalid and prioritized accordingly.<br>
* <a
href="https://bugs.launchpad.net/tempest/+bugs?search=Search&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&orderby=date_last_updated"
moz-do-not-send="true">Confirmed/Triaged</a> : review
importances and assignees. Also look for duplicates.<br>
<br>
I think the focus on Thursday should be specially on item 2, but
also looking at 3. I'll start looking at those points and all the
help here is appreciated. The final goal is to have this process
well established to avoid getting a huge list of new bugs without
review.<br>
<br>
Please, all thoughts/opinions will be really appreciated.<br>
<br>
Best regards,
<pre class="moz-signature" cols="72">--
Adalberto Medeiros
Linux Technology Center
Openstack and Cloud Development
IBM Brazil
Email: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:adalbas@linux.vnet.ibm.com">adalbas@linux.vnet.ibm.com</a></pre>
<br>
</div>
<br>
</body>
</html>