Jonas Hahnfeld <hah...@hahnjo.de> writes: > Am Donnerstag, den 21.05.2020, 17:21 +0200 schrieb Han-Wen Nienhuys: >> On Thu, May 21, 2020 at 1:17 PM James <pkx1...@posteo.net> wrote: >> > On 21/05/2020 12:02, Han-Wen Nienhuys wrote: >> > > so a next step might be making the countdown process more >> > > continuous. >> > >> > What does that mean - even conceptually? >> >> My idea is that patches could enter 'countdown' stage throughout the >> day, and when they do a 48 hour period waiting period kicks in. This >> means the moment they are mergable will be more spread out throughout >> the day. >> >> My main worry is that the CI process (make doc) will be forced to run >> on machines with less CPU power, and the whole test/doc cycle would >> take 1 or even 2 hours. If CI takes 2 hours, we'd realistically only >> be able to merge 8 changes on a day. > > The full pipeline (build & test & doc) takes less than 1 hour on > GitLab's shared runners with a single core. I think it's a safe bet > that it can't get worse than that. If LilyPond itself gets slower by a > factor of 2, I'd call that a regression in general.
If it is by the translation team doubling the number of supported languages... Actually, if translations were all kept up to date, we'd probably need less time for "make doc" since then most of the translations would work with the same code examples. -- David Kastrup