On Fri, Apr 15, 2011 at 7:30 AM, [email protected] <[email protected]> wrote: >>> OK. http://code.google.com/p/lilypond/issues/detail?id=1613 >> >> I am testing a fix for this; it was an oversight of mine. >> >> Graham, >> >> this issue was exposed due to a (seemingly innocuous) one-line change >> by Mike. Can I ask that you branch off the 2.14 branch so the release >> candidate does not get disturbed by other one-liners with unintended >> effects? If you don't branch off a stable branch, 2.14 will never get >> finished. > > I agree - I think that if we branch off 2.14 after we fix the three > remaining critical issues (all of which seem to have been recently > introduced) and if everyone holds off on pushing new stuff for a bit (my > MultiMeasureRest work, for example, won't make it into 2.14.0), we can still > sit on it for a week or two before building it with GUB. During this > incubation phase, we'd only apply patches that fix critical or high priority > problems.
The beauty of branching off is that nobody needs to hold off anything. You just continue to put stuff in master (2.15.0), and cherry-pick whatever needs to go to 2.14. -- Han-Wen Nienhuys - [email protected] - http://www.xs4all.nl/~hanwen _______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
