you can help triage bzr bugs

[Patrick Regan]

I am trying to help with this. I don't have access to be able to
change the importance of a bug. I can change the status, and the
assignee, but I can not change the importance. For example, I was
trying to triage bug 490770, and make it "high," but I have no access
to do so.

Is there something I'm missing? My guess right now is that by default
the Bazaar team has it set up that people can not change the
importance. Should there be a triage team who gets this access?

Pat

On 12/1/09, Robert Collins <robert.collins at canonical.com> wrote:
> On Tue, 2009-12-01 at 18:56 +1100, Martin Pool wrote:
>
> I think this is a good thing to do. I have a couple of key things I'd
> like anyone doing triage to be aware of.
>
>>  * See if you can find a duplicate, just by searching for a similar
>> message
>
> _Please_ look for a matching traceback. We have many bugs that can
> trigger the same symptoms but are genuinely different, and we can also
> have bugs that trigger from the same function but have different higher
> level call stacks. As Martin says, if you make a mistake, its not a big
> deal, we can undo 'mark as duplicate'. In Ubuntu, in some projects with
> similar properties to bzr, triagers often find this hard to do right. I
> suggest that if you are unsure, say 'I think this is a duplicate of
> XYZ', and let a developer assess it further.
>
>
>> Triage according to;
>>
>>  * critical: data loss or seriously broken functionality
>>  * high: blocks work for some people
>>  * low: otherwise
>
> I realise the following two items are a bit meta and not really related
> to the 'lets get more people caring about the bug tracker'. So if you're
> interested in QA feel free to ignore them :).
>
> My second point is about 'high' and 'low' here; we've previously been
> making a lot of bugs medium as a default, and I think we should keep
> doing that, otherwise we're just making newer bugs low because our
> process has changed, not because they've been compared and found less
> important.
>
> Finally, missing features shouldn't really be considered high, just
> because you can't do something without the feature. Generally I think we
> should make these 'wishlist', and if they happen to be something that a
> dev is working on, they could be either upgraded, or simply marked in
> progress.
>
>> I think it's realistic to expect we could fairly quickly get some
>> triagers who're often helping users faster than they are helped now,
>> letting developers fix more bugs, and rarely having any changes
>> undone.  If it works, it would be pretty cool.
>
> That would be cool.
>
> -Rob
>


-- 
Patrick Regan
Email: regan.patrick at gmail.com
Phone: (330) 576-4044