Re: Emacs 29.3 released

[Ihor Radchenko <yantar92@posteo.net>]

Michael Albinus <michael.albinus@gmx.de> writes:

>> 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? ...
>
> 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.

May it be an option to follow what Org mode does?
We have a stable branch that we periodically tag as a bugfix release
(weekly, if there are new commits).
Only tagged bugfix releases are merged to Emacs upstream.
The same bugfix releases go to ELPA.

> (FWIW, I don't understand yet why 29.3 was such an emergency that it was
> released w/o any warning in advance.)

CVE.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>