unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: CHENG Gao <chenggao@royau.me>
To: emacs-devel@gnu.org
Subject: Re: Basic questions about the triage process
Date: Tue, 29 Dec 2015 14:46:48 +0800	[thread overview]
Message-ID: <m2fuyloip3.fsf@royau.me> (raw)
In-Reply-To: m21ta6canh.fsf@newartisans.com

*On Mon, 28 Dec 2015 17:21:22 -0800
* Also sprach John Wiegley <jwiegley@gmail.com>:

>>>>>> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> Andrew Hyatt <ahyatt@gmail.com> writes:
>>> That sounds like a good idea for bugs of reasonable recentness. I'm
>>> going through old bugs that are years old now. To me, it feels a
>>> bit awkward to suddenly ask people to confirm anything after years
>>> have passed - just closing seems like a more reasonable approach to
>>> me. But I'll follow your advice for bugs in the last year. If you
>>> feel strongly that time elapsed shouldn't matter, though, I'm happy
>>> to do it your way all the time.
>
>> 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.

Maybe the strategy needs a clarification of version supporting policy or
should be based on said policy if it exists.

Say for example 24.x line supported while 23.x support dropped.

The priority could be as below:

Number one: emacs-25 branch related
Should have highest priority since they'll block the release.

Number two: emacs git
They slow down moving train.

Number three: emacs 24.x
Maybe a policy to include accumulated fixes in a new release untill
support dropped, for example yearly bugfix on Dec. 25 or Dec. 31.
Bug fixes only, no new feature backports.

Number four: emacs 23.x/22.x etc (justing kidding. No kidding?)
If bothered by "cannot sleep thinking users are abandoned in darkness"
syndrome, accept users submitted patches and release accumulated bugfix
minor version each year as above.

Maybe a cycling poicy can be built.

Just my RMB2 cents.




  parent reply	other threads:[~2015-12-29  6:46 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
2016-02-15 20:04                 ` Marcin Borkowski
2015-12-29  6:46             ` CHENG Gao [this message]
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=m2fuyloip3.fsf@royau.me \
    --to=chenggao@royau.me \
    --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).