"Valentin Villenave" <[EMAIL PROTECTED]> writes: > 2008/10/8 Valentin Villenave <[EMAIL PROTECTED]>: >> I won't push it myself because it's still a scary move (at least to me). > > And by the way: I haven't added any NEWS item since I'm not sure this > will get merged, but it ever does, we /ABSOLUTELY/ need to post it on > the mailing list, on the website, put a big warning in the > documentation, send airplanes with banners in the sky, etc. > > PianoStaff may be used by 80% of LilyPonders, so if suddenly stops > working that would easily look like an apocalypse to them.
The customary solution for interface changes would be to make this a three-step process distributed over three releases. First step is deprecating it in the documentation, second step is to have Lilypond emit warnings when it is used, third step is to remove support. First and second step may reasonably be conflated here since there is a feasible way to have source working without warning across releases: just use Grandstaff anywhere. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
