On Wed, 2026-01-14 at 05:08 +0000, Werner LEMBERG wrote:
> > Is it about time to start preparing 2.26?

Thanks for bringing this up. FWIW the last discussion was in July, see
https://lists.gnu.org/archive/html/lilypond-devel/2025-07/msg00022.html
where we concluded "not before the end of the year" (2025). I've not
been as active as I had hoped since then, so I didn't push further on
this. I can again volunteer to "manage" the release, but given some
other constraints it may be a bit less smooth than the last two times.
Apologies in advance, if that's ok for everyone I can try my best.

> > For my part, I'm behind where I had hoped to be by this time, but I
> > think I should be content with that and leave \senzaMisura for 2.27.
> 
> The LSR-to-Wiki transition needed immediate attention, and I'm done
> within the next few days.  However, this cost me two months.  There is
> still some `musicxml2ly` stuff that I would like to finish before 2.26
> gets released, so I suggest to do a code freeze in March.

March sounds like a reasonable time to branch, with a release aimed
towards May or so? If we think that could work, I can prepare a rough
"timelime" to get a better idea of how things would look.

In general, if we want to stick to a timeline, it can well be that some
work doesn't make it. For example, I finally managed to get a large
part of the MinGW patches into Guile upstream and was half hoping to
wait for a release so we don't need to patch it for our binaries.
However, I don't think we should wait for that (nor try to update Guile
at the very last minute).

Note that there is one "urgent" point that needs to be addressed: The
cfarm machine I use for building the macOS arm64 binaries was recently
updated to macOS 26. First, this means that I wasn't even able to build
binaries for today's unstable release. I think I know how to fix it,
but it needs a bit more time than I could invest today. And second, it
means the binaries won't work on older OS versions anymore. There may
also be ways to improve that, but it needs some experimentation and
then a bit of discussion. Overall doable until March, I hope.

Cheers,
Jonas

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

Reply via email to