On Sun, Sep 26, 2010 at 05:48:37PM +0100, Phil Holmes wrote: > "Trevor Daniels" <t.dani...@treda.co.uk> wrote in message > news:f867cc5a71fc42b7b9f90fbb44692...@trevorlaptop... > > > >>We expect the Bug Squad to test on the latest development release. > > > >OK. I see one of the actions for a Bug Squad member > >is to generate a png file demonstrating the problem.
Overall, the task of the Bug Squad is to make sure that a claimed bug is a real problem, and not just a user error. > >So I was wrong - we _do_ expect them to do this research. > >Presumably they should forward the report to -dev if the > >bug does not show in the latest GUB release. > > The original report said "does not work with lates git Lilypond > 2.13.35 but works on 2.13.34-1". So my interpretation of this is > that there is no bug on any release that most Bug Squad members > could test to or generate output from. Correct. To emphasize this point, we absolutely do not expect any Bug Squad member to compile source code. > So nothing for a Bug Squad member to do Not quite -- you can (and should) mark such issues as Invalid as soon as they appear. 1) it wasn't added by a Bug Squad member or developer 2) it's not clearly a real bug. Two strikes and you're out. :) Cheers, - Graham _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
