From: Eli Zaretskii <eliz@gnu.org>
To: Nicolas Petton <nicolas@petton.fr>
Cc: rgm@gnu.org, andrewjmoreton@gmail.com, emacs-devel@gnu.org
Subject: Re: Emacs 26.2 RC1 is out!
Date: Fri, 22 Mar 2019 12:11:24 +0300 [thread overview]
Message-ID: <83k1grs283.fsf@gnu.org> (raw)
In-Reply-To: <87lg17l1xi.fsf@petton.fr> (message from Nicolas Petton on Fri, 22 Mar 2019 09:59:37 +0100)
> From: Nicolas Petton <nicolas@petton.fr>
> Cc: andrewjmoreton@gmail.com, emacs-devel@gnu.org, rgm@gnu.org
> Date: Fri, 22 Mar 2019 09:59:37 +0100
>
> The doc says that it's best not to commit the files that change the
> version number (to 26.2 in our case) and the release date (it's set to a
> future date, and is subject to change).
>
> If we change that process, the docs should say instead to make commit
> those files, and make a tag, just like we do for pretests.
>
> > I don't think I mind RC tags in the repository, even if they
> > eventually point to the same commit as the release, but I'm not sure I
> > understand the details well enough.
>
> The only issue is that we push files with a version number and release
> date that is not final (if the RC has issues).
Thanks for the explanations.
Which are the affected files?
next prev parent reply other threads:[~2019-03-22 9:11 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83k1grs283.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrewjmoreton@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=nicolas@petton.fr \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.