Open Stack

On 12/13/2013 06:13 AM, Thierry Carrez wrote:
> Robert Collins wrote:
>> "
>> Confirmed The bug was reproduced or confirmed as a genuine bug
>> Triaged The bug comments contain a full analysis on how to properly
>> fix the issue
>> "
>>
>> From wiki.openstack.org/wiki/Bugs
>>
>> Putting aside the difficulty of complete reproduction sometimes, I
>> don't understand the use of Triaged here.
>>
>> In LP they mean:
>>
>> Confirmed Verified by someone other than the reporter.
>> Triaged     Verified by the bug supervisor.
>>
>> So our meaning is very divergent. I'd like us to consolidate on the
>> standard meaning - which is that the relative priority of having a
>> doctor [developer] attack the problem has been assessed.
> 
> I'm the one who established, a long time ago, this divergence between
> Launchpad's classic use of those statuses and OpenStack's. In my
> experience NOBODY ever uses "Confirmed" with the LP meaning, so I
> figured we should use it for something more useful: to describe how
> advanced you are in the resolution of the issue.
> 
> This is why I proposed (and we used) the following distinction, as
> described in https://wiki.openstack.org/wiki/BugTriage :
> 
> "Confirmed" bugs are genuine bugs but nobody really looked into the best
> way to fix them yet. They are confirmed, priority-assigned, tagged
> 
> "Triaged" bugs are bugs which are analyzed and have a clear way forward
> to resolve them, just missing someone to actually write the patch
> 
> That way developers could pick "ready to fix" bugs by searching
> "Triaged" bugs rather than "Confirmed" ones.
> 
>> Specifically:
>>  - we should use Triaged to indicate that:
>>     - we have assigned a priority
>>     - we believe it's a genuine bug
>>     - we have routed[tagged] it to what is probably the right place
>> [vendor driver/low-hanging-fruit etc]
>>  - we should use Incomplete if we aren't sure that its a bug and need
>> the reporter to tell us more to be sure
>>  - triagers shouldn't ever set 'confirmed' - thats reserved solely for
>> end users to tell us that more than one user is encountering the
>> problem.
> 
> I can see how that works for Ubuntu. But did you ever see, in OpenStack,
> an end user tell us that they /also encountered/ the problem ?
> 
> The end result of your proposal is that we stop using "Confirmed" and
> use "Triaged" instead (to describe the exact same thing). We lose the
> ability to use "Triaged" to indicate a "more analyzed" state. I'm not
> sure that's a net win, or worth asking anyone to change their habits, or
> worth changing the BugTriage wikipage (and/or any other page that
> repeated it).
> 
> I'll gladly admit that my meaning of "Triaged" was not used that much
> and that it could be replaced by something more useful. But merely using
> "triaged" for our old meaning of "confirmed" (and stop using
> "confirmed") sounds like change for the sake of change.

Agree with Thierry.

Yesterday was our giant bug triage day in Tempest, going from 276 to 74
open bugs in the process. And the things I learned in the process:

People are terrible at finding bugs that actually affect them. Honestly,
Launchpad search is terrible. I spent way too much time yesterday doing
dup squashing for bugs I knew I'd just seen, then taking 15 minutes to
find the base bug, or finally give up and just mark the bug as invalid
because I knew we were already tracking it, or it was already fixed.

So I like the current model, we just need to use it more. New goes to
Confirmed if someone is sure it's actually a problem, Incomplete if you
need more info from the person.

Triaged is for a bug that's got enough details in it that someone should
be able to just pick it up and run with it. Added bonus, if the
implementation notes are detailed enough, it can be put as
low-hanging-fruit so acts as a good on ramp task.

	-Sean

-- 
Sean Dague
http://dague.net

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 482 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131213/68505a1b/attachment.pgp>