From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Quantity of open bugs
Date: Sat, 12 Mar 2011 11:09:44 -0600 [thread overview]
Message-ID: <20110312170944.GA15228@comet> (raw)
In-Reply-To: <1299941135.2212.94.camel@raven.home.flameeyes.eu>
[-- Attachment #1: Type: text/plain, Size: 736 bytes --]
On 15:45 Sat 12 Mar , Diego Elio Pettenò wrote:
> I actually use the fact that these are still open to judge whether a
> package has to be removed from the tree, closing them would definitely
> be a bad idea for two reasons:
I'm assuming you're talking only about broken builds here and not
"QA-only" bugs. My opinion is that if a tinderbox QA script is the only
thing finding a nonfatal bug, and it's never reported or CC'd by a user,
then it's about as low priority as you can get.
So this might serve as a pointer to potentially unmaintained packages,
but clearly more investigation is required before removal.
--
Thanks,
Donnie
Donnie Berkholz
Sr. Developer, Gentoo Linux
Blog: http://dberkholz.com
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-03-12 17:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110307130425.3C1ED1C042@pigeon.gentoo.org>
2011-03-10 20:25 ` [gentoo-dev] Quantity of open bugs Kevin F. Quinn
2011-03-10 21:03 ` [gentoo-dev] " Duncan
2011-03-10 21:33 ` [gentoo-dev] " Chris Richards
2011-03-11 4:46 ` [gentoo-dev] " Ryan Hill
2011-03-11 8:07 ` [gentoo-dev] " Alec Warner
2011-03-11 8:25 ` George Prowse
2011-03-11 14:13 ` Thomas Kahle
2011-03-12 14:45 ` [gentoo-dev] " Diego Elio Pettenò
2011-03-12 17:09 ` Donnie Berkholz [this message]
2011-03-12 17:16 ` [gentoo-dev] " Diego Elio Pettenò
2011-03-16 4:17 ` [gentoo-dev] " Jeroen Roovers
2011-03-16 9:46 ` [gentoo-dev] " Tomáš Chvátal
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=20110312170944.GA15228@comet \
--to=dberkholz@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