Gentoo Archives: gentoo-dev

From: "Petteri Räty" <betelgeuse@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Handling of keywording bugs with only one arch
Date: Sat, 13 Mar 2010 17:08:58
Message-Id: 4B9BC65D.9000504@gentoo.org
In Reply to: Re: [gentoo-dev] Handling of keywording bugs with only one arch by Jeremy Olexa
On 03/12/2010 10:11 PM, Jeremy Olexa wrote:
> > On Fri, 12 Mar 2010 21:18:03 +0200, Petteri Räty <betelgeuse@g.o> > wrote: >> 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: >> http://bugs.gentoo.org/show_bug.cgi?id=272160#c5 >> Let's get agreed on a single approach and I will add a note here: >> http://devmanual.gentoo.org/keywording/index.html >> 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. > > -Jeremy >
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. Regards, Petteri

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies