From: Ricardo Wurmus <rekado@elephly.net>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-user@gnu.org
Subject: Re: rfc: next guile 1.8.x release
Date: Sat, 30 Jan 2021 13:31:26 +0100 [thread overview]
Message-ID: <871re2ip29.fsf@elephly.net> (raw)
In-Reply-To: <878s8b71d6.fsf@web.de>
Dr. Arne Babenhauserheide <arne_bab@web.de> writes:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Thien-Thi Nguyen <ttn@gnuvola.org> skribis:
>>> I would like to work (on the weekends, so as not to intefere w/
>>> <day-job>) on preparation and release of Guile 1.8.9, targeted
>>> for the ides of April (more or less).
>>>
>>> Guile 1.8.x users: What changes do you want to see in 1.8.9?
>
> I am not a Guile 1.8.x user, but changes I would like to see is anything
> that could ease incremental porting to Guile 3.x. If there’s a way to
> backport incompatible interfaces from 3.x so people can replace the
> 1.8.x-specific interfaces one by one, that could make it more viable to
> move upwards.
Guile 2 was already very different from 1.8.
>>> Guile maintainers: Any tips (process, content, interop, etc)
>>> most welcome!
>>
>> Guile 1.8 has been unmaintained for years and I wonder about the message
>> we’d be sending by publishing a bug-fix release 11 years and 3 major
>> versions later.
>
> The message we’re sending is that we don’t leave anyone out in the cold
> who committed to using Guile.
The mailing lists are evidence enough that users of Guile 1.8 can get
help in migrating to version 2+.
But suggesting that Guile 1.8 is still maintained when it emphatically
is not — that is a step too far, in my opinion.
--
Ricardo
next prev parent reply other threads:[~2021-01-30 12:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 21:54 rfc: next guile 1.8.x release Thien-Thi Nguyen
2021-01-11 14:51 ` Mike Gran
2021-01-12 10:55 ` Massimiliano Gubinelli
2021-01-16 22:55 ` Thien-Thi Nguyen
2021-01-16 22:48 ` Thien-Thi Nguyen
2021-01-29 21:35 ` Ludovic Courtès
2021-01-29 23:46 ` Dr. Arne Babenhauserheide
2021-01-30 12:31 ` Ricardo Wurmus [this message]
2021-01-30 14:49 ` Dr. Arne Babenhauserheide
2021-01-31 17:35 ` Massimiliano Gubinelli
2021-02-01 21:49 ` Ludovic Courtès
2021-02-07 6:59 ` John Cowan
2021-03-08 20:36 ` Andy Wingo
2021-03-09 7:14 ` Dr. Arne Babenhauserheide
2022-03-03 0:11 ` Thien-Thi Nguyen
2022-03-14 12:14 ` Thien-Thi Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871re2ip29.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=arne_bab@web.de \
--cc=guile-user@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).