Re: Updated release schedule
> Le 12 nov. 2022 à 15:45, Dan Eble a écrit : > > On Nov 12, 2022, at 09:07, Werner LEMBERG wrote: > >>> 2. Release 2.23.81 without the fix and instead review it properly. > ... >> Option 2 is fine with me. > > +1 +1 as well.
Re: Updated release schedule
On Nov 12, 2022, at 09:07, Werner LEMBERG wrote: >> 2. Release 2.23.81 without the fix and instead review it properly. ... > Option 2 is fine with me. +1 — Dan
Re: Updated release schedule
> 1. Review and merge the fix this weekend and release 2.23.81, hoping >that it doesn't break text replacements in other ways. Assuming >things go well, we could still have the final 2.24.0 in early >December. > > 2. Release 2.23.81 without the fix and instead review it >properly. Then have a third release candidate 2.23.82 the weekend >of November 26/27, and delay the final 2.24.0 to mid December >(maybe the week 12th-18th). > > I only had a quick look so far and the fix seems non-trivial to me, > in particular not a plain revert of a previous commit. It also > seems to involve GC related problems, which I haven't understood > yet. I therefore lean towards the second option. Option 2 is fine with me. Werner
Re: Updated release schedule
On Mon, 2022-10-10 at 23:08 +0200, Jonas Hahnfeld wrote: > Weekend of October 22/23: first release candidate LilyPond 2.23.80 > > Weekend of November 12/13: second release candidate LilyPond 2.23.81 So we are here. That said, we have a Critical Regression issue: https://gitlab.com/lilypond/lilypond/-/issues/6463 Jean already prepared a fix in the form of https://gitlab.com/lilypond/lilypond/-/merge_requests/1725 In my opinion, this leaves us with two alternatives: 1. Review and merge the fix this weekend and release 2.23.81, hoping that it doesn't break text replacements in other ways. Assuming things go well, we could still have the final 2.24.0 in early December. 2. Release 2.23.81 without the fix and instead review it properly. Then have a third release candidate 2.23.82 the weekend of November 26/27, and delay the final 2.24.0 to mid December (maybe the week 12th-18th). I only had a quick look so far and the fix seems non-trivial to me, in particular not a plain revert of a previous commit. It also seems to involve GC related problems, which I haven't understood yet. I therefore lean towards the second option. Please let me know what you think. Jonas signature.asc Description: This is a digitally signed message part
Re: Updated release schedule
On Mon, Oct 10, 2022 at 11:08:57PM +0200, Jonas Hahnfeld via Discussions on LilyPond development wrote: > Hi all, > > Yes, I'm trying to slightly shorten the timeline to three weeks between > the release candidates in an attempt to get a release before the end of > the year. We will see how this will work out... Thank you for doing this. It looks good. Kevin
Re: Updated release schedule
> Wednesday, October 12: Branch stable/2.24 unless we get some serious > problem reports for 2.23.14 > > [ branch is frozen, no new features or syntax changes; master is > bumped to 2.25.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 October 22/23: first release candidate LilyPond 2.23.80 > > Weekend of November 12/13: second release candidate LilyPond 2.23.81 > > Begin of December: final LilyPond 2.24.0; unless we need another > release candidate 2.23.82 > > > Yes, I'm trying to slightly shorten the timeline to three weeks > between the release candidates in an attempt to get a release before > the end of the year. We will see how this will work out... Thanks, and it looks good. Werner
