On Thu, 2022-07-14 at 17:38 +0200, Jean Abou Samra wrote: > Hi, > > In https://lists.gnu.org/archive/html/lilypond-devel/2022-05/msg00099.html, > we talked about targeting the end of this year for the next > stable release. That probably means branching around > the beginning of September, right?
Possibly, yes. If wanted, I can try and prepare a "draft timeline" based on what we did two years ago and what needs to happen until around what deadline... > I'd like to call for attention on the regressions we have > <https://gitlab.com/lilypond/lilypond/-/issues/?label_name%5B%5D=Regression> > as well as some other serious things that should go > into this release: basically, (assuming branching in September) > there is a month and a half left to take care of those. > This is not all that long if not very short, especially since > some people (like me) tend to be less active in August. I agree, even though I'd like to note that only those marked ~Critical actually block the release. There are a number of ~Regression issues that have been there for 2.22.x or even 2.20.0. Whether we want to re- classify some of the more recent ones as ~Critical, is of course up for discussion. And fixing issues is obviously still a good idea š > [...] > > * Cairo anyone? What's the status of > Ā https://gitlab.com/lilypond/lilypond/-/merge_requests/913? > Ā Not really a blocker, but I thought the plan was to > Ā integrate Cairo in the official binaries for this stable > Ā release. The merge request needs work; on Linux it currently finds system libs: https://gitlab.com/lilypond/lilypond/-/merge_requests/913#note_678654750 I expect this will also need work for FreeBSD, macOS and Windows; first getting it to build and then some serious testing. > * āHeisen-crashes on Windows with large scoresā > > Ā https://gitlab.com/lilypond/lilypond/-/issues/6361 > > Ā A nasty and poorly understood GC problem on Windows, > Ā needs some tough debugging. This is currently the only issue marked ~Critical, and I agree this must be addressed before a stable release. I hope I can come back to this in the next weeks. > * āGUILE 2.2 doesn't provide source locationsā > > Ā https://gitlab.com/lilypond/lilypond/-/issues/5992 > > Ā Needs figuring out if executing Scheme code with > Ā `compile` is OK performance-wise and how to get > Ā it to display source location info. I agree this is annoying, and it would be great to improve the situation. I'm not sure if this should block the release though. Jonas
signature.asc
Description: This is a digitally signed message part
