Verifying issues

[Simon Albrecht]

Hello,

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 
<https://sourceforge.net/p/testlilyissues/issues/4754/> – claimed to be 
‘Fixed_2_19_38’ – and fed it into <http://philholmes.net/lilypond/git/>, 
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