From: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Planning for automatic assignment of bugs
Date: Fri, 27 Apr 2007 09:04:40 -0400 [thread overview]
Message-ID: <fcaeb9bf0704270604p6d6fcdc9ga685209f51e14e1b@mail.gmail.com> (raw)
In-Reply-To: <46311AE3.70600@gentoo.org>
On 4/26/07, Joshua Jackson <tsunam@gentoo.org> wrote:
> Nguyen Thai Ngoc Duy wrote:
> > On 4/26/07, Robin H. Johnson <robbat2@gentoo.org> wrote:
> >> Case 2 - Metadata contains a single maintainer
> >> ----------------------------------------------
> >> - The herd field is not used.
> >> - The maintainer address is used as the bugzilla assignee.
> >> This is important for all the herds that have aliases that are NOT the
> >> same as their herd name!
> >> This diverges from existing manual practice, to avoid unnecessary
> >> duplicate mail, and means that existing metadata may need a cleanup.
> >
> > It should take devaway into account.
> >
> why? Seriously, dev-away != dev retired... having it take devaway into
> account is pointless in my opinion as it won't improve it being properly
> assigned...as it'll be covered in other cases, and its not like there's
> not bugs for all of us dev's that have not sat there for a month or so,
> at some point
I meant if a maintainer is away, his/her herd should be assignee with
him/her CCed.
--
Duy
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-04-27 13: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 [this message]
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
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=fcaeb9bf0704270604p6d6fcdc9ga685209f51e14e1b@mail.gmail.com \
--to=pclouds@gmail.com \
--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