Re: Thoughts on next stable release(s)
On Sun, 2024-06-16 at 22:24 +0200, Jonas Hahnfeld wrote: > Hi all, > > it's been 7 months since the last stable (bugfix) release, LilyPond > 2.24.3. Today I went through the list of all (smaller) merge requests > and marked those that we might want to apply to the stable/2.24 branch > with the Backport label: > https://gitlab.com/lilypond/lilypond/-/merge_requests?state=merged&label_name[]=Backport > > It's not many and they are each small, but in my opinion we could think > about having LilyPond 2.24.4 in early / mid July. What do you think? If > there are other changes that you would like to see backported and I > missed so far, or you are unsure about, please ping me on GitLab or > reply to this message. I backported the fixes collected so far, except for https://gitlab.com/lilypond/lilypond/-/merge_requests/2231 which doesn't apply and I believe is not needed for stable/2.24. The tentative plan would be to release 2.25.18 next weekend and then 2.24.4 the week after, maybe again with binaries produced on Wednesday or Thursday (to be seen). Cheers, Jonas signature.asc Description: This is a digitally signed message part
Re: Thoughts on next stable release(s)
On Mon, 2024-06-17 at 19:37 +, Werner LEMBERG wrote: > > > I also suggest !2359. > > > > So far I didn't backport any documentation improvements to > > stable/2.24. Is there anything special about this one? > > I think these index entries complete the list of essential syntax > elements in the NR. I had a quick look through the git history since branching stable/2.24 and it seems there were many other index entries added since then, for example https://gitlab.com/lilypond/lilypond/-/commit/63da9aaeb6ed0c4e79169cdf41350a3a9244ba6e https://gitlab.com/lilypond/lilypond/-/commit/7b4951a5f9ab08b6c7dddb70bfebf86bcc4fd359 https://gitlab.com/lilypond/lilypond/-/commit/fc7c539b14176df781728f77aceee3576f5ac5e4 https://gitlab.com/lilypond/lilypond/-/commit/3a929840508a77539b3e56cce7e5f3fd052583c3 I think I tend towards skipping all of them for stable/2.24 at the current state. Jonas signature.asc Description: This is a digitally signed message part
PATCHES - Countdown to July 10
Here is the current countdown report. The next countdown will begin on 2024-07-10 A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: No patches in Push at this time. Countdown: !2376 Allow limiting beam subdivision depth away from correct metric value - Jason Yip https://gitlab.com/lilypond/lilypond/-/merge_requests/2376 !2375 better accidental mark support in `musicxml2ly` - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/2375 Review: No patches in Review at this time. New: No patches in New at this time. Waiting: No patches in Waiting at this time. Cheers, Colin
Re: Thoughts on next stable release(s)
> The tentative plan would be to release 2.25.18 next weekend and then > 2.24.4 the week after, maybe again with binaries produced on > Wednesday or Thursday (to be seen). +1 Werner
Re: Thoughts on next stable release(s)
> I think I tend towards skipping all of them for stable/2.24 at the > current state. OK. Werner
