On Fri, Nov 27, 2009 at 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&y=Priority&x=Type&cells=ids > > Neat, huh? I'll add it to the CG.
Yes! That is very cool. Somehow they seem less daunting in that format ... maybe because they take up so little space. > Note that anything in the High or Regression range stops 2.14 from > being released. > > > 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. > > Also, could somebody on OSX check 752 (high defect) ? I suspect this > has been fixed by bumping pango. > > Also, 818 (high defect)? > > Cheers, > - Graham > > > _______________________________________________ > bug-lilypond mailing list > bug-lilyp...@gnu.org > http://lists.gnu.org/mailman/listinfo/bug-lilypond > _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
