On Sun, 2023-11-05 at 22:36 +0100, Jonas Hahnfeld wrote:
> Step 1: Officially support Guile 3.0 and add optional CI testing
> I opened https://gitlab.com/lilypond/lilypond/-/merge_requests/2162 to
> add some compatibility with earlier versions of Guile 3.0 and then
> implement detection support in configure. It also creates Docker images
> and adds optional CI testing, as we had it for the transition to Guile
> 2.2.
The MR is nominally on countdown right now, do we have a consensus on
this? I'm fully ok with delaying this, but then it will miss the next
unstable release that I would like to do this weekend, and the backport
to the stable version tentatively planned for the next weekend (see
below).
> Step 2a: Assuming this testing goes fine, I would like to backport the
> changes from the first step to stable/2.24 and release a new stable
> version. The idea is that distributions wanting to drop their package
> for Guile 2.2 can switch LilyPond 2.24 to Guile 3.0. Note that the
> official binaries will stay Guile 2.2 for future bug fix releases, it's
> only about officially supporting the later version. However, we also
> have to see how the situation develops with Ghostscript 10.02.1, so
> let's postpone discussion on this topic for now...
So https://gitlab.com/lilypond/lilypond/-/merge_requests/2160 seems to
work now, and I think we should get this out in an unstable release
(next weekend) and then a bug fix release the weekend after. For other
bug fixes, I marked a number of merge requests with the Backport label:
https://gitlab.com/lilypond/lilypond/-/merge_requests?scope=all=merged_name[]=Backport
Please ping me on other fixes that you think should be part of 2.24.3,
or any of the above that should not be backported. For the support of
Guile 3.0, it depends on whether we merge it for 2.25.10 and if people
think it should be backported.
Cheers,
Jonas
signature.asc
Description: This is a digitally signed message part
