unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Getting start on Emacs 25.2
Date: Sun, 18 Sep 2016 12:28:21 -0400	[thread overview]
Message-ID: <jwv1t0hji1y.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 83mvj5i8ab.fsf@gnu.org

>> Now that 25.1 is out the door, it's time to begin work on 25.2. I'd
>> like to ask those who are aware of patches that might have been
>> applied to 25.1, but weren't due to time pressure, to review those
>> patches and consider cherry-picking them to the emacs-25 branch,
>> which is now open to such changes.

Maybe a good start is to look at those commits on master whose commit
message refers to a bug#.

> My gut feeling is that everything on master is relevant to Emacs 25.2,
> and therefore we should probably start a new branch, called Emacs-25.2
> or some such, forking it off master.

Master includes a fairly large number of changes already, so it's
clearly not fit for a quick bug-fix-only release.

IOW what you're suggesting is to forgo bug-fix releases and go straight
to the next "feature" release (maybe with fairly few features).

I'm fine with it, but I'd call it Emacs-26, then ;-)

> Alternatively, we could decide that 25.2 will be a bugfix only
> release, in which case none of the changes on master should be in it,
> only bugs that will be reported hence about the released version.

I'd vote for that option (but accepting some cherrypicks from master
from those people who care enough to take the time to do that).
[ Of course, nobody should be surprised at this point: back in the
  time of 24.5 I made it clear that I think the ".MM" part should be
  used exclusively for bugfix-only releases, so Emacs-24.3 should have
  been called Emacs-25.1.  ]


        Stefan




  reply	other threads:[~2016-09-18 16:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-18  2:45 Getting start on Emacs 25.2 John Wiegley
2016-09-18 14:37 ` Eli Zaretskii
2016-09-18 16:28   ` Stefan Monnier [this message]
2016-09-18 19:41   ` John Wiegley
2016-09-18 21:23     ` Nicolas Petton
2016-09-19  6:37       ` Andreas Röhler
2016-09-19 16:37     ` Eli Zaretskii
2016-09-22 12:57       ` Phillip Lord
2016-09-22 15:15         ` Eli Zaretskii
2016-09-18 20:48 ` Phillip Lord
2016-09-19  7:09   ` Michael Albinus
2016-09-19  8:52     ` Phillip Lord
2016-09-29 19:23   ` 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=jwv1t0hji1y.fsf-monnier+gmane.emacs.devel@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).