From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs 29.3 released
Date: Tue, 26 Mar 2024 21:35:53 +0200 [thread overview]
Message-ID: <86o7b0iy5i.fsf@gnu.org> (raw)
In-Reply-To: <875xx9f4ol.fsf@gmx.de> (message from Michael Albinus on Tue, 26 Mar 2024 15:28:26 +0100)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: emacs-devel@gnu.org
> Date: Tue, 26 Mar 2024 15:28:26 +0100
>
> > Would it be possible to modify the Tramp revision on the release
> > branch so that it would not have the "-pre" suffix, and otherwise
> > leave intact the procedure by which you collect and merge fixes to the
> > release branch? That would mean that if such an emergency release
> > does happen, you then advance the Tramp version to the next one (say,
> > from 2.6.3 to 2.6.4), and keep updating the release branch with any
> > further fixes. If that is possible for you, I think it will be the
> > easiest solution for the future, if we ever need to make such
> > emergency releases again (something that I think is quite probable,
> > given that it happened both for Emacs 28 and Emacs 29).
>
> It would be possible. I could change the Tramp version in the release
> branch to the next anticipated release number. So I could change it now
> to "2.6.3.29.4". However, I see at least two problems:
>
> - The Tramp version doesn't guarantee any longer uniqueness. Tramp
> 2.6.3.29.4 would differ today and tomorrow. That was the reason to use
> such an ambiguous version like 2.6.3-pre.
>
> - We might run into problems on ELPA. A user sees a builtin version of
> Tramp 2.6.3.29.4, but in order to fix something for her there is also
> Tramp 2.6.2.9 (let's say). I fear we'll have a hard time to explain,
> that 2.6.2.9 is newer than 2.6.3.29.4.
Then perhaps make-tarball.txt needs to say that the version of Tramp
should be changed from X.Y.Z-pre to X.Y.Z as part of preparing the
release? Or even do this automatically in admin/admin.el, as part of
set-version?
> > Alternatively, we could record in make-tarball.txt the fact that such
> > releases must be coordinated with you. From where I stand, this is
> > less desirable (as it adds a non-trivial prerequisite for such
> > releases, which could mean a delay if you are unavailable for some
> > reason), but still possible.
>
> Perhaps it must not be coordinated with "me" only. A single
> announcement, that there will be an emergency release within two days
> would have helped. Usually, I scan Emacs related messages every single day.
>
> If I am unavailable that time, so be it. Not worse than now.
Preparation of a release tarball is a precarious job: since we don't
lock the Git repository while the release is being worked on, it must
be done very quickly; any commits someone does during the time it
takes to do all the steps necessary for producing the tarball is a
setback that requires to go back several steps and start anew. So any
additional dependency is a disadvantage I'd like to avoid.
> (FWIW, I don't understand yet why 29.3 was such an emergency that it was
> released w/o any warning in advance.)
Because it makes no sense to announce in advance that Emacs has
security vulnerabilities. It's akin to waving the proverbial red flag
at a bull.
next prev parent reply other threads:[~2024-03-26 19:35 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-24 14:14 Emacs 29.3 released Eli Zaretskii
2024-03-24 17:52 ` Corwin Brust
2024-03-24 18:46 ` Eli Zaretskii
2024-03-24 19:36 ` Corwin Brust
2024-03-24 19:46 ` Eli Zaretskii
2024-03-24 19:58 ` Eli Zaretskii
2024-03-27 5:54 ` Corwin Brust
2024-03-24 18:48 ` Michael Albinus
2024-03-24 19:29 ` Eli Zaretskii
2024-03-24 20:10 ` Michael Albinus
2024-03-24 20:20 ` Eli Zaretskii
2024-03-26 8:48 ` Michael Albinus
2024-03-26 12:46 ` Eli Zaretskii
2024-03-26 14:28 ` Michael Albinus
2024-03-26 14:38 ` Ihor Radchenko
2024-03-26 17:50 ` Michael Albinus
2024-03-26 18:01 ` Ihor Radchenko
2024-03-26 18:48 ` Michael Albinus
2024-03-26 19:35 ` Eli Zaretskii [this message]
2024-03-27 8:27 ` Michael Albinus
2024-03-27 12:42 ` Eli Zaretskii
2024-03-27 14:07 ` Michael Albinus
2024-03-27 16:42 ` Eli Zaretskii
2024-03-27 17:35 ` Michael Albinus
2024-04-03 12:03 ` Michael Albinus
2024-04-03 12:36 ` Robert Pluim
2024-04-03 15:01 ` Michael Albinus
2024-04-03 12:51 ` Eli Zaretskii
2024-04-03 14:56 ` Michael Albinus
2024-04-04 12:25 ` Eli Zaretskii
2024-04-04 12:40 ` Michael Albinus
2024-04-04 17:46 ` Ihor Radchenko
2024-03-27 15:15 ` Corwin Brust
2024-03-26 15:32 ` Ulrich Mueller
2024-03-26 18:42 ` Michael Albinus
2024-04-06 15:45 ` Lynn Winebarger
2024-04-06 16:09 ` Eli Zaretskii
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=86o7b0iy5i.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
/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).