From: Dan Nicolaescu <dann@gnu.org>
To: Karl Fogel <kfogel@red-bean.com>
Cc: emacs-devel@gnu.org
Subject: Re: Bug statistics
Date: Thu, 24 Jun 2010 21:28:19 -0400 [thread overview]
Message-ID: <yxq8w63dhos.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <874ogsthn2.fsf@red-bean.com> (Karl Fogel's message of "Thu\, 24 Jun 2010 14\:22\:41 -0400")
Karl Fogel <kfogel@red-bean.com> writes:
> Richard Stallman <rms@gnu.org> writes:
>> 4594 reports [1]
>> 2647 closed reports
>>
>>Amost 2000 bug reports not closed
>>is rather disturbing.
>>
>> 14% have been marked "minor"
>> 20% have been marked "wishlist"
>> 9% are tagged "moreinfo"
>> 5% are tagged "wontfix".
>>
>>That is about 40%. It seems to imply there are around 1200 bug
>>reports which are not marked in these ways, and not fixed either.
>>Is that true?
>>
>>Can you compute the number of bug reports that are waiting for action
>>by the maintainers?
>
> Percentage of bug reports not closed is not in itself a problem. It's
> possible that bugs-not-triaged is a problem, but that really depends on
> many things about the project.
>
> http://ostatic.com/blog/fixing-the-perception-of-bugs
>
> (And yes, I'm quoting someone quoting me in order to give my opinions
> more authority. :-) )
>
> IMHO the poor web interface of our bug tracker is an impediment to
> finding and triaging bugs. Heck, I can't even find the tracker half the
> time. If I start at http://gnu.org/software/emacs and click on the link
> to [what is purported to be] the Emacs bug database, I am taken to the
> generic top of the Gnu tracker: http://debbugs.gnu.org/. Then there is
> a table there, with a row for Emacs. Since what I want to do is search
> the Emacs bug database, I take the closest option to that, which is the
> "Browse bug reports" column with its cell for "Emacs reports". Clicking
> on that brings me to:
>
> http://debbugs.gnu.org/cgi/pkgreport.cgi?package=emacs;max-bugs=100;base-order=1;bug-rev=1
Although the debbugs UI is far from ideal, do you have any evidence
that is one of the more important problems?
IMO the main problem is man power.
There are >100 bugs with patches attached that have not been applied.
For a lot of these patches there's no obvious maintainer to take care
of them, so one of the maintainers would have to do it.
Same goes about bug reports, quite a few are about areas that nobody
feels particularly attached to, so they don't get any action.
next prev parent reply other threads:[~2010-06-25 1:28 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 20:41 Bug statistics Glenn Morris
2010-06-23 21:48 ` Dan Nicolaescu
2010-06-23 23:46 ` Glenn Morris
2010-06-24 15:40 ` Richard Stallman
2010-06-24 17:59 ` Tassilo Horn
2010-06-25 10:24 ` Eli Zaretskii
2010-06-25 11:07 ` Tassilo Horn
2010-06-25 20:16 ` Chong Yidong
2010-06-26 0:48 ` Stephen J. Turnbull
2010-06-25 21:31 ` Karl Fogel
2010-06-26 8:53 ` Eli Zaretskii
2010-06-26 9:28 ` Tassilo Horn
2010-06-26 10:37 ` Eli Zaretskii
2010-06-26 19:38 ` Karl Fogel
2010-06-25 18:37 ` Richard Stallman
2010-06-26 1:18 ` Stephen J. Turnbull
2010-06-24 18:22 ` Karl Fogel
2010-06-24 18:34 ` Glenn Morris
2010-06-24 19:07 ` Karl Fogel
2010-06-24 19:21 ` Glenn Morris
2010-06-24 19:26 ` Karl Fogel
2010-06-25 1:28 ` Dan Nicolaescu [this message]
2010-06-25 1:40 ` Karl Fogel
2010-06-25 1:57 ` debbugs search output [was Re: Bug statistics] Glenn Morris
2010-06-25 2:03 ` debbugs search output Glenn Morris
2010-06-25 3:02 ` Karl Fogel
2010-07-03 13:19 ` Michael Albinus
2010-07-03 14:34 ` Chong Yidong
2010-07-03 18:36 ` Michael Albinus
2010-06-25 8:55 ` Bug statistics Yoni Rabkin
2010-06-25 10:27 ` Eli Zaretskii
2010-06-25 20:23 ` Chong Yidong
2010-06-26 8:55 ` Eli Zaretskii
2010-06-26 19:58 ` Chong Yidong
2010-06-26 14:09 ` Richard Stallman
2010-06-25 21:01 ` Dan Nicolaescu
2010-06-26 12:22 ` Eli Zaretskii
2010-06-26 14:14 ` Stephen J. Turnbull
2010-06-27 19:38 ` Eli Zaretskii
2010-06-27 20:25 ` Andreas Schwab
2010-06-24 18:26 ` Glenn Morris
2010-06-25 5:47 ` Stephen J. Turnbull
2010-06-26 14:09 ` Richard Stallman
2010-06-26 16:43 ` Stephen J. Turnbull
2010-06-27 21:09 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2019-10-20 19:32 Eli Zaretskii
2019-10-20 20:15 ` Lars Ingebrigtsen
2019-10-21 6:17 ` Eli Zaretskii
2019-10-21 7:24 ` Michael Albinus
2019-10-21 11:05 ` Lars Ingebrigtsen
2019-10-21 11:20 ` Eli Zaretskii
2019-10-21 12:26 ` Stefan Monnier
2019-10-21 13:04 ` Lars Ingebrigtsen
2019-10-21 13:50 ` Michael Albinus
2019-10-21 13:54 ` Lars Ingebrigtsen
2019-10-21 14:19 ` Michael Albinus
2019-10-21 14:32 ` Michael Albinus
2019-10-21 17:12 ` Lars Ingebrigtsen
2019-10-21 14:38 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yxq8w63dhos.fsf@fencepost.gnu.org \
--to=dann@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).