Graham Percival wrote Monday, November 29, 2010 7:33 AM
With that in mind, I'm reopening the same question as the 24 Oct email. 2) release 2.14 ASAP with no critical flaws, but with some kind of code freeze.
I prefer a variant on this. Branch 2.14 now and apply only patches to critical problems to it. That will at least prevent new bugs arising from new code. Continue to allow development in 2.15 unrestrained. Do not start GOP or GLISS until 2011. That allows time over the holiday period for critical bugs to receive attention, permitting (hopefully) a release of 2.14.0 early in 2011. Announce (to development) a target date for releasing 2.14.0, say 15 Jan 2011, to encourage work on bugs, translations, docs, etc over this period. Trevor _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
