unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: Drew Adams <drew.adams@oracle.com>
Cc: Xue Fuqiao <xfq.free@gmail.com>,
	John Wiegley <jwiegley@gmail.com>,
	Lars Ingebrigtsen <larsi@gnus.org>,
	Andrew Hyatt <ahyatt@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: Basic questions about the triage process
Date: Sat, 02 Jan 2016 22:37:57 +0100	[thread overview]
Message-ID: <87y4c7slvu.fsf@mbork.pl> (raw)
In-Reply-To: <b973c974-8be7-41cc-858e-7cad8e725fb7@default>

Hi,

I'm starting to work on bugs, too.

On 2015-12-29, at 02:50, Drew Adams <drew.adams@oracle.com> wrote:

>> > Yeah, if they're really old and aren't reproducing, closing them may be
>> > the right thing to do.
>> 
>> Andrew, I think your strategy is good, but can we turn that clock back to
>> two years? Emacs doesn't move all that rapidly. If you can't reproduce something
>> From 2013 or earlier, close it as cannot reproduce with a CC to the original
>> reporter. Otherwise, ping the submitter with a CC to the bug address saying
>> it can't be reproduced, but leave it open.
>
> FWIW, I disagree that there should be a 2-year limit, or any limit.
>
> If Emacs Dev has never responded to a bug report, no matter
> how old, then it should be treated as new.  If you cannot
> seem to reproduce it now then start by asking for more info -
> and not after closing it, just as you would do for a bug
> reported yesterday.
>
> If Emac Dev has responded previously, that's a different
> story.  But there is a giant backlog of bugs, and some of
> them are several years old (perhaps even many years old)
> and have never been responded to.
>
> What should count, if you must count time elapsed, is the
> time since the last attempt by a bug fixer to obtain info.
> If no one has ever tried, then the clock should be reset
> to zero.
>
> (Just one opinion.)

And another one, too - I agree with Drew on this

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University



  reply	other threads:[~2016-01-02 21:37 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-28  5:39 Basic questions about the triage process Andrew Hyatt
2015-12-28  8:58 ` Michael Albinus
2015-12-28 16:25   ` Andrew Hyatt
2015-12-28 17:35     ` Michael Albinus
2015-12-28 20:24 ` John Wiegley
2015-12-29  5:40   ` Andrew Hyatt
2015-12-29 17:12     ` Eli Zaretskii
2015-12-30  0:22       ` Andrew Hyatt
2015-12-30 17:21         ` Eli Zaretskii
2015-12-31  1:19           ` Noam Postavsky
2015-12-31  3:38             ` Eli Zaretskii
2015-12-31  9:06               ` Michael Albinus
2015-12-31 13:49                 ` Eli Zaretskii
2015-12-31 13:57                   ` Michael Albinus
2016-01-07 21:04     ` Phillip Lord
2016-01-07 22:05       ` Andy Moreton
2016-01-07 22:40         ` Phillip Lord
2016-01-09  3:46           ` Andrew Hyatt
2015-12-28 23:55 ` Xue Fuqiao
2015-12-29  0:38   ` Andrew Hyatt
2015-12-29  0:50     ` Lars Ingebrigtsen
2015-12-29  0:59       ` Andrew Hyatt
2015-12-29  1:07         ` Lars Ingebrigtsen
2015-12-29  1:21           ` John Wiegley
2015-12-29  1:50             ` Drew Adams
2016-01-02 21:37               ` Marcin Borkowski [this message]
2016-02-15 20:04                 ` Marcin Borkowski
2015-12-29  6:46             ` CHENG Gao
2015-12-29 15:50               ` Eli Zaretskii
2015-12-29 17:03         ` Nikolaus Rath
2015-12-29 17:16           ` John Wiegley
2015-12-29 17:50           ` Drew Adams
2015-12-29 23:36             ` Andrew Hyatt
2016-01-07 21:09               ` Phillip Lord
2016-01-07 21:28                 ` Lars Magne Ingebrigtsen
2016-01-09  3:47                   ` Andrew Hyatt
2016-01-09 20:56                     ` John Wiegley

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=87y4c7slvu.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --cc=ahyatt@gmail.com \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=jwiegley@gmail.com \
    --cc=larsi@gnus.org \
    --cc=xfq.free@gmail.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).