Bug Triage Privileges
daniel.holbach at ubuntu.com
Mon Sep 11 07:27:25 BST 2006
Am Sonntag, den 10.09.2006, 22:30 -0500 schrieb Rocco Stanzione:
> When I say "triage" I refer to setting the importance of a bug, which I was
> sure until recently was the same thing.
To triage is much more than that. Triaging a bug is
* making sure all information is available (version number, debug
backtrace, test case to reproduce, ...)
* make sure it's no duplicate
* the right people subscribed to it
* it's maybe forwarded upstream
> Still more wiki pages and docs
> explain how to triage correctly, but none (that I could find) indicate how to
> get those privileges.
This should indeed be documented.
> When I found out that it was restricted to -qa
> (and -dev and -core-dev), I inquired about getting membership in -qa and was
> told that it was a very elite group.
I'm not sure who told you that, but it's not true. For this group we
make sure that team members are known as Bug Triagers already and know
what they do. Simon Law and I are Administrators of that team -
although he set it up and I leave the task mostly to him and look after
the 'bugsquad' team myself.
It's useful to set a bug importance, sure - but my observation is that
it takes a while until people stop seeing their bug as critical - which
is not really useful.
If we can improve the process, I'm all ears to how to do so.
Have a nice day,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20060911/d94e9a0f/attachment.pgp
More information about the ubuntu-devel