On May 13, 2020, at 17:13, David Kastrup wrote:
>>> At the current point of time, our pipeline does not tend to be all that
>>> full I think. We are not at Linux kernel levels of participation...
>>
>> No, you're probably right. It's only a bit more bothersome if you have
>> multiple changes to
Jonas Hahnfeld writes:
> Am Mittwoch, den 13.05.2020, 21:54 +0200 schrieb David Kastrup:
>> Jonas Hahnfeld writes:
>> > Hi all,
>> >
>> > as discussed before the migration, we might want to look into using a
>> > CI system. Foremost this would help James who is currently still
>> > testing
Am Mittwoch, den 13.05.2020, 21:54 +0200 schrieb David Kastrup:
> Jonas Hahnfeld writes:
> > Hi all,
> >
> > as discussed before the migration, we might want to look into using a
> > CI system. Foremost this would help James who is currently still
> > testing patches manually. At least the doc
Jonas Hahnfeld writes:
> Hi all,
>
> as discussed before the migration, we might want to look into using a
> CI system. Foremost this would help James who is currently still
> testing patches manually. At least the doc build can and should be
> completely automatic.
> Additionally GitLab has a
Hi all,
as discussed before the migration, we might want to look into using a
CI system. Foremost this would help James who is currently still
testing patches manually. At least the doc build can and should be
completely automatic.
Additionally GitLab has a feature called "Merge Trains", see [1]
Am Mittwoch, den 13.05.2020, 15:23 + schrieb Trevor:
> Jonas, you wrote 13/05/2020 07:19:54
>
> > Am Dienstag, den 12.05.2020, 17:08 + schrieb Trevor:
> > > Jonas, you wrote 12/05/2020 14:49:27
> > >
> > > > Actually I think we should use milestones for this. They can be closed
> > >
Jonas, you wrote 13/05/2020 07:19:54
Am Dienstag, den 12.05.2020, 17:08 + schrieb Trevor:
Jonas, you wrote 12/05/2020 14:49:27
> Actually I think we should use milestones for this. They can be closed
> and don't clutter the labels.
> This comes with the disadvantage that there can be
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'lilypond' has been submitted
by the Dutch team of translators. The file is available at:
https://translationproject.org/latest/lilypond/nl.po
(We can arrange things so
Am Mittwoch, den 13.05.2020, 10:24 +0100 schrieb James:
> Hello
>
> On 13/05/2020 07:15, Jonas Hahnfeld wrote:
> > So I think we should just have some kind of policy where to discuss
> > things first.
>
> OK would there be any objection to removing the 'countdown-specific'
> labels (i.e.
Hello,
Here is the current patch countdown list. The next countdown will be on
May 15th.
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
!18 Prevent race condition in `-dfont-ps-resdir` - Masamichi Hosoda
Hello
On 13/05/2020 07:15, Jonas Hahnfeld wrote:
So I think we should just have some kind of policy where to discuss
things first.
OK would there be any objection to removing the 'countdown-specific'
labels (i.e. new/review/countdown/push) from closed issues, or issues
that have been
Am Dienstag, den 12.05.2020, 17:08 + schrieb Trevor:
> Jonas, you wrote 12/05/2020 14:49:27
>
> > Actually I think we should use milestones for this. They can be closed
> > and don't clutter the labels.
> > This comes with the disadvantage that there can be at most one
> > milestone set
Am Dienstag, den 12.05.2020, 17:00 + schrieb Trevor:
> Jonas wrote 12/05/2020 13:42:46
>
> > In my opinion, there are currently far too many labels on GitLab. To
> > avoid the situation getting worse, please do not create new labels out
> > of thin air for now. Instead we should first
13 matches
Mail list logo
