[openstack-dev] [bugs] definition of triaged
dolph.mathews at gmail.com
Thu Dec 12 22:39:50 UTC 2013
On Thu, Dec 12, 2013 at 3:46 PM, Robert Collins
<robertc at robertcollins.net>wrote:
> Hi, I'm trying to overhaul the bug triage process for nova (initially)
> to make it much lighter and more effective.
> I'll be sending a more comprehensive mail shortly but one thing that
> has been giving me pause is this:
> 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.
> - 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
++ that's exactly how I use it, with some emphasis on "believe" which I use
to differentiate from this from "Confirmed" ...
> [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
As a "triager", if I put my user hat on and am able to reproduce a bug,
I'll mark Confirmed, otherwise it's just Triaged.
> Robert Collins <rbtcollins at hp.com>
> Distinguished Technologist
> HP Converged Cloud
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev