From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: How does the Emacs bug tracker work?
Date: Thu, 30 Jun 2011 22:25:26 -0400 [thread overview]
Message-ID: <jwvhb76lp3z.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m3r56bko98.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 30 Jun 2011 23:22:59 +0200")
> So "closed" is mainly a way to say "I probably don't normally want to
> have these included in my searches". So moving three year old
> "wontfix"-es over to "closed" means taking less time searching for the
> bugs you want to look at.
No, in my experience what I want to include in my searches depends a lot
on what I'm doing. If I'm searching for duplicates, I want to include
pretty much all previous bugs no matter what, and if I'm looking for
"bugs that need love" I don't want to include any wontfix, regardless of
their age.
IOW, I don't find the notion of "closed" to be useful.
>> The bad ones are "untriaged", "forgotten" and "ready", so we should come
>> up with a way to distinguish inprogress from untriaged, as well as a way
>> to mark the forgotten ones as well, so we can ask debbugs to show us
>> these ones.
> If `date' is the same as `log-modified', it means that nobody has
> responded to the bug. This can't be searched for, but can be
> highlighted in the debbugs buffer.
Rather than highlight, I'd like to see them sorted first, but yes, that
should be good enough.
>> I guess we could add "inprogress" and "forgotten" tags and then try to
>> be careful to add "inprogress" whenever we first reply to a bug report.
>> Then have some cron job check all the "inprogress" bugs and turn them
>> into "forgotten" after some pre-defined delay (at which point humans
>> way come and relabel it to "moreinfo" if the delay is not our fault).
> Adding these tags aren't really necessary if using the debbugs.el
> interface. An "inprogress" report is one that has gotten at least one
> reply lately,
OK.
> and "forgotten" would be one where the reply is old.
OK (except if it's marked "moreinfo", of course).
> So this can be controlled client-side. If you don't consider 30 seconds
> being too slow to get the complete list of bugs over to Emacs.
Sounds fine,
Stefan
next prev parent reply other threads:[~2011-07-01 2:25 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 0:07 How does the Emacs bug tracker work? Lars Magne Ingebrigtsen
2011-06-30 0:32 ` Glenn Morris
2011-06-30 0:56 ` Lars Magne Ingebrigtsen
2011-06-30 5:00 ` Dan Nicolaescu
2011-06-30 9:09 ` Lars Magne Ingebrigtsen
2011-06-30 9:16 ` Julien Danjou
2011-06-30 9:32 ` Lars Magne Ingebrigtsen
2011-06-30 10:14 ` Bastien
2011-06-30 10:54 ` Julien Danjou
2011-06-30 9:39 ` Andreas Schwab
2011-06-30 9:40 ` Deniz Dogan
2011-06-30 13:04 ` Jason Rumney
2011-06-30 13:05 ` Deniz Dogan
2011-06-30 13:47 ` Juanma Barranquero
2011-06-30 14:35 ` Julien Danjou
2011-06-30 14:40 ` Juanma Barranquero
2011-06-30 14:44 ` Lars Magne Ingebrigtsen
2011-06-30 19:56 ` Stefan Monnier
2011-06-30 21:22 ` Lars Magne Ingebrigtsen
2011-07-01 2:25 ` Stefan Monnier [this message]
2011-07-01 10:00 ` Lars Magne Ingebrigtsen
2011-07-01 11:24 ` Michael Albinus
2011-07-01 15:24 ` Chong Yidong
2011-07-01 16:01 ` Drew Adams
2011-07-01 16:57 ` Lars Magne Ingebrigtsen
2011-07-01 17:16 ` Glenn Morris
2011-07-01 16:38 ` Michael Albinus
2011-07-01 0:18 ` Richard Stallman
2011-06-30 15:15 ` Chong Yidong
2011-06-30 16:30 ` Lars Magne Ingebrigtsen
2011-06-30 18:04 ` Glenn Morris
2011-06-30 20:54 ` Michael Albinus
2011-07-01 23:02 ` Glenn Morris
2011-07-02 11:23 ` Michael Albinus
2011-07-02 12:42 ` Lars Magne Ingebrigtsen
2011-07-02 12:57 ` Michael Albinus
2011-07-02 13:00 ` Lars Magne Ingebrigtsen
2011-07-02 13:21 ` Michael Albinus
2011-07-02 18:05 ` Glenn Morris
2011-07-02 20:04 ` Chong Yidong
2011-07-02 23:38 ` Michael Albinus
2011-07-02 18:03 ` Glenn Morris
2011-07-02 18:46 ` Michael Albinus
2011-07-02 20:19 ` Lars Magne Ingebrigtsen
2011-07-02 20:28 ` Michael Albinus
2011-07-02 22:25 ` Glenn Morris
2011-07-02 22:29 ` Lars Magne Ingebrigtsen
2011-07-02 22:42 ` Glenn Morris
2011-07-06 18:39 ` Lars Magne Ingebrigtsen
2011-07-06 20:05 ` Glenn Morris
2011-07-06 20:26 ` Lars Magne Ingebrigtsen
2011-07-01 6:55 ` Glenn Morris
2011-07-01 11:39 ` Richard Stallman
2011-06-30 16:32 ` Juanma Barranquero
2011-07-01 1:03 ` Stephen J. Turnbull
2011-07-01 11:08 ` Juanma Barranquero
2011-07-01 11:48 ` Lars Magne Ingebrigtsen
2011-07-01 12:18 ` Juanma Barranquero
2011-07-01 12:40 ` Lars Magne Ingebrigtsen
2011-07-01 12:51 ` Stephen J. Turnbull
2011-07-01 12:57 ` Juanma Barranquero
2011-07-01 13:02 ` Lars Magne Ingebrigtsen
2011-07-01 13:25 ` Michael Albinus
2011-07-01 15:27 ` Julien Danjou
2011-07-01 16:24 ` Lars Magne 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=jwvhb76lp3z.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--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).