[Top][All Lists]

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

Verifying issues

From: Simon Albrecht
Subject: Verifying issues
Date: Wed, 2 Mar 2016 23:52:56 +0100


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? 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.
What do you think?

Best, Simon

reply via email to

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