Am 02.04.19 um 09:48 schrieb Malte Meyn:
Am 02.04.19 um 09:34 schrieb Urs Liska:
But that probably should wait until the release of 2.20.0 and
2.21.0, shouldn’t it?
I don't think so. Of course such a fundamental change doesn't belong
in 2.20, but adding stuff to the development branch doesn't seem
problematic to me. If it should turn out that starting with these
changes imposes any risk of breaking stuff we could still work on a
branch for a longer time (and maybe merge that to 2.21 after a 2.20
release).
An extra branch is a good idea. I thought of people who want to use
the new features introduced in 2.21.0 but not 2.20.0 (there probably
will be a lot of those), therefore I’d add changes to master only
after the release of 2.21.0 (i. e. 2.21.1 would be the earliest
possible release for big SMuFL changes).
Ah that's why you asked. No, adding stuff to the development branch will
*not* go into 2.20 anymore, that has already been forked. For any new
commits to be included in 2.20 David Kastrup would have to manually pick
them (which would simply not be done in this case).
Urs
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user