> mozilla handles it this way: the bug starts as unconfirmed. they have a
> volunteer group of pre screeners. Only when one of these people sets
> it to valid or similar then the owners of the module get mail.
>
>This sounds like a good idea.
Currently in the kernel bugzilla, after a bug is filed, it is initially
in the OPEN state -- this is similar to the Unconfirmed state mentioned
above. The screeners (my team and others who volunteer) can get rid of
many invalid bugs and dups. Only valid bugs then go to the ASSIGNED state
with correct owners. Of course, we do not expect to get rid 100% of all
the invalids and dups, but at least that should reduce the work of
the owners who should only work with bugs in the ASSIGNED state.
Also, the bug owner can close MULTIPLE bugs at the same time
on Bugzilla. A bug owner can query all of his bugs which will
then be displayed in a list, click the option "Change several bugs
at once" at the bottom of the list, select the bugs that he wants
to close, and then hit Commit button. It's pretty simple. Besides
closing the bugs, the owner can make similar changes to several bugs
at the same time using the same mechanism.
Regards,
Khoa
_________________________________________
Khoa Huynh, Ph.D.
IBM Linux Technology Center
(512) 838-4903; T/L 678-4903; khoa@us.ibm.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/