From: Eli Zaretskii <eliz@gnu.org>
To: Philippe Vaucher <philippe.vaucher@gmail.com>
Cc: rgm@gnu.org, nicolas@petton.fr, andrewjmoreton@gmail.com,
emacs-devel@gnu.org
Subject: Re: Emacs 26.2 RC1 is out!
Date: Fri, 22 Mar 2019 12:25:28 +0200 [thread overview]
Message-ID: <83ef6zrysn.fsf@gnu.org> (raw)
In-Reply-To: <CAGK7Mr6hq9EowT2sP67ZOvKR_W42U8ZQSqxjYoKKhcKg9+5v6w@mail.gmail.com> (message from Philippe Vaucher on Fri, 22 Mar 2019 11:16:49 +0100)
> From: Philippe Vaucher <philippe.vaucher@gmail.com>
> Date: Fri, 22 Mar 2019 11:16:49 +0100
> Cc: Nicolas Petton <nicolas@petton.fr>, Glenn Morris <rgm@gnu.org>, andrewjmoreton@gmail.com,
> Emacs developers <emacs-devel@gnu.org>
>
> > That, and the HISTORY file contains a release date for 26.2 as well.
>
> It's the same problem. Suppose we update HISTORY to the date of RC1.
> If RC1 becomes Emacs 26.2, the date in HISTORY is correct; otherwise
> we will commit a modified HISTORY with the release of the next RC.
>
> Just a note: with my proposal there is always a difference between 26.2-rc1 and 26.2 (the names), so the
> history date would change as well.
If there's a difference, then it isn't an RC. A Release Candidate
means that if no significant problems are reported, the RC _becomes_
the official release, by just renaming the tarball without changing
its contents.
What you propose would be appropriate for a pretest, not for an RC.
next prev parent reply other threads:[~2019-03-22 10:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 22:21 Emacs 26.2 RC1 is out! Nicolas Petton
2019-03-21 6:06 ` Van L
2019-03-21 8:22 ` Nicolas Petton
2019-03-21 8:01 ` Philippe Vaucher
2019-03-21 8:16 ` Nicolas Petton
2019-03-21 9:43 ` Philippe Vaucher
2019-03-21 13:48 ` Andy Moreton
2019-03-21 14:45 ` Óscar Fuentes
2019-03-21 20:50 ` Nicolas Petton
2019-03-22 6:55 ` Eli Zaretskii
2019-03-22 8:59 ` Nicolas Petton
2019-03-22 9:11 ` Eli Zaretskii
2019-03-22 9:37 ` Nicolas Petton
2019-03-22 9:48 ` Eli Zaretskii
2019-03-22 9:51 ` Nicolas Petton
2019-03-22 10:00 ` Eli Zaretskii
2019-03-22 10:16 ` Philippe Vaucher
2019-03-22 10:25 ` Eli Zaretskii [this message]
2019-03-22 12:32 ` Philippe Vaucher
2019-03-22 10:14 ` Philippe Vaucher
2019-03-22 11:12 ` Nicolas Petton
2019-03-22 16:39 ` Glenn Morris
2019-03-22 16:46 ` Eli Zaretskii
2019-03-22 16:48 ` Glenn Morris
2019-03-25 9:50 ` Rostislav Svoboda
2019-03-25 10:10 ` Eli Zaretskii
2019-03-25 14:46 ` Nicolas Petton
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=83ef6zrysn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrewjmoreton@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=nicolas@petton.fr \
--cc=philippe.vaucher@gmail.com \
--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).