On Thu, Jul 14, 2011 at 04:30:30PM +0200, Urs Liska wrote: > >ick. That means that they're floating around in the "issues to > >verify" list, thereby confusing things for development. > Do they really? After all they are "issues to verify". > With this policy you can see the tag "verified_2_15_5" in the issues > list and see it's halfway done. > > But OTOH one could also argue to leave such issues completely > unverified if you can't verify them completely. > > What do you think?
I think all this energy could be directed at much more important stuff. I think that there's a lot of fuss about something which doesn't matter. The first 2.16 release candidate will be out in 2.5 weeks (if there's 0 critical issues). It will probably take 1-2 weeks to fix those issues, unless we make a "stable" release with known Critical Issues, we're looking at releasing 2.14.2 approximately 7 days before the first 2.16 release candidate. Woot? Cheers, - Graham _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
