bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 1716 in lilypond: No convert-ly rule for the fix for issue 165


From: lilypond
Subject: Re: Issue 1716 in lilypond: No convert-ly rule for the fix for issue 1655
Date: Tue, 28 Jun 2011 10:55:47 +0000


Comment #8 on issue 1716 by percival.music.ca: No convert-ly rule for the fix for issue 1655
http://code.google.com/p/lilypond/issues/detail?id=1716

Short-term fiat decision (as release meister): absolutely no removing/renaming to syntax in a stable version, even for internal properties. Any text file which works in 2.14.0 must work in 2.14.n. Absolutely no convert-ly rules. Don't backport 1655.

Long-term: it's now on the GOP list under the general "release policies" item. I'm willing to discuss relaxing the "any text file" rule, although I personally will argue against it.


Of heavy interest to this question is the release schedule. The first 2.16 release candidate will be on a month or so; if we can successfully avoid stable releases being once-a-year-or-more, then that takes some pressure off of backporting.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]