[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Release ERC 5.6

From: J.P.
Subject: Re: [PATCH] Release ERC 5.6
Date: Sat, 25 Nov 2023 13:50:16 -0800
User-agent: Gnus/5.13 (Gnus v5.13)

Eli Zaretskii <eliz@gnu.org> writes:

>> From: "J.P." <jp@neverwas.me>
>> Cc: emacs-erc@gnu.org, bandali@gnu.org
>> Date: Sat, 25 Nov 2023 09:02:17 -0800
>> ERC plans on releasing a new version sometime soon. Would it be possible
>> to add something like the attached to the release branch informing
>> people of this?
> I'm not sure I understand why ERC should behave differently than any
> other bundled package that is also on ELPA.  None of them tells the
> user the bundled version is "outdated", as in this message:
>> +       nil (concat
>> +            "\C-bThis version of ERC is outdated\C-b. The latest release"
>> +            " on GNU ELPA contains a host of new fixes and features."
>> +            " If you use ERC regularly, please consider upgrading."
>> +            " See (info \"(erc) Upgrading\") for details. Network I/O was"
>> +            " not involved in bringing you this message.")))))

Perhaps the "outdated" bit was unnecessary.

> Instead, we rely on package.el to tell users that a newer version is
> available from ELPA, and we rely on users to decide whether to
> upgrade.

I've come to discover users aren't aware ERC exists on ELPA or that
bundled packages can be upgraded. But I suppose those issues can be
addressed in some other way.

> Is there anything in ERC that justifies this different behavior?

I guess not.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]