GNU bug report logs - #66554
[PATCH] Add the public API of Compat to the core

Previous Next

Full log

Message #79 received at 66554 <at> debbugs.gnu.org (full text, mbox):

From: Philip Kaludercic <philipk <at> posteo.net>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: mail <at> daniel-mendler.de, stefankangas <at> gmail.com, monnier <at> iro.umontreal.ca,
 66554 <at> debbugs.gnu.org
Subject: Re: bug#66554: [PATCH] Add the public API of Compat to the core
Date: Fri, 12 Jan 2024 18:17:21 +0000

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Philip Kaludercic <philipk <at> posteo.net>
>> Cc: 66554 <at> debbugs.gnu.org,  eliz <at> gnu.org,  Stefan Monnier
>>  <monnier <at> iro.umontreal.ca>,  Stefan Kangas <stefankangas <at> gmail.com>
>> Date: Fri, 12 Jan 2024 16:29:15 +0000
>> 
>> > What happens when we bump Emacs version from NN.x to NN.x.90 or from
>> > NN.x.90 to NN.x.91?  emacs-major-version and emacs-minor-version stay
>> > the same, but the Emacs version is bumped, and there could be changes
>> > in compat.el specific to the next release, NN.x+1 or NN+1.1, no?
>> 
>> Generally speaking, Compat only provides support for "proper" releases,
>> and not for pre-releases.
>
> Is that wise?
>
> Can't we support pretest versions as well?

I hope I am not misunderstanding something, but from the perspective of
Compat and Emacs development as a whole, I think it would be preferable
to not start propagating additions and changes to functions that might
change before a proper release, so as to not unnecessarily burden
development with sticking to decisions that one realises were mistakes
before the final release is cut.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.