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 Friday 12 March 2010 23:47:05 William Hubbs wrote:
> On Fri, Mar 12, 2010 at 08:11:50PM +0000, Jeremy Olexa wrote:
> > On Fri, 12 Mar 2010 21:18:03 +0200, Petteri R??ty <firstname.lastname@example.org>
> > 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.
> This is a good enough reason for me to vote for assigning bugs to
> maintainers and cc'ing arch teams. This is the way I was taught that
> this should be handled, and this comment explains why.
> Since all the arch team does is stabilize or keyword, the maintainer
> needs to know if other issues come up with the bug after it is closed.
I like that idea as well
Markos Chandras (hwoarang)
Gentoo Linux Developer