On Sat, 2026-01-17 at 17:56 +0100, Jonas Hahnfeld wrote: > 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.
Below is a proposal - for comparison (and so I don't have to search the link again), here's what we planned for 2.24: https://lists.gnu.org/archive/html/lilypond-devel/2022-10/msg00053.html In the end, we did another release candidate and delayed things a bit: https://lists.gnu.org/archive/html/lilypond-devel/2022-11/msg00052.html Weekend of February 7/8: LilyPond 2.25.33 (official binaries should work again on macOS arm64) Afterwards, I want to update all dependencies in release/binaries/ - should we add another unstable release on the weekend of February 21/22 to make sure nothing breaks? Weekend of March 7/8: LilyPond 2.25.34 Week of March 9-12: run formatting tools, branch stable/2.26 [ branch is frozen, no new features or syntax changes; master is bumped to 2.27.0 and is open again for development; I will pick fixes into the stable branch; translation work continues on the stable branch and I'll synchronize back to master during the releases ] Weekend of March 21/22: first release candidate LilyPond 2.25.80 (send lilypond.pot to translators) Weekend of April 4/5: second release candidate LilyPond 2.25.81 Around mid/end April: final LilyPond 2.26.0; unless we need another release candidate 2.25.82 Jonas
signature.asc
Description: This is a digitally signed message part
