David Kastrup wrote 12/05/2018 11:27:40
James, they try to fix lilypond 2.18, not 2.20 or master.
2.18 is still insecure.
At this point of time we probably really need to decide to release
2.20,
come hell and high water, including its current faults.
Or pitch out 2.18.3. At the very least it might make sense to add
purely compilation fixes (for keeping up with more current versions of
compilers etc) to the current stable branch in future even if one does
no proper release. Possibly even security fixes. That way there is
some semi-official way of dealing with bit rot. Also makes it easier
to
do regression testing 5 years later.
"decide to release 2.20"? Yes. Better still: "And" rather than "Or".
If details of the regressions in 2.20.0 are provided alongside the
improvements
folk can decide which of 2.18.3 and 2.20.0 suits them best.
Trevor
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
