unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: emacs-devel@gnu.org
Subject: Bug statistics
Date: Sun, 20 Oct 2019 22:32:25 +0300	[thread overview]
Message-ID: <83lftf43hy.fsf@gnu.org> (raw)

Does debbugs*.el support compiling statistics about our bugs?  Like
how many new bugs were reported and how many were closed during a
given period of time, including distribution by severity?

I think it might make sense to have such a feature, and perhaps even
post the statistics from time to time, so that we know how we are
doing on that front.

Does it make sense?  Would someone like to work on this?

TIA



             reply	other threads:[~2019-10-20 19:32 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-20 19:32 Eli Zaretskii [this message]
2019-10-20 20:15 ` Bug statistics 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
  -- strict thread matches above, loose matches on Subject: below --
2010-06-23 20:41 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
2010-06-25  1:40       ` Karl Fogel
2010-06-25  8:55       ` 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

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=83lftf43hy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.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.
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).