From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Harald van Dijk" <truedfx@gentoo.org>
Subject: Re: [gentoo-dev] bug wrangler queue is large...
Date: Tue, 25 May 2010 16:25:44 -0400 [thread overview]
Message-ID: <201005251625.44819.vapier@gentoo.org> (raw)
In-Reply-To: <20100525200807.GA1515@boostbox>
[-- Attachment #1: Type: Text/Plain, Size: 1416 bytes --]
On Tuesday 25 May 2010 16:08:55 Harald van Dijk wrote:
> On Tue, May 25, 2010 at 03:33:33PM -0400, Mike Frysinger wrote:
> > On Tuesday 25 May 2010 14:46:01 Matti Bickel wrote:
> > > I wrangle bugs when there's a need and I'd
> > > like to hear what maintainers want to see on a bug assigned to them.
> > > If info is missing I usually ask for it and assign the bug anyway. If
> > > that's not wanted, let me know.
> >
> > i dont feel like this should go to the maintainer yet. if a report is
> > missing something that the maintainer needs, it isnt ready for them to
> > look at. so wranglers ask for it, leave it assigned to bug-wranglers,
> > and close as NEEDINFO. when (if) things become available, it can then
> > be re-opened and moved to the maintainer.
>
> No, don't close as NEEDINFO, mark as ASSIGNED. NEEDINFO bugs cannot be
> reopened by other users, even if they provide the requested information.
> NEEDINFO bugs are also easily forgotten about when the reporter forgets
> to reopen the bug him/herself.
and people on the wrangler alias see that traffic, so the state doesnt matter.
but i guess you're trying to cater to people who only scan the assigned list
rather than watching the e-mails sent to it.
> Plus, it's in the docs anyway.
then i guess i'll point this out to those who wrangle these things to
maintainers w/out following the docs. thanks.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-05-25 20:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 6:02 [gentoo-dev] bug wrangler queue is large Andreas K. Huettel
2010-05-25 18:24 ` Mike Frysinger
2010-05-25 18:46 ` Matti Bickel
2010-05-25 19:33 ` Mike Frysinger
2010-05-25 20:08 ` Harald van Dijk
2010-05-25 20:21 ` Matti Bickel
2010-05-25 20:25 ` Mike Frysinger [this message]
2010-05-25 21:40 ` Harald van Dijk
2010-05-26 3:08 ` Jeroen Roovers
2010-05-26 9:27 ` [gentoo-dev] " Duncan
2010-05-26 17:38 ` Alec Warner
2010-05-26 20:42 ` Jeroen Roovers
2010-07-15 22:50 ` Markos Chandras
2010-07-15 23:38 ` "Paweł Hajdan, Jr."
2010-07-19 18:01 ` Jeroen Roovers
2010-07-19 18:05 ` Alex Alexander
2010-07-19 18:08 ` Pacho Ramos
2010-05-25 21:06 ` [gentoo-dev] " Matti Bickel
2010-05-25 22:03 ` Mike Frysinger
2010-05-26 5:36 ` Graham Murray
2010-05-26 9:01 ` [gentoo-dev] " Duncan
2010-05-26 9:08 ` Matti Bickel
2010-05-26 3:05 ` [gentoo-dev] " Jeroen Roovers
2010-05-25 20:09 ` Matti Bickel
2010-05-26 3:02 ` Jeroen Roovers
2010-05-26 3:30 ` Jeroen Roovers
2010-05-26 7:42 ` Panagiotis Christopoulos
2010-05-25 19:33 ` Richard Freeman
2010-05-26 2:58 ` Jeroen Roovers
2010-05-26 4:25 ` Mike Frysinger
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=201005251625.44819.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=truedfx@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