From: Eli Zaretskii <eliz@gnu.org>
To: John Wiegley <jwiegley@gmail.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Getting start on Emacs 25.2
Date: Sun, 18 Sep 2016 17:37:00 +0300 [thread overview]
Message-ID: <83mvj5i8ab.fsf@gnu.org> (raw)
In-Reply-To: <m2bmzmj57g.fsf@newartisans.com> (message from John Wiegley on Sat, 17 Sep 2016 19:45:55 -0700)
> From: John Wiegley <jwiegley@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, Richard Stallman <rms@gnu.org>
> Date: Sat, 17 Sep 2016 19:45:55 -0700
>
> 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.
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. Trying to go through the changes
deciding which ones are worthy of cherry-picking is IMO a waster of
our time, as no AFAIR major features were pushed to master that would
be inappropriate for 25.2.
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.
My $0.20, anyway.
next prev parent reply other threads:[~2016-09-18 14:37 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 [this message]
2016-09-18 16:28 ` Stefan Monnier
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=83mvj5i8ab.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@gmail.com \
--cc=rms@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).