On Fri, Nov 27, 2009 at 09:04:10PM -0700, Carl Sorensen wrote: > On 11/27/09 2:29 PM, "Graham Percival" <gra...@percival-music.ca> wrote: > > > After a bit of experimenting, I think this is the best way to view issues: > > > > http://code.google.com/p/lilypond/issues/list?mode=grid=Priority=Type=ids > > Yes, quite nice. It's very helpful. Thanks!
Also of note: items marked "Documentation" generally only need a few sentences added to the docs. We could probably close 5 of these issues with half an hour of doc-editing... if anybody wanted to touch the docs? Remember folks, you don't need to compile anything to write+test docs! > > Note that anything in the High or Regression range stops 2.14 from > > being released. > > 697 dates from 2.11, so we released 2.12 with it. Do we want to hold up > 2.14 for it? Dunno. There's also at least one item called "Regression: blah blah" which isn't at Regression priority. I was going to raise this question in a few days, after everybody has had a chance to delete all the issue update emails. :) > > BTW, my initial guess is that 787 could be fixed with less than 5 > > lines of scheme; I think some code is doing a simple comparison rather > > than sorting through a list. > > Actually, this had nothing to do with it. I'm not sure exactly why, but > with the extra notes the outside-staff-priority was used instead of the > script-priority. And the outside-staff-priority was not set properly. Thanks! Cheers, - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
