bug#66554: [PATCH] Add the public API of Compat to the core

[Philip Kaludercic]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Daniel Mendler <mail@daniel-mendler.de>
>> Cc: Philip Kaludercic <philipk@posteo.net>,  66554@debbugs.gnu.org,
>>   monnier@iro.umontreal.ca,  stefankangas@gmail.com
>> Date: Fri, 12 Jan 2024 19:40:38 +0100
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> > I guess I'm misunderstanding something.  The scenario that I have in
>> > mind is this:
>> >
>> >   . we bump Emacs version to NN.1.90 as part of pretesting version NN.2
>> >   . as part of the pretest, some function changes that requires
>> >     addition or change in compat.el
>> >   . compat.el still claims version NN.1, although it includes changes
>> >     not present in Emacs NN.1
>> >
>> > Did I succeed in explaining my worries?
>> 
>> I hope I understood your reasoning correctly. Shortly after you bump
>> NN.1.90 we can release compat-NN.2.0 which will include the necessary
>> change.
>
> Release where? on ELPA or as part of the Emacs tarball?
>
> And how do we make sure we will not forget to release this new version
> of compat.el?

We have to distinguish the ELPA package Compat and the compat.el file
being added here.  The ELPA package Compat is manually released on our
behalf, usually after a release of Emacs has been announced.  The plan
is that the compat.el file does not have to be touched at all, since it
registers itself to use the right version, while Emacs is scraping the
for autoloads.  So there shouldn't be any additional effort from the
side of Emacs maintenance, and nothing one can "forget".