On 4/30/11 8:07 AM, "Phil Holmes" <m...@philholmes.net> wrote:
> ----- Original Message ----- > From: "Carl Sorensen" <c_soren...@byu.edu> > To: "Lily devel" <lilypond-devel@gnu.org> > Sent: Saturday, April 30, 2011 1:59 PM > Subject: Backporting / stable > > >> So it appears that the biggest source of Critical bugs, and the thing that >> is holding up release of 2.14, is the beam-collision-engraver. >> >> Should we try to remove the beam-collision-engraver from 2.14.0? Or >> should >> we wait for it to settle itself out and make it part of 2.14.0? I can see >> arguments for both. >> >> Thanks, >> >> Carl > > My own view is that getting the beam collisions improved is now a major > feature of 2.14 and if it can be fixed in weeks rather than months it would > be better to wait. > > I guess the counter-argument is that gives you lots of extra work :-( > I actually think it would be more work to remove the beam-collision-engraver than to keep it in. But at this point I expect it to be months before we are sure we're clear of Critical bugs in beam-collision engraver. Beaming affects literally every piece of music. And there are so many beam cases that it seems to me to be unlikely that we'll be able to wring this all out in a time frame of say 6 weeks. I expect it to be more like 4-6 months. We have had beam-collision-engraver in git since Feb. 9. We still have Critical issues related to it. Please don't consider this a complaint about the beam-collision-engraver. I think it's a *great* feature, and I'm glad Mike has jumped in to tackle it. It's just *extremely* hard to verify something that affect so much music in so many different ways. We have what we think are good regtests, and then we find something new that we haven't covered. But I'm certainly willing to wait for a bit to see if we can get rid of all the critical bugs. Thanks, Carl _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
