[Top][All Lists]

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

Re: Verifying issues

From: Simon Albrecht
Subject: Re: Verifying issues
Date: Thu, 3 Mar 2016 00:47:41 +0100

On 03.03.2016 00:19, Trevor Daniels wrote:
Simon Albrecht wrote Wednesday, March 02, 2016 10:52 PM

>I noticed that there have been many ‘Issues to verify’ around, so I
>started to catch up with these. Now the question is: Shouldn’t we only
>mark issues as verified, when the change is already included in an
>official release?
Yes, that is correct.  See Regular Maintenance under

Verified fixes should be in an available release.

>For curiosity, following the CG instruction I took the committish from
><>  – claimed to be
>‘Fixed_2_19_38’ – and fed it into<>,
>and it worked. So according to the instruction, I should mark the issue
>verified, although the change is not contained in the most recent
>release, 2.19.37.
Which instruction is this?  I think Phil's tool finds any commit that is in
the git master, not just those in built releases.

Instruction from the very same page that you link above. That’s why I asked.

Best, Simon

reply via email to

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