Am Dienstag, den 30.06.2020, 14:54 +0200 schrieb Jonas Hahnfeld:
> Am Montag, den 29.06.2020, 08:25 -0400 schrieb Dan Eble:
> > On Jun 29, 2020, at 07:49, Jonas Hahnfeld wrote:
> > > I got the list down to five corner cases, all involving multiple
> > > commits related to a single issue.
> >
> >
Am Montag, den 29.06.2020, 08:25 -0400 schrieb Dan Eble:
> On Jun 29, 2020, at 07:49, Jonas Hahnfeld wrote:
> > I got the list down to five corner cases, all involving multiple
> > commits related to a single issue.
>
> ...
> > I think it would be sufficient to have the final release that
Jonas, you wrote 29/06/2020 12:49:08
I got the list down to five corner cases, all involving multiple
commits related to a single issue.
https://gitlab.com/lilypond/lilypond/-/issues/154
https://gitlab.com/lilypond/lilypond/-/issues/1861
These two issues saw additional fixes after several
On Jun 29, 2020, at 07:49, Jonas Hahnfeld wrote:
>
> I got the list down to five corner cases, all involving multiple
> commits related to a single issue.
...
> I think it would be sufficient to have the final release that included
> all commits, but wanted to check back if everybody agrees on
Am Freitag, den 26.06.2020, 11:35 +0200 schrieb Jonas Hahnfeld:
> Am Mittwoch, den 24.06.2020, 13:29 +0200 schrieb Jonas Hahnfeld:
> > Am Dienstag, den 23.06.2020, 20:54 +0200 schrieb Jean Abou Samra:
> > > Le 23/06/2020 à 17:50, Jonas Hahnfeld a écrit :
> > > > Am Dienstag, den 23.06.2020, 15:54
Am Mittwoch, den 24.06.2020, 13:29 +0200 schrieb Jonas Hahnfeld:
> Am Dienstag, den 23.06.2020, 20:54 +0200 schrieb Jean Abou Samra:
> > Le 23/06/2020 à 17:50, Jonas Hahnfeld a écrit :
> > > Am Dienstag, den 23.06.2020, 15:54 +0200 schrieb Valentin Villenave:
> > > > - How do you plan to indicate
Am Mittwoch, den 24.06.2020, 13:23 +0200 schrieb Jonas Hahnfeld:
> Am Dienstag, den 23.06.2020, 13:04 -0400 schrieb Dan Eble:
> > On Jun 23, 2020, at 04:40, Jonas Hahnfeld wrote:
> > > Pretty much that: You can only have one label from the same scope, and
> > > assigning a second automatically
Am Dienstag, den 23.06.2020, 20:54 +0200 schrieb Jean Abou Samra:
> Le 23/06/2020 à 17:50, Jonas Hahnfeld a écrit :
> > Am Dienstag, den 23.06.2020, 15:54 +0200 schrieb Valentin Villenave:
> > > - How do you plan to indicate backports? (Granted, this is a very
> > > limited subset.)
> >
> > Yes,
Am Dienstag, den 23.06.2020, 13:04 -0400 schrieb Dan Eble:
> On Jun 23, 2020, at 04:40, Jonas Hahnfeld wrote:
> > Pretty much that: You can only have one label from the same scope, and
> > assigning a second automatically removes the old (cf. Patch::*). I
> > actually agree that multiple Type's
Am Mittwoch, den 24.06.2020, 12:41 +0200 schrieb Jean Abou Samra:
> Hi,
>
> Le 23/06/2020 à 21:47, Jonas Hahnfeld a écrit :
> > "carefully ensuring" means going through all labels.
>
> Does it? I thought we'd just verify it carefully for a handful
> of them, including corner cases.
I think it
Hi,
Le 23/06/2020 à 21:47, Jonas Hahnfeld a écrit :
"carefully ensuring" means going through all labels.
Does it? I thought we'd just verify it carefully for a handful
of them, including corner cases.
Whether we just
delete them once verified or defer that to a script shouldn't make much
of a
James writes:
> On 23/06/2020 20:47, Jonas Hahnfeld wrote:
>> Never understood the difference between Started and Accepted either.
Presumably "New" and "Accepted". "Started" means that somebody is
working on it, to avoid duplication of effort.
>
> While we have definitions in the CG as Carl
On 23/06/2020 20:47, Jonas Hahnfeld wrote:
Never understood the difference between Started and Accepted either.
While we have definitions in the CG as Carl pointed out the context of
this was, if I remember correctly, to a make sure developers could see
clearly if a tracker issue entered
Am Dienstag, den 23.06.2020, 23:40 +0200 schrieb Valentin Villenave:
> On 6/23/20, Jonas Hahnfeld wrote:
> > I knew that description and, honestly, that would be a show stopper for
> > me reporting any issue to a project in 2020.
>
> Why? Because mailing lists are a thing of the past in your
On 6/23/20, Jonas Hahnfeld wrote:
> I knew that description and, honestly, that would be a show stopper for
> me reporting any issue to a project in 2020.
Why? Because mailing lists are a thing of the past in your view? :-)
Sending an e-mail to an open mailing list is much more universal and
On Tue, Jun 23, 2020 at 2:25 PM Jonas Hahnfeld wrote:
>
> Am Dienstag, den 23.06.2020, 14:11 -0600 schrieb Carl Sorensen:
> > Accepted: the Bug Squad added it, or reviewed the item.
> > Started: a contributor is working on a fix. Owner should change to be
> > this contributor.
> >
> > Closed
Am Dienstag, den 23.06.2020, 14:11 -0600 schrieb Carl Sorensen:
> On Tue, Jun 23, 2020 at 2:04 PM Jonas Hahnfeld wrote:
> > Am Dienstag, den 23.06.2020, 20:54 +0200 schrieb Jean Abou Samra:
> > > Hi,
>
>
> > > Actually, I think the while Status family of scoped labels will no longer
> > > need
On Tue, Jun 23, 2020 at 2:04 PM Jonas Hahnfeld wrote:
>
> Am Dienstag, den 23.06.2020, 20:54 +0200 schrieb Jean Abou Samra:
> > Hi,
> > Actually, I think the while Status family of scoped labels will no longer
> > need to exist. Status::Fixed and Status::Verified are replaced as above.
> > In
Am Dienstag, den 23.06.2020, 20:54 +0200 schrieb Jean Abou Samra:
> Hi,
>
> Le 23/06/2020 à 17:50, Jonas Hahnfeld a écrit :
> > Am Dienstag, den 23.06.2020, 15:54 +0200 schrieb Valentin Villenave:
> > > On 6/22/20, Jonas Hahnfeld wrote:
> > > > In short, I'd like to propose that we replace the
Hi,
Le 23/06/2020 à 17:50, Jonas Hahnfeld a écrit :
Am Dienstag, den 23.06.2020, 15:54 +0200 schrieb Valentin Villenave:
On 6/22/20, Jonas Hahnfeld wrote:
In short, I'd like to propose that we replace the labels Fixed_x_y_z
with milestones x.y.z and use these to track which issues were fixed
On Jun 23, 2020, at 04:40, Jonas Hahnfeld wrote:
>>
> Pretty much that: You can only have one label from the same scope, and
> assigning a second automatically removes the old (cf. Patch::*). I
> actually agree that multiple Type's might be useful. If others are in
> favor as well, we can just
Am Dienstag, den 23.06.2020, 15:54 +0200 schrieb Valentin Villenave:
> On 6/22/20, Jonas Hahnfeld wrote:
> > In short, I'd like to propose that we replace the labels Fixed_x_y_z
> > with milestones x.y.z and use these to track which issues were fixed
> > for a particular release. This has the
On 6/22/20, Jonas Hahnfeld wrote:
> In short, I'd like to propose that we replace the labels Fixed_x_y_z
> with milestones x.y.z and use these to track which issues were fixed
> for a particular release. This has the advantage of a) less labels
> which makes the drop-downs more usable and b) the
Hi James,
Am Dienstag, den 23.06.2020, 08:00 +0100 schrieb James:
> Hello
>
> On 22/06/2020 18:33, Jonas Hahnfeld wrote:
> > In short, I'd like to propose that we replace the labels Fixed_x_y_z
> > with milestones x.y.z and use these to track which issues were fixed
> > for a particular release.
Hello
On 22/06/2020 18:33, Jonas Hahnfeld wrote:
In short, I'd like to propose that we replace the labels Fixed_x_y_z
with milestones x.y.z and use these to track which issues were fixed
for a particular release.
Just so you know I have just gone through all the 'Fixed_' labels this
morning
In short, I'd like to propose that we replace the labels Fixed_x_y_z
with milestones x.y.z and use these to track which issues were fixed
for a particular release. This has the advantage of a) less labels
which makes the drop-downs more usable and b) the possibility to close
milestones. After all,
26 matches
Mail list logo
