Joshua Jackson wrote: > Nguyen Thai Ngoc Duy wrote: > > On 4/26/07, Robin H. Johnson <[EMAIL PROTECTED]> wrote: > >> Case 2 - Metadata contains a single maintainer > >> ---------------------------------------------- > >> - The herd field is not used. > >> - The maintainer address is used as the bugzilla assignee. > >> This is important for all the herds that have aliases that are NOT the > >> same as their herd name! > >> This diverges from existing manual practice, to avoid unnecessary > >> duplicate mail, and means that existing metadata may need a cleanup. > > > > It should take devaway into account. > > why? Seriously, dev-away != dev retired... having it take devaway into > account is pointless in my opinion as it won't improve it being properly > assigned...as it'll be covered in other cases, and its not like there's > not bugs for all of us dev's that have not sat there for a month or so, > at some point I think it is important that someone has a look at the bugs submitted. For instance, a submitter might not behave correctly, and submit a security issue to Gentoo Linux instead of Gentoo Security. Or the submitter does not even recognize it is a security issue, or might be or become one. In that case the bug would sit there until the dev it was automatically assigned to is back again (which could take quite some time).
Another (minor) reason, might be, that bugs could be assigned to the wrong person, because of whatsoever reason, and that dev is unavailable. This bug would sit there and wait to be reassigned until the dev comes back, who will reassign it to the correct dev, who in turn will mark it as "dublicate" because someone else useing the correct format for the summary submitted it yet and the submitter of our first bug feels demotivated :-) Maybe it is for those and similar reasons which can easily be made up better to leave bugs which would otherwise be automatically assigned to devs which are unavailable to the bug-wranglers, or maybe better: Automatically assign but manually review them to emulate the first glance the unavailable dev would have taken. Obviously, there should not be too many bugs which would be automatically assigned to developers which are away anyway. -- [EMAIL PROTECTED] mailing list
