[bug#63984] [PATCH emacs-team 0/2] Start preparing for Emacs 29

[Andrew Tropin <andrew@trop.in>]

[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]

On 2023-06-11 21:09, Mekeor Melire wrote:

> Hello :)
>
> 2023-06-11 09:35 andrew@trop.in:
>
>> Sounds reasonable, but I think it would be ok, if after updating 
>> emacs, emacs-next will be 29 for a couple of weeks with 
>> deprecation warning on top of it. The meaning of -next suffix is 
>> a convention, not a technical limitation, so it's fine to 
>> violate it for deprecation period.
>
>> Overall, deprecation is not something crucial here and people 
>> know that guix breaks backward compatibility from time to time, 
>> so I think it's ok to go without it.
>
> I think we don't need to divert deprecation/alias from its 
> intended use. I think NEWS serves its job well enough.
>
> When having emacs-next installed and keeping it upgraded, users 
> should be able to expect that the upcoming release of Emacs is 
> installed, without deprecation warnings. After all, the package is 
> not called emacs29 but emacs-next.
>
> That being said, I believe it's a good idea to 
> define-deprecated/public-alias emacs-next-pgtk and 
> emacs-next-pgtk-xwidgets.

All emacs-next* variables dissapear after this patch is applied and
talking about deprecation warning: I don't see much difference between
emacs-next and emacs-next-pgtk-xwidgets in this context.

-- 
Best regards,
Andrew Tropin

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]