Re: Is it about time to start preparing 2.26?

Jonas Hahnfeld via Discussions on LilyPond development <[email protected]> Sat, 07 Mar 2026 13:42:23 +0100

Newsgroups	gmane.comp.gnu.lilypond.devel
Message-ID	<[email protected]>

On Thu, 2026-02-05 at 21:42 +0100, Jonas Hahnfeld wrote:
> 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?

LilyPond 2.25.34 was released on February 21 and, as far as I can tell,
there were no reports that the binaries are broken.

> Weekend of March 7/8: LilyPond 2.25.34

Consequently this weekend's release is LilyPond 2.25.35. The VERSION in
master was bumped to 2.25.80 in preparation for the release candidate
phase.

So we are now here. I have to say that the last two releases were still
relatively packed with changes (and some of them with quite widespread
impact!). For comparison, despite being compressed to two weeks the
releases have the same number of commits that previously landed during
four weeks. I would still like to go ahead as planned:

> 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

signature.asc (application/pgp-signature, 228 B)