List Archive: gentoo-dev
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
On 03/12/2010 10:11 PM, Jeremy Olexa wrote:
> On Fri, 12 Mar 2010 21:18:03 +0200, Petteri Räty <firstname.lastname@example.org>
>> There seems to be two different schools on who to assign a keywording
>> bug with only a single arch. I have myself assigned it to the arch in
>> question but there's a difference of opinion here:
>> Let's get agreed on a single approach and I will add a note here:
>> I naturally support the approach I have been doing as I think the arch
>> team is the one in charge.
> The "problem" with assigning bugs to arch teams is when the user comments
> on the bug after it is resolved. If the arch team is CC'd, they remove
> themselves when done and any comments after the bug is closed goes to
> someone that is interested. If the arch team is assigned, then the comment
> basically goes to /dev/null. So, if we are to improve the user experience,
> assign to maintainer and CC arch team.
When a bug is marked as fixed it doesn't show up in searches developers
use so it's a matter of who reads the email and acts upon it. I don't
see why maintainers would be any more likely to act than an arch team
comprised of multiple people in the case of bigger arches. Let's not
forget that users are really supposed to open new bugs instead of
commenting on the resolved ones although I know there are users out
there who rather comment on a two year old only distantly related bug
than open a new one.