Next releases

[Jonas Hahnfeld]

Hi all,

I would like to plan releasing LilyPond 2.25.1 not next weekend, but
the one after that (i.e. January 21/22), unless somebody wants to have
an unstable release this weekend?

Additionally I would have liked to target the last weekend of January /
early February for a bugfix release 2.24.1. Unfortunately, I haven't
heard back from the Debian people yet. As you may remember, the timing
for the stable release was chosen to make it possible to include
LilyPond 2.24.0 in the upcoming Debian Bookworm and a user also opened
a request: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026200
However, in answering I discovered that Debian removed guile-2.2 for
the Bookworm release during November, after we had already branched.
Right now, they only have guile-3.0 which LilyPond doesn't officially
support. I'd find it unfortunate if the next Debian didn't include the
latest LilyPond, but I neither like bundling guile-2.2 with the
lilypond package (as they do with Guile 1.8 right now) or having a
large user base run with Guile 3.0 while we're not officially
supporting it. On the other hand, I'm also hesitant on calling it
"supported" if we're not testing this configuration in our CI...
Opinions?

Still, if possible, please try to submit fixes for 2.24.1 soon to get
them tested with the next unstable release(s) 😉

Cheers
Jonas

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