From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs 29.3 released
Date: Wed, 03 Apr 2024 14:03:51 +0200 [thread overview]
Message-ID: <87r0fmk5zs.fsf@gmx.de> (raw)
In-Reply-To: <87o7az7f2o.fsf@gmx.de> (Michael Albinus's message of "Wed, 27 Mar 2024 18:35:43 +0100")
[-- Attachment #1: Type: text/plain, Size: 660 bytes --]
Michael Albinus <michael.albinus@gmx.de> writes:
Hi Eli,
>>> I would change the Tramp version from "2.6.3-pre" to "2.6.3.29.3", and I
>>> would update `customize-package-emacs-version-alist'.
>>>
>>> The Tramp version happens on several places in Emacs, so I have a small
>>> automation which runs on my laptop. See lisp/net/trampver.el and
>>> doc/misc/trampver.texi.
>>
>> Would it make sense to make this part of admin/admin.el, called from
>> "M-x set-version"? Or at least add some text to make-tarball.txt to
>> verify that these changes are done before preparing the tarball?
>
> I'll think about when I'm back.
What about this:
[-- Attachment #2: Type: text/plain, Size: 1612 bytes --]
diff --git a/admin/make-tarball.txt b/admin/make-tarball.txt
index 5704e8e8922..6ea22220928 100644
--- a/admin/make-tarball.txt
+++ b/admin/make-tarball.txt
@@ -134,6 +134,9 @@ General steps (for each step, check for possible errors):
Before a release candidate is made, the tasks listed in
admin/release-process must be completed.
+ If this is an emergency release without a prior pretest, inform
+ the concerned package maintainers. See admin/notes/versioning.
+
Set the version number to that of the actual release (commit in
one, as described above). Pick a date about a week from now when
you intend to make the release. Use M-x add-release-logs from
diff --git a/admin/notes/versioning b/admin/notes/versioning
index 9428dc76710..a86e2a1b9d5 100644
--- a/admin/notes/versioning
+++ b/admin/notes/versioning
@@ -27,3 +27,12 @@ unexpected last-minute problem occurs.
The development version for a new major release has "minor" = 0.
The development version for a new minor release has "minor" = that of
the previous release.
+
+Emacs contains built-in packages with an own version number, which
+could be different from the natural version number of this package
+(for example, Tramp). Usually, they are adjusted by the respective
+maintainers prior an Emacs release. If a new Emacs version will be
+released without a pretest release, for example an emergency release
+due to security problems, inform the respective package maintainers in
+advance by email, and give them a short period (one day) to adjust the
+package version number.
[-- Attachment #3: Type: text/plain, Size: 25 bytes --]
Best regards, Michael.
next prev parent reply other threads:[~2024-04-03 12:03 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
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 [this message]
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=87r0fmk5zs.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=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).