public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jeroen Roovers <jer@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] metdata.dtd should require <herd/>
Date: Thu, 24 Dec 2009 17:12:22 +0100	[thread overview]
Message-ID: <20091224171222.3f4c5dc7@epia.jer-c2.orkz.net> (raw)
In-Reply-To: <4B336086.2000108@gentoo.org>

On Thu, 24 Dec 2009 07:37:26 -0500
Richard Freeman <rich0@gentoo.org> wrote:

> I think we should definitely have some way of designating which
> should be the contact for bugs.  I've had some bugs sit around for a
> while without being noticed because they were assigned to the herd
> the package is in, and not to me personally, and I don't generally
> work with that herd, and the project associated with the herd doesn't
> generally maintain the package.

That means the bug wasn't properly assigned... I've set up some rules
[1] that might help there. It comes down to this:

1) If one or more <maintainer> tags are listed, assign to the first one
mentioned.
2) If no <maintainer> tag is listed, assign to the first <herd>
mentioned.
3) CC everyone else listed (<maintainer>s and <herd>s).

The rationale is that if one or more <maintainer>s are listed as well as
one or more <herd>s, a bug wrangler shouldn't need to go find out if
that maintainer happens to be on the <herd>'s alias as well (otherwise,
why would it mention those maintainers separately?).

The order in which <maintainer> and <herd> tags are listed isn't
special, because <maintainer> goes before <herd> for the reason set out
above. The order of multiple <maintainer> tags (or multiple <herd> tags)
does matter: the first one you find is the Assignee, the others are
CC'd.


Regards,
     jer


[1] http://www.gentoo.org/proj/en/qa/bug-wranglers/index.xml#doc_chap4



      reply	other threads:[~2009-12-24 18:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07 11:56 [gentoo-dev] irregular metdata.xml check Thilo Bangert
2009-12-07 12:13 ` Ulrich Mueller
2009-12-07 13:20   ` Thilo Bangert
2009-12-07 17:04 ` Hans de Graaff
2009-12-07 20:20   ` Thilo Bangert
2009-12-15 15:19     ` [gentoo-dev] metdata.dtd should require <herd/> Peter Volkov
2009-12-15 17:16       ` Alex Alexander
2009-12-15 17:27       ` Mike Frysinger
2009-12-15 17:48       ` [gentoo-dev] " Jonathan Callen
2009-12-16  6:49       ` [gentoo-dev] " Rémi Cardona
2009-12-23 18:36         ` Paul de Vrieze
2009-12-24 12:37           ` Richard Freeman
2009-12-24 16:12             ` Jeroen Roovers [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=20091224171222.3f4c5dc7@epia.jer-c2.orkz.net \
    --to=jer@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