> Personally, I am almost in favor of a rather hard cut where we switch
> from Guilev1 to Guilev2.
+1
> Most direct would be a hard cut: exchange the Guile version, and get
> everybody working furiously until LilyPond works again.
Yes :-)
>> Given that these patches will be quite extensive, is now a good
>> time to set up a guile-2 branch in git, forking off from the start
>> of the V2.17.0 development?
As suggested by David, I would favor that guile v2 support is added to
the master branch, assuming that you consider it mature enough to
break only, say, 90% of lilypond input files and not 99% :-)
Werner
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
