From: John Wiegley <jwiegley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rgm@gnu.org, eggert@cs.ucla.edu, emacs-devel@gnu.org,
Phillip Lord <phillip.lord@russet.org.uk>
Subject: Re: status of emacs-25 branch
Date: Sun, 21 May 2017 11:37:42 -0400 [thread overview]
Message-ID: <m2h90e5igp.fsf@newartisans.com> (raw)
In-Reply-To: <83r2zwa759.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 10 May 2017 21:39:14 +0300")
>>>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:
EZ> It is still too early to cut the emacs-26 branch, Emacs 25.2 was released
EZ> less than a month ago. IMO, we should wait a bit longer, before we decide
EZ> that emacs-25 will see no more bug-fix releases.
Agreed.
EZ> Once that decision is made, we should next decide whether Emacs 26.1
EZ> should wait for some unexec solution or not. If it should wait, we cannot
EZ> yet cut a release branch based on master.
I don't think we need to wait for that in particular. It might be nice to get
a new release out with the threading support, start gaining some experience
for that change, while we continue to get unexec ready.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2017-05-21 15:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 17:06 status of emacs-25 branch Glenn Morris
2017-05-09 17:47 ` Eli Zaretskii
2017-05-09 19:16 ` Paul Eggert
2017-05-10 2:30 ` Eli Zaretskii
2017-05-10 17:47 ` Phillip Lord
2017-05-10 18:39 ` Eli Zaretskii
2017-05-21 15:37 ` John Wiegley [this message]
2017-05-21 16:03 ` Eli Zaretskii
2017-05-21 17:39 ` Michael Albinus
2017-05-21 18:39 ` Eli Zaretskii
2017-05-22 7:39 ` Michael Albinus
2017-05-22 18:43 ` Eli Zaretskii
2017-05-27 12:04 ` Eli Zaretskii
2017-05-29 21:04 ` Paul Eggert
2017-05-21 20:38 ` Nicolas Petton
2017-05-22 4:04 ` Eli Zaretskii
2017-05-22 15:45 ` martin rudalics
2017-05-22 20:03 ` John Wiegley
2017-05-24 18:14 ` Eli Zaretskii
2017-05-12 8:06 ` Eli Zaretskii
2017-05-15 1:09 ` Glenn Morris
2017-05-15 2:46 ` Eli Zaretskii
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=m2h90e5igp.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=phillip.lord@russet.org.uk \
--cc=rgm@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).