From: Thomas Kahle <tomka@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Quantity of open bugs
Date: Fri, 11 Mar 2011 15:13:38 +0100 [thread overview]
Message-ID: <20110311141338.GW3732@denkmatte.Speedport_W_502V_Typ_A> (raw)
In-Reply-To: <20110310202510.45627780@athlong2.kevquinn.com>
[-- Attachment #1: Type: text/plain, Size: 2166 bytes --]
On 20:25 Thu 10 Mar , Kevin F. Quinn wrote:
> Hi all,
>
> I was nosing through bugzilla, and noticed:
>
> * Number of open bugs is greater than 14,000
> * Number of open bugs untouched for more than 2 years - well over 2000.
> * Number of open bugs untouched between 1 and 2 years - well over 2000.
> * Number of open bugs untouched between 6 months and 1 year - well over
> 2000.
> * Number of open bugs untouched between 3 months and 6 months - over
> 2000
>
> The winner is bug #78406, which hasn't been touched for over 2240 days
> - over 6 years - at the time of writing.
>
> I would guess these old untouched bugs aren't actually going to be
> touched, ever - a lot simply won't be relevant any more for one reason
> or another. All they're doing is cluttering up bugzilla.
>
>
> So I'd like to suggest a drastic, perhaps controversial action. Mark
> all bugs that haven't been touched for over (say) 3 months as
> "Resolved:Wontfix", with a polite comment saying that it is closed due
> to lack of resource amongst the volunteer developer community.
I do come back to bugs after years. They should not be closed if they
are not fixed. "WONTFIX" for me means that there was a decision made
that this will not be fixed, but that is not the case.
+1 for the argument that 14000 open bugs is not a problem. Bugzilla is
not something that needs to be clean and tidy. Closing them would
generate a lot of work because of false positive while there is zero
benefit.
Cheers,
Thomas
> sure a suitable bugzilla script wiz could do that relatively easily.
> Users who care about such bugs can still comment on them, or talk
> directly to the assigned dev to highlight it's still a relevant issue
> to them, or even to supply a solution against the current tree.
>
> It could be an ongoing policy, in which case, users who care about
> them can keep bugs alive simply by posting useful updates to the bug,
> describing how the issue still applies to a new revision for example.
>
> Just a thought from an old ex-dev...
>
> Kev.
>
>
>
--
Thomas Kahle
http://dev.gentoo.org/~tomka/
[-- Attachment #2: Type: application/pgp-signature, Size: 316 bytes --]
next prev parent reply other threads:[~2011-03-11 14:13 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 [this message]
2011-03-12 14:45 ` [gentoo-dev] " Diego Elio Pettenò
2011-03-12 17:09 ` 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=20110311141338.GW3732@denkmatte.Speedport_W_502V_Typ_A \
--to=tomka@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