Re: Post-Upgrade Breakage

[Philip Kaludercic]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Christopher Howard <christopher@librehacker.com>
>> Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org,
>>   emacsconf-discuss@gnu.org
>> Date: Mon, 26 Aug 2024 09:01:35 -0800
>> 
>> Stefan Kangas <stefankangas@gmail.com> writes:
>> > Yes, the branch you want is emacs-30.  I'd recommend doing that,
>> > especially if time is concern.
>> >
>> 
>> I just built it this morning from the emacs-30 repo branch. I am
>> using guix's emacs-next environment, and did not have any trouble
>> building or installing it. I just have to set the EMACSLOADPATH to
>> the correct place, and also keep a watch on what info files I'm
>> loading, so I'm reading the newer manuals. Thanks!
>> 
>> I was expecting half my code to break, or something. But
>> undramatically, my entire init.el loaded normally without any errors
>> or warnings. A seamless experience so far...
>
> This is Emacs, so no surprises here.

I am not sure if this is generally true.  Sure, we who understand what
every line in your init.el and work on master don't have issues, but in
oneline discussions I frequently hear of people having issues when
upgrading from one version to another, especially if the change in the
major mode is greater than one.

It is probably not easy to debug this, but some special handling to
detect if the major mode version has changed from one startup to the
next might be useful for the average user.

-- 
        Philip Kaludercic on peregrine