From: Eli Zaretskii <eliz@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Starting the Emacs 27 release cycle
Date: Mon, 23 Dec 2019 22:05:56 +0200 [thread overview]
Message-ID: <83pngex0wr.fsf@gnu.org> (raw)
In-Reply-To: <83zhfjvxhc.fsf@gnu.org> (message from Eli Zaretskii on Mon, 23 Dec 2019 18:05:19 +0200)
> Date: Mon, 23 Dec 2019 18:05:19 +0200
> From: Eli Zaretskii <eliz@gnu.org>
>
> I've created the emacs-27 release branch, and bumped Emacs version on
> master to 28.0.50. A pretest of Emacs 27.1 will follow some time
> soon, I hope.
>
> Please from now on push safe bugfixes and documentation fixes to the
> release branch; all the other development should happen on master.
> When in doubt whether a bugfix is safe enough, please ask.
I see that people continue fixing bugs on master, disregarding what I
said above. Please fix bugs on the release branch instead. In
particular, documentation bugs should always be fixed on the release
branch as long as it is active.
Thanks.
next prev parent reply other threads:[~2019-12-23 20:05 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 16:05 Starting the Emacs 27 release cycle Eli Zaretskii
2019-12-23 16:17 ` Alan Mackenzie
2019-12-23 17:26 ` Pankaj Jangid
2019-12-23 20:05 ` Eli Zaretskii [this message]
2019-12-29 20:17 ` Robert Pluim
2019-12-29 20:22 ` Eli Zaretskii
2019-12-29 21:25 ` Robert Pluim
2019-12-31 11:59 ` Windows Snapshots Updated was " phillip.lord
2019-12-31 16:51 ` Drew Adams
2019-12-31 17:05 ` Drew Adams
-- strict thread matches above, loose matches on Subject: below --
2019-11-23 16:59 Eli Zaretskii
2019-11-23 17:25 ` 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
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=83pngex0wr.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).