From: "Diego Elio Pettenò" <flameeyes@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Quantity of open bugs
Date: Sat, 12 Mar 2011 15:45:34 +0100 [thread overview]
Message-ID: <1299941135.2212.94.camel@raven.home.flameeyes.eu> (raw)
In-Reply-To: <20110310202510.45627780@athlong2.kevquinn.com>
[-- Attachment #1: Type: text/plain, Size: 1637 bytes --]
Il giorno gio, 10/03/2011 alle 20.25 +0000, Kevin F. Quinn ha scritto:
>
> * Number of open bugs is greater than 14,000
For the record, about 10% of those are reported by me through tinderbox
(1506 open bugs reported by me as of today). A number of those date back
in 2008 and earlier, and could be fixed reasonably quickly if the
packages were maintained. And no, me or any other number of people going
through to fix just those is not feasible, see my old post at [1] for
some reasons.
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:
- makes it harder to see whether the package has any maintainer at all;
- would waste my time as I'd be re-opening the same exact bug at the
following tinderbox iteration, as the original bug was closed (and no, I
wouldn't go _reopening_ the bug, since I wouldn't remember there was one
already most of the time, so the load on bugzilla would increase).
So if somebody would still have doubts about this, I think the point is
vetoed to close bugs without action as WONTFIX after any time at all.
Rather get rid of the package in that case. And you can challenge that
with the council if you wish as I'm weighting that in as part of QA,
thank you very much.
OTOH if a bug is waiting for user to report build logs or other kind of
test results, closing as TEST-REQUEST or NEEDINFO is likely a good idea.
[1] http://blog.flameeyes.eu/2009/12/28/the-five-minutes-fix-myth
--
Diego Elio Pettenò — Flameeyes
http://blog.flameeyes.eu/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-03-12 14:48 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 ` Diego Elio Pettenò [this message]
2011-03-12 17:09 ` [gentoo-dev] " Donnie Berkholz
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=1299941135.2212.94.camel@raven.home.flameeyes.eu \
--to=flameeyes@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