From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Nicolas Petton <nicolas@petton.fr>,
andrewjmoreton@gmail.com, emacs-devel@gnu.org
Subject: Re: Emacs 26.2 RC1 is out!
Date: Fri, 22 Mar 2019 12:39:44 -0400 [thread overview]
Message-ID: <x4imwayib3.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83imwbs0ip.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 22 Mar 2019 11:48:14 +0200")
>> > Which are the affected files?
>>
>> README
>> configure.ac
>> etc/HISTORY
>> msdos/sed2v2.inp
>> nt/README.W32
The instructions are probably unclear.
The intent was that you would M-x set-version, commit, tag, push.
It was just the HISTORY and ChangeLog file with the release notice that
would not be committed, in case the release date had to change.
It would not do any harm to commit those two files as well (ChangeLog is
no longer versioned, but those changes get committed as ChangeLog.3 or
whatever). It just creates a bit of churn if the release date ends up
changing, and obviously those files two don't affect the build in any
way, so personally I see no reason to commit them.
Testing from git is not the same as testing the release tarball, because
the tarball includes many generated files that certainly do affect the
build (configure, elc files, etc).
BTW, looks like none of the 26.2.x pretests (or RC) were tagged.
Since other changes have since been committed to emacs-26, but the
version number change wasn't, it's not really possible to tag the RC now.
next prev parent reply other threads:[~2019-03-22 16:39 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
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 [this message]
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=x4imwayib3.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=andrewjmoreton@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=nicolas@petton.fr \
/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).