[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Re[2]: issue verification

From: Jonas Hahnfeld
Subject: Re: Re[2]: issue verification
Date: Thu, 17 Sep 2020 22:34:11 +0200
User-agent: Evolution 3.36.5

Am Donnerstag, den 17.09.2020, 20:30 +0000 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 still in development, which cannot be verified. Making
> > everybody wanting to help with verification skip over the same set of
> > issues potentially wastes a lot of time...
> > 
> > Jonas
> 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 2.21.4
> Page down to see a list of completed issues (closed).
> These are the ones to verify for 2.21.4 I believe.

Right, that's what we currently have. As far as I understood Jean
wondered if we could move the step of assigning the milestone to
verification? In that case, the described procedure would not work.

Attachment: signature.asc
Description: This is a digitally signed message part

reply via email to

[Prev in Thread] Current Thread [Next in Thread]