Am Donnerstag, den 17.09.2020, 23:01 +0200 schrieb Michael Käppler:
> From my point of view, if an issue is
> 1. closed
> 2. marked as "Status::Fixed"
> 3. assigned to milestone x.y.z
>
> one can be sure that it is fixed in release x.y.z
> What should we verify?
See below.
> Another point is wha
Il giorno mer 16 set 2020 alle 15:39, Michael Käppler
ha scritto:
Am 16.09.2020 um 13:45 schrieb Michael Käppler:
Am 16.09.2020 um 12:18 schrieb Federico Bruni:
Il giorno sab 12 set 2020 alle 15:13, Jonas Hahnfeld
ha scritto:
I think right now it makes most sense to just release 2.21.6 a
Am 17.09.2020 um 23:01 schrieb Michael Käppler:
From my point of view, if an issue is
1. closed
2. marked as "Status::Fixed"
3. assigned to milestone x.y.z
one can be sure that it is fixed in release x.y.z
What I meant was: 'that the commit with the purpose of
fixing the issue has gone into rel
Am 17.09.2020 um 21:32 schrieb Jonas Hahnfeld:
Am Donnerstag, den 17.09.2020, 20:58 +0200 schrieb Jean Abou Samra:
What I do not yet understand is when milestones should be assigned
to issues and MRs. So far Jonas has done this from time to time. That was
after each release, right?
Yes, mostly
Le 17/09/2020 à 22:34, Jonas Hahnfeld a écrit :
Am Donnerstag, den 17.09.2020, 20:30 + schrieb Trevor:
Maybe I'm misunderstanding the problem, but a list of issues to verify
for a particular release, say 2.21.4, can be found by
Issues -> Milestones -> Release LilyPond 2.21.4 -> Milestone
Am Donnerstag, den 17.09.2020, 20:30 + schrieb Trevor:
> Jonas, you wrote 17/09/2020 20:32:31
> Subject: Re: issue verification
>
> > The problem I'm seeing is that it would become harder to find the
> > issues to verify: Most of the time, there will be fixed issues for the
> > current version
Jonas, you wrote 17/09/2020 20:32:31
Subject: Re: issue verification
The problem I'm seeing is that it would become harder to find the
issues to verify: Most of the time, there will be fixed issues for the
current version still in development, which cannot be verified. Making
everybody wanting t
Am Donnerstag, den 17.09.2020, 20:58 +0200 schrieb Jean Abou Samra:
> What I do not yet understand is when milestones should be assigned
> to issues and MRs. So far Jonas has done this from time to time. That was
> after each release, right?
Yes, mostly so. I'm just continuing what CG previously s
Hello,
Here is the current patch countdown list. The next countdown will be on
September 19th.
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
!405 py: drop unused langdefs imports - Han-Wen Nienhuys
https:
Hi,
Le 17/09/2020 à 13:27, Michael Käppler a écrit :
Am 17.09.2020 um 09:47 schrieb Jonas Hahnfeld:
Hi all,
unless I'm missing something, there has been no activity on this since
the community effort in May [1][2] and issues since version 2.21.2
don't yet have Status::Verified labels. As I'm
Am Donnerstag, den 03.09.2020, 16:56 +0200 schrieb Jean Abou Samra:
> Le 02/09/2020 à 22:01, Jonas Hahnfeld a écrit :
>
> > Am Mittwoch, den 02.09.2020, 20:51 +0200 schrieb Jean Abou Samra:
> > > A related question, just out of curiosity: how short are we with
> > > respect to CI minutes?
> > I wr
Am 17.09.2020 um 09:47 schrieb Jonas Hahnfeld:
Hi all,
unless I'm missing something, there has been no activity on this since
the community effort in May [1][2] and issues since version 2.21.2
don't yet have Status::Verified labels. As I'm currently updating CG to
mention our use of milestone
Hi all,
unless I'm missing something, there has been no activity on this since
the community effort in May [1][2] and issues since version 2.21.2
don't yet have Status::Verified labels. As I'm currently updating CG to
mention our use of milestones (not sure why I forgot about this
previously), the
13 matches
Mail list logo
