David Kastrup wrote Friday, September 27, 2013 1:33 PM

> I think after letting 2.17.27 settle for a few days, we are ready to
> create the branch.  We still might make another 2.17 release afterwards
> to get some exposure to final fixes (like the \fill-line markup), but it
> better not have any syntax changes requiring convert-ly rules unless
> they are going to end up in 2.18 as well.  Issue 3566 is a candidate for
> this "may or may not make it" threshold.
> 
> But I think having a release of 2.18 ready in about three weeks seems
> possible enough that we should try.

Good.  I'll start to think about the doc changes which should go into 2.19 :)
Suggestions welcome.

(I stopped making changes to the docs a while ago so translators had
a clear target to aim for.)

Trevor
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to