Gentoo Archives: gentoo-dev

From: "Robin H. Johnson" <robbat2@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [v4] Planning for automatic assignment computation of bugs
Date: Sun, 19 Oct 2008 20:16:44
Message-Id: 20081019195100.GG21785@curie-int.orbis-terrarum.net
In Reply to: Re: [gentoo-dev] [v4] Planning for automatic assignment computation of bugs by "Robin H. Johnson"
1 On Sun, Oct 19, 2008 at 12:43:05PM -0700, Robin H. Johnson wrote:
2 > On Sun, Oct 19, 2008 at 03:49:35PM +0200, Ulrich Mueller wrote:
3 > > >>>>> On Sat, 18 Oct 2008, Robin H Johnson wrote:
4 > >
5 > > > 3. If you want the default assignment to go to a maintainer, and NOT
6 > > > the herd, move the <herd> element further down in the metadata.xml!
7 > >
8 > > I disagree about this point. IMHO the procedure described in
9 > > <http://www.gentoo.org/proj/en/qa/bug-wranglers/> makes more sense:
10 > >
11 > > # When the file [i.e., metadata.xml] lists multiple entries, then you
12 > > # assign the bug to the first maintainer, and CC the other
13 > > # maintainer(s) and herd(s).
14 > See now, here I disagree. If you review the v1 proposal, there was a LOT
15 > of resistance to your assignment procedure there, primarily from teams
16 > where this produced a lot of spam.
17 As an addenda, from v1, different teams and developers DO want different
18 behaviors:
19 1. Assign to herd, CC all others (eg: GNOME, base-system)
20 2. Assign to first maintainer, CC herd and others (eg: net-mail)
21
22 That was deliberately why I had logic about using the order in the
23 metadata.xml file, with the addition that later duplicate entries of an
24 email would override the first one.
25
26 Your generic rule of (assign to first non-herd maintainer, CC rest)
27 doesn't fit all of the cases.
28
29 --
30 Robin Hugh Johnson
31 Gentoo Linux Developer & Infra Guy
32 E-Mail : robbat2@g.o
33 GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85