Re: Issue 1273 in lilypond: Woodwind Diagrams lead to Ghostscript error in latest git

[Trevor Daniels]

Carl Sorensen wrote Sunday, September 26, 2010 1:51 PM

> On 9/26/10 3:14 AM, "Trevor Daniels" <address@hidden> 
> 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.

Might be worth making this clear in the CG, as at present
it's just a side effect of the actions in 7.5 Adding
issues to the tracker.

> Problems with a git build are reported on -devel, with a reference 
> to a
> commit SHA1.

Hm. Not sure a Bug Squad member should be expected to
determine the SHA1, if a bug is reported on -bug.
Forwarding to -dev should be sufficient.

> Carl

Trevor