Re: issues to verify -> no more releases

[David Kastrup]

Graham Percival <address@hidden> writes:

> Now that the Patchy staging-merge is running ok, it's time to
> force the next issue:
>   I will not be making any more releases, stable or unstable,
>   as long as there are issues to verify relating to a
>   previously-released version.
>
> At the time of this writing, this means that if *ANY* issue on this
> list:
> http://code.google.com/p/lilypond/issues/list?can=7
> does *NOT* say "fixed_2_15_28", there will be no release.

"verifying" an issue is not the same as giving a "fixed_*" marking.  So
I don't quite understand what you expect here.  I can put the respective
"fixed" markers corresponding to the respective commits on (which is
what I do unless I forget whenever marking an issue of mine fixed after
pushing).

Or is your problem that you want to see "Verified" on every committed
fix with a version earlier than 2.15.18, making sure that the commit did
indeed make it into the mentioned release?

-- 
David Kastrup