From: "Tiziano Müller" <dev-zero@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [v4] Planning for automatic assignment computation of bugs
Date: Wed, 07 Jan 2009 07:01:07 +0100 [thread overview]
Message-ID: <1231308067.2013.36.camel@localhost> (raw)
In-Reply-To: <20090104180608.2e0935e5@epia.jer-c2.orkz.net>
[-- Attachment #1: Type: text/plain, Size: 1549 bytes --]
Am Sonntag, den 04.01.2009, 18:06 +0100 schrieb Jeroen Roovers:
> On Sun, 04 Jan 2009 17:02:21 +0000
> Mike Auty <ikelos@gentoo.org> wrote:
>
> > According to [1], "When the file lists multiple entries, then you
> > assign the bug to the first maintainer, and CC the other
> > maintainer(s) and herd(s)." So it looks as though the file should go
> > through the maintainers first and herds second? Should be pretty
> > easy to fix...
>
> I spotted that too but didn't remember putting it in black and white. :)
>
> The order ("first maintainer as assignee" or "first maintainer/herd as
> assignee") is open to discussion and I think this is the proper forum to
> have that discussion.
I'd say that the correct way to fix this is to fix the metadata schema
to be able to write something like this:
<maintainer>
<team>foo</team>
</maintainer>
<maintainer>
<dev>adev</dev>
</maintainer>
<maintainer>
<team>bar</team>
</maintainer>
or
<maintainer type="team">foo</maintainer>
<maintainer type="dev">adev</maintainer>
<maintainer type="team">bar</maintainer>
Because having to write this:
<herd>foo</herd>
<maintainer><email>adev@gentoo.org</email></maintainer>
<herd>bar</herd>
is just nonsense.
Cheers,
Tiziano
--
-------------------------------------------------------
Tiziano Müller
Gentoo Linux Developer
Areas of responsibility:
Samba, PostgreSQL, CPP, Python, sysadmin
E-Mail : dev-zero@gentoo.org
GnuPG FP : F327 283A E769 2E36 18D5 4DE2 1B05 6A63 AE9C 1E30
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-01-07 6:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 6:01 [gentoo-dev] [v4] Planning for automatic assignment computation of bugs Robin H. Johnson
2008-10-19 13:29 ` Robert Buchholz
2008-10-19 19:13 ` Robin H. Johnson
2008-10-19 13:47 ` Jeremy Olexa
2008-10-19 19:16 ` Robin H. Johnson
2008-10-19 13:49 ` Ulrich Mueller
2008-10-19 19:43 ` Robin H. Johnson
2008-10-19 19:51 ` Robin H. Johnson
2008-10-19 19:32 ` Alec Warner
2008-10-19 19:47 ` Robin H. Johnson
2008-11-13 20:22 ` Thilo Bangert
2008-11-13 6:04 ` Donnie Berkholz
2009-01-04 16:52 ` Robert Buchholz
2009-01-04 17:02 ` Mike Auty
2009-01-04 17:06 ` Jeroen Roovers
2009-01-04 17:15 ` Mike Auty
2009-01-04 17:57 ` Robert Buchholz
2009-01-04 18:12 ` Mike Auty
2009-01-06 12:54 ` Robin H. Johnson
2009-01-06 14:19 ` Mike Auty
2009-01-06 10:11 ` Peter Volkov
2009-01-07 7:53 ` [gentoo-dev] " Steve Long
2009-01-07 6:01 ` Tiziano Müller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1231308067.2013.36.camel@localhost \
--to=dev-zero@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox