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] Re: RFC Bugzilla interaction guide for devs & editbugs users
Date: Sat, 11 Sep 2010 15:43:35 +0200	[thread overview]
Message-ID: <20100911154335.6dfdfedd@epia.jer-c2.orkz.net> (raw)
In-Reply-To: <pan.2010.09.11.07.17.00@cox.net>

On Sat, 11 Sep 2010 07:17:01 +0000 (UTC)
Duncan <1i5t5.duncan@cox.net> wrote:

> Jeroen Roovers posted on Fri, 10 Sep 2010 18:32:38 +0200 as excerpted:
> 
> > If the reason you propose this is visibility, then maybe we should
> > make the quicksearch option include more than just open bugs. I've
> > thought about having UPSTREAM/DUPLICATE/INVALID added so that
> > bugzilla users can more easily discover whether a bug was already
> > reported and was deemed fixed, a duplicate of another bug or
> > canonically invalid.
> 
> I've wondered why quick-search didn't do ALL by default, myself.

Because it's never just right. We'd get even more people reopening bug
reports that were RESOLVED/FIXED years ago just because there's a
similarity in package/problem. Also, because you'd easily see a couple
of thousands of results listed. Just think of all the bugs filed with a
Summary of "fails to compile" or "emake failed" instead of something
specific, accurate, unique. Which is why we should all make an effort
to move away from the "firefox crashed" type of Summary, but that's an
never-ending battle as well.


     jer



  reply	other threads:[~2010-09-11 13:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-06  8:32 [gentoo-dev] RFC Bugzilla interaction guide for devs & editbugs users Robin H. Johnson
2010-09-06  8:39 ` Dirkjan Ochtman
2010-09-06 12:38   ` Alex Legler
2010-09-06 15:31   ` Michael Weber
2010-09-06 16:07     ` [gentoo-dev] " Christian Faulhammer
2010-09-06 21:24   ` Ryan Hill
2010-09-06 12:10 ` Christian Faulhammer
2010-09-06 12:36   ` Alex Legler
2010-09-07 20:47 ` [gentoo-dev] " Róbert Čerňanský
2010-09-07 21:30   ` Robin H. Johnson
2010-09-07 21:43     ` Andreas K. Huettel
2010-09-07 21:44     ` dev-random
2010-09-07 22:05       ` Pacho Ramos
2010-09-07 22:53         ` [gentoo-dev] " Duncan
2010-09-08  4:44           ` Ryan Hill
2010-09-10 16:32     ` [gentoo-dev] " Jeroen Roovers
2010-09-11  7:17       ` [gentoo-dev] " Duncan
2010-09-11 13:43         ` Jeroen Roovers [this message]
2010-09-11 21:58       ` [gentoo-dev] " Róbert Čerňanský

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=20100911154335.6dfdfedd@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