From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Planning for automatic assignment of bugs
Date: Fri, 27 Apr 2007 02:57:59 +0300 [thread overview]
Message-ID: <1177631880.26557.4.camel@ulla> (raw)
In-Reply-To: <20070426221651.GS7846@curie-int.orbis-terrarum.net>
On Thu, 2007-04-26 at 15:16 -0700, Robin H. Johnson wrote:
> On Thu, Apr 26, 2007 at 05:46:24PM -0400, Daniel Drake wrote:
> > Robin H. Johnson wrote:
> > > Case 2 - Metadata contains a single maintainer
> > > ----------------------------------------------
> > > - The herd field is not used.
> > > - The maintainer address is used as the bugzilla assignee.
> > At least for some packages I'm involved with, this will result in me
> > deleting myself from metadata.xml (but I'd rather not do so).
> >
> > I like these bugs to go to the herd, not me directly. I get the bug mail
> > anyway (I'm in the herd) but sometimes other herd members who see the mail
> > jump in and help resolve the bug, for which I'm very grateful.
> This is handled by a later case in the proposal.
> Simply interest a maintainer element with the herd email address, and
> add the contact=0 attribute to your maintainer element in the file.
>
> > That aside, I like having myself in the metadata alongside the herd, to
> > point out that I am the primary maintainer within the herd for the package
> > in question. It is also useful for others so that when they have questions
> > about the package, they know who to approach on IRC or whatever.
> This is exactly the reason that I proposed the contact=0 attribute - for
> some of the packages that I maintain, I do not want the bugs assigned
> directly to me, but to the herd instead. While for others I _do_ want
> the duplicate.
Could "contact" be named differently then?
contact=0 in metadata.xml in this context means that the automatic
reassigning should not assign to that maintainer, but when a user looks
whom to ask specific questions from and sees contact=0 he/she will
understand he/she is not to contact that person as the value is zero,
but Daniel wants them to contact precisely him in that case.
A different keyword might be better for that reason.
Good proposal otherwise!
I do have some reservations due to no human looking over new bugs
(before they get reassigned to a possibly otherwise busy maintainer), as
someone already has expressed, but we can always try it out and see how
it goes, I think.
Regards,
Mart Raudsepp
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-04-27 0:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 19:40 [gentoo-dev] Planning for automatic assignment of bugs Robin H. Johnson
2007-04-26 20:03 ` Robin H. Johnson
2007-04-26 20:23 ` Dan Meltzer
2007-04-26 21:17 ` expose
2007-04-26 21:24 ` Nguyen Thai Ngoc Duy
2007-04-26 21:34 ` Joshua Jackson
2007-04-26 21:53 ` expose
2007-04-27 13:04 ` Nguyen Thai Ngoc Duy
2007-04-27 13:16 ` Jakub Moc
2007-04-26 21:46 ` Daniel Drake
2007-04-26 22:01 ` expose
2007-04-26 22:16 ` Robin H. Johnson
2007-04-26 23:57 ` Mart Raudsepp [this message]
2007-04-27 0:24 ` Robin H. Johnson
2007-04-27 0:26 ` expose
2007-04-27 0:33 ` Danny van Dyk
2007-04-27 5:01 ` Robin H. Johnson
2007-04-27 8:32 ` Jan Kundrát
2007-04-27 17:51 ` Robin H. Johnson
2007-04-27 19:29 ` Jan Kundrát
2007-04-28 11:29 ` Flammie Pirinen
2007-04-27 12:01 ` expose
2007-04-27 17:55 ` Robin H. Johnson
2007-04-27 15:57 ` Ned Ludd
2007-04-27 17:57 ` Robin H. Johnson
2007-04-27 18:15 ` Matti Bickel
2007-04-27 19:04 ` Ned Ludd
2007-04-28 10:01 ` expose
2007-04-28 9:58 ` expose
2007-04-27 4:00 ` Andrej Kacian
2007-04-27 0:24 ` expose
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=1177631880.26557.4.camel@ulla \
--to=leio@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