unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: emacs-devel@gnu.org
Subject: Starting the Emacs 27 release cycle
Date: Sat, 23 Nov 2019 18:59:39 +0200	[thread overview]
Message-ID: <83r21yttok.fsf@gnu.org> (raw)

I'm planning on cutting the emacs-27 release branch in a week or so.
If someone has plans for changes that must be done before that, so
that they end up in Emacs 27.1, please make it happen till then, or
ask here for an extension.  After the branch is cut, only bugfixes
will be allowed on the release branch, per our usual practices (see
CONTRIBUTE).

Thanks.



             reply	other threads:[~2019-11-23 16:59 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-23 16:59 Eli Zaretskii [this message]
2019-11-23 17:25 ` Starting the Emacs 27 release cycle Robert Pluim
2019-11-23 17:41   ` Eli Zaretskii
2019-11-24 16:51     ` Robert Pluim
2019-11-23 20:02 ` Philipp Stephani
2019-11-24  3:30   ` Eli Zaretskii
2019-11-25 21:48     ` Philipp Stephani
2019-11-26 18:09       ` Eli Zaretskii
2019-11-23 21:30 ` Eric Abrahamsen
2019-11-24  3:36   ` Eli Zaretskii
2019-11-23 23:16 ` Juri Linkov
2019-11-23 23:49   ` Stefan Kangas
2019-11-25 23:03     ` Phil Sainty
2019-11-27 23:50       ` Juri Linkov
2019-11-28  5:55         ` Stefan Kangas
2019-11-28  8:53           ` Robert Pluim
2019-11-28 10:30             ` VanL
2019-11-28 22:42               ` Juri Linkov
2019-11-27 23:47     ` Juri Linkov
2019-11-29  5:21       ` Richard Stallman
2019-11-24  3:39   ` Eli Zaretskii
2019-12-03 16:13 ` Bastien
2019-12-03 16:23   ` Eli Zaretskii
2019-12-03 22:40     ` Bastien
2019-12-03 23:09       ` Juanma Barranquero
2019-12-04  9:53         ` Bastien
2019-12-04 11:01           ` Juanma Barranquero
  -- strict thread matches above, loose matches on Subject: below --
2019-12-23 16:05 Eli Zaretskii
2019-12-23 16:17 ` Alan Mackenzie
2019-12-23 17:26 ` Pankaj Jangid
2019-12-23 20:05 ` Eli Zaretskii
2019-12-29 20:17 ` Robert Pluim
2019-12-29 20:22   ` Eli Zaretskii
2019-12-29 21:25     ` Robert Pluim

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=83r21yttok.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).