"Trevor Daniels" <t.dani...@treda.co.uk> wrote in message
news:f867cc5a71fc42b7b9f90fbb44692...@trevorlaptop...
Carl Sorensen wrote Sunday, September 26, 2010 1:51 PM
On 9/26/10 3:14 AM, "Trevor Daniels" <t.dani...@treda.co.uk> wrote:
Carl wrote
Also, please note that we don't file bugs on any versions not yet
released, because there really isn't a 2.13.35 yet.
Why not? A bug which happened to have been noticed in
a version compiled from git might have existed for some
time. We don't expect the Bug Squad to do this research,
do we?
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.
This clearly would demonstrate whether a problem which
happened to be noticed in a git build was present in
the latest GUB release.
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. So nothing for a Bug Squad member to do - it's at this point solely
an issue for the developers. If it appears in the released 13.35 then a bug
report should appear on .bug and a Bug squad member will do the necessary to
get it into the tracker.
--
Phil Holmes
Bug Squad
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
