Re: Blockers for Guile 2.2

[Jonas Hahnfeld]

Am Mittwoch, dem 23.02.2022 um 16:37 +0100 schrieb David Kastrup:
> Jonas Hahnfeld via Discussions on LilyPond development
> <lilypond-devel@gnu.org> writes:
> 
> > > If we need to kill 1.8 support because it blocks something important,
> > > then so be it, but given the impact on lilypond development, I'd try
> > > to postpone it if possible.
> > 
> > So, you propose that development continues on Guile 1.8, but we
> > advertise that we consider Guile 2.2 ready for production use?
> 
> We advertise that Guile 2.2 is considered to be workable.

And what version would the official binaries use? Remain the sole user
of Guile 1.8 while Linux distributions and macOS package managers
switch to Guile 2.2?

> > I don't think that makes for a great user experience if we let them
> > find problems...
> 
> Uh, that's the whole point of having unstable releases, isn't it?

Maybe, but so far we at least tested the combination of dependency
versions during development, even before an unstable release happens.
That would be gone and only a brave subgroup of developers testing the
integration with Guile 2.2 could notice problems before they pop up for
users.

signature.asc
Description: This is a digitally signed message part