Re: branching stable/2.22?

Am Montag, den 24.08.2020, 22:10 +0200 schrieb Jean Abou Samra: > > > > > As sort of a shot in the dark, how about planning the 2.22 release > > > > > for May 2021, for example? > > > > > > > > Do you mean branching stable/2.22 or releasing 2.22.0 in May 2021? In > > > > my understanding, the pas

Re: branching stable/2.22?

Hi, > Le 24 août 2020 à 13:46, Jonas Hahnfeld a écrit : > > Am Montag, den 24.08.2020, 12:56 +0200 schrieb Jean Abou Samra: >> Hi, >> >>> Le 24 août 2020 à 08:30, Jonas Hahnfeld a écrit : >>> >>> Am Sonntag, den 23.08.2020, 23:44 +0200 schrieb Jean Abou Samra: Maybe we could try to relea

Re: maintaining lilypond git repository on github

Am Mittwoch, den 19.08.2020, 19:42 +0200 schrieb Jonas Hahnfeld: > Am Dienstag, den 18.08.2020, 20:55 +0200 schrieb Jonas Hahnfeld: > > Looks like the previous updates didn't purge removed branches, at least > > there are still a bunch that are neither at Savannah nor GitLab. I'd > > propose we del

Re: branching stable/2.22?

Jonas Hahnfeld writes: > Am Montag, den 24.08.2020, 12:56 +0200 schrieb Jean Abou Samra: >> >> Right, I was oblique: the scripts are fragile at present, so >> branching release/2.22 now is no good in my opinion, but hopefully >> we can stabilize them faster than we stabilize LilyPond as a whole,

Re: branching stable/2.22?

Am Montag, den 24.08.2020, 12:56 +0200 schrieb Jean Abou Samra: > Hi, > > > Le 24 août 2020 à 08:30, Jonas Hahnfeld a écrit : > > > > Am Sonntag, den 23.08.2020, 23:44 +0200 schrieb Jean Abou Samra: > > > Hi, > > > > > > (Sorry about the strange reply style.) > > > > > > > On Sun, Aug 23, 2020

Re: branching stable/2.22?

Hi, > Le 24 août 2020 à 08:30, Jonas Hahnfeld a écrit : > > Am Sonntag, den 23.08.2020, 23:44 +0200 schrieb Jean Abou Samra: >> Hi, >> >> (Sorry about the strange reply style.) >> >>> On Sun, Aug 23, 2020 at 1:58 PM Jonas Hahnfeld wrote: >>> I'd like to ask what it would take in principle to

PATCHES - Countdown for August 24th

Hello, Here is the current patch countdown list. The next countdown will be on August 26th. A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: !342 Fix doc/ja/customized-drum-notation-in-printed-and-midi-outpu

Re: GSoC 2020 update: (hopefully) final commits made; testing time

> I've reordered and rebased my code, and it is now up to date with > the current master. I've just published the new branch to GitLab as > dev/lamb/GSoC-2020-final if you'd like to give it a look. It's only > nine commits now, instead of over a hundred, and they're ordered in > a way that's hope

Re: GSoC 2020 update: (hopefully) final commits made; testing time

>> At the same time, I'll write docs for my work. I figure I'll make >> nine documentation commits, one for each code change commit. Hmm. Maybe I've misunderstood you. What's actually missing are documentation strings *within* the commits. For example, the commit Add smufl data to feta gl

Re: GSoC 2020 update: (hopefully) final commits made; testing time

Am Montag, den 24.08.2020, 09:06 +0200 schrieb Werner LEMBERG: > > I've reordered and rebased my code, and it is now up to date with > > the current master. I've just published the new branch to GitLab > as > > dev/lamb/GSoC-2020-final if you'd like to give it a look. It's > only > > nine commits

Re: GSoC 2020 update: (hopefully) final commits made; testing time

> I've reordered and rebased my code, and it is now up to date with > the current master. I've just published the new branch to GitLab as > dev/lamb/GSoC-2020-final if you'd like to give it a look. It's only > nine commits now, instead of over a hundred, and they're ordered in > a way that's ho