PATCHES - Countdown for May 25th

Hello, Here is the current patch countdown list. The next countdown will be on May 27th. A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: !65 musicxml2ly: support multiple elements - Valentin Villenave ht

GitLab permissions

Hi, Could someone please add me to the LilyPond group on GitLab? Since I'm trying to work on MusicXML, it would be nice if I could add the corresponding label to the appropriate issues, and perhaps self-assign a few of them. Also, there are some old issues that look fixed but are still open,

Re: new procedure with GitLab CI

Am Sonntag, den 24.05.2020, 16:28 +0200 schrieb David Kastrup: > Jonas Hahnfeld writes: > > Am Sonntag, den 24.05.2020, 13:19 +0100 schrieb James Lowe: > > > So, and you didn't answer this specific question, if I set the label to > > > 'review' before the pipeline runs will make doc still run? >

Re: new procedure with GitLab CI

Am Sonntag, den 24.05.2020, 14:37 +0100 schrieb James Lowe: > > But what if a patch in countdown is rebased (without a diff) and is > > currently running? Should it be put back to Patch::new and afterwards > > skip the labels until Patch::countdown? That sounds very confusing to > > me... > > I gu

Re: new procedure with GitLab CI

Jonas Hahnfeld writes: > Am Sonntag, den 24.05.2020, 13:19 +0100 schrieb James Lowe: > >> So, and you didn't answer this specific question, if I set the label to >> 'review' before the pipeline runs will make doc still run? > > Sorry: Yes, CI pipelines will run irrespective of the labels. One n

Re: new procedure with GitLab CI

On 24/05/2020 14:11, Jonas Hahnfeld wrote: Am Sonntag, den 24.05.2020, 13:19 +0100 schrieb James Lowe: On 24/05/2020 12:09, Jonas Hahnfeld wrote: You should see it at the individual MR, can you check https://gitlab.com/lilypond/lilypond/-/merge_requests/82 ? I am still not certain. Sorry to be

Re: new procedure with GitLab CI

Am Sonntag, den 24.05.2020, 13:19 +0100 schrieb James Lowe: > On 24/05/2020 12:09, Jonas Hahnfeld wrote: > > You should see it at the individual MR, can you check > > https://gitlab.com/lilypond/lilypond/-/merge_requests/82 > > ? > > I am still not certain. Sorry to be a pain here. > > !83 and !8

Re: new procedure with GitLab CI

On 24/05/2020 12:09, Jonas Hahnfeld wrote: Am Sonntag, den 24.05.2020, 11:41 +0100 schrieb James Lowe: OK. Using Masamichi's MR as an example (nothing personal Hosoda-san!) I saw that his MR !81 came up via countdown.py - I am using the latest update of this BTW - so looking at this MR via the w

Re: new procedure with GitLab CI

> I can't tell you for sure either. It could be that the fork at > https://gitlab.com/trueroad/lilypond has Pipelines enabled, but only > visible to project members. Hosoda-san, could you check this in your > project? The drop-down is at Settings > General > Visibility ... > > Pipelines. I'm guess

Re: new procedure with GitLab CI

Am Sonntag, den 24.05.2020, 11:41 +0100 schrieb James Lowe: > OK. Using Masamichi's MR as an example (nothing personal Hosoda-san!) I > saw that his MR !81 came up via countdown.py - I am using the latest > update of this BTW - so looking at this MR via the web I could not tell > if this had don

Re: helping with testing resources

Jonas Hahnfeld writes: > Am Sonntag, den 24.05.2020, 10:18 +0200 schrieb Jonas Hahnfeld: >> Am Sonntag, den 24.05.2020, 00:21 +0200 schrieb David Kastrup: >> > I think configure options should likely point to Guile-1.8 (for now) and >> > use --enable-checking and (to save CI minutes) --enable-gs-

Re: helping with testing resources

Am Samstag, den 23.05.2020, 21:30 +0200 schrieb Valentin Villenave: > On 5/23/20, Jonas Hahnfeld wrote: > > If you have spare hardware and / or want to help with CI testing, this > > is easy to setup with GitLab. First you'll need their runner and I'll > > defer to the excellent documentation: >

Re: lilypond grammar in the contributor guide

Han-Wen Nienhuys writes: > thanks, I'll take this as an OK to drop grammar from the manual. I am actually unhappier about seeing the mechanism for generating it disappear rather than the grammar itself. But for LilyPond, it really does no longer provide a reasonable value. -- David Kastrup

Re: new procedure with GitLab CI

On 24/05/2020 08:59, Jonas Hahnfeld wrote: Hi James, Am Samstag, den 23.05.2020, 19:08 +0100 schrieb James Lowe: Jonas, On 23/05/2020 18:59, Jonas Hahnfeld wrote: Hi all, I've now made the necessary settings, merged the changes in https://gitlab.com/lilypond/lilypond/-/merge_requests/57, cha

Re: helping with testing resources

Am Sonntag, den 24.05.2020, 10:18 +0200 schrieb Jonas Hahnfeld: > Am Sonntag, den 24.05.2020, 00:21 +0200 schrieb David Kastrup: > > I think configure options should likely point to Guile-1.8 (for now) and > > use --enable-checking and (to save CI minutes) --enable-gs-api . > > > > Reasonable? >

Re: helping with testing resources

Am Sonntag, den 24.05.2020, 00:21 +0200 schrieb David Kastrup: > Jonas Hahnfeld writes: > > (see my previous message(s) for context on GitLab CI) > > > > If you have spare hardware and / or want to help with CI testing, this > > is easy to setup with GitLab. First you'll need their runner and I'l

Re: new procedure with GitLab CI

Hi James, Am Samstag, den 23.05.2020, 19:08 +0100 schrieb James Lowe: > Jonas, > > On 23/05/2020 18:59, Jonas Hahnfeld wrote: > > Hi all, > > > > I've now made the necessary settings, merged the changes in > > https://gitlab.com/lilypond/lilypond/-/merge_requests/57, changed all > > existing mer

Re: lilypond grammar in the contributor guide

thanks, I'll take this as an OK to drop grammar from the manual. On Sun, May 24, 2020 at 12:19 AM David Kastrup wrote: > > David Kastrup writes: > > > Han-Wen Nienhuys writes: > > > >> We have a dump of the bison grammar in the contributor guide (see > >> http://lilypond.org/doc/v2.19/Documenta