PATCHES - Countdown to May 28

Here is the current countdown list. The next countdown will be on May 28. A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: !1380 musicxml2ly: update bar line conversion - Dan Eble https://gitlab.com/lilypond/l

Re: Thinking about the next stable release

Le 26/05/2022 à 23:19, Dan Eble a écrit : I have "fire in the belly" to finish a \caesura command that engraves marks, divisiones, and bar lines. I hope I can do it by the beginning of autumn. I have quite a number of substantial projects as well. In my humble opinion, we can adjust the prec

Re: Thinking about the next stable release

On May 26, 2022, at 12:12, Jean Abou Samra wrote: > >> 1) Target a release towards the end of this year, but do not deprecate >> things in anticipation of a new major version after; instead go for a >> "regular" 2.26.0 afterwards. > > I think there's reasonable agreement that this is a > good pl

Re: Thinking about the next stable release

Le 26/05/2022 à 18:40, Jean-Charles Malahieude a écrit : Le 26/05/2022 à 18:12, Jean Abou Samra a écrit : Le 22/05/2022 à 14:39, Jonas Hahnfeld via Discussions on LilyPond development a écrit : Hi all, with the unstable releases switched over to Guile 2.2, I think it might be a good idea

Re: Thinking about the next stable release

Le 26/05/2022 à 18:12, Jean Abou Samra a écrit : Le 22/05/2022 à 14:39, Jonas Hahnfeld via Discussions on LilyPond development a écrit : Hi all, with the unstable releases switched over to Guile 2.2, I think it might be a good idea to think about the next stable release. The last time, for 2

Re: Thinking about the next stable release

Le 22/05/2022 à 14:39, Jonas Hahnfeld via Discussions on LilyPond development a écrit : Hi all, with the unstable releases switched over to Guile 2.2, I think it might be a good idea to think about the next stable release. The last time, for 2.22.0 in early 2021, we kind of coincidentally al

Re: checkout releases?

Thanks all! Am Do., 26. Mai 2022 um 13:53 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > > Alas I can't checkout v2.23.7: > > $ git checkout v23.7 > > error: pathspec 'v23.7' did not match any file(s) known to git > > I really hate that damn machine > I wish that they would sell it > I

Re: checkout releases?

Thomas Morley writes: > Alas I can't checkout v2.23.7: > $ git checkout v23.7 > error: pathspec 'v23.7' did not match any file(s) known to git I really hate that damn machine I wish that they would sell it It never does that what I mean But only what I tell it -- David Kastrup

Re: checkout releases?

On May 26, 2022, at 06:52, Thomas Morley wrote: > > Hi, > > some time ago we decided to use v2.23.7 instead of the old > release/2.23.6-1 in the repository. > > Alas I can't checkout v2.23.7: > $ git checkout v23.7 typo: missing "2." between "v" and "23" — Dan

Re: checkout releases?

Le 26/05/2022 à 12:52, Thomas Morley a écrit : Hi, some time ago we decided to use v2.23.7 instead of the old release/2.23.6-1 in the repository. Alas I can't checkout v2.23.7: $ git checkout v23.7 error: pathspec 'v23.7' did not match any file(s) known to git Though I've success with $ git ch

checkout releases?

Hi, some time ago we decided to use v2.23.7 instead of the old release/2.23.6-1 in the repository. Alas I can't checkout v2.23.7: $ git checkout v23.7 error: pathspec 'v23.7' did not match any file(s) known to git Though I've success with $ git checkout release/2.23.6-1 Updating files: [...] Am