On 9/26/10 3:14 AM, "Trevor Daniels" <[email protected]> wrote:

> Carl wrote
> 
>> Comment #2 on issue 1273 by Carl.D.Sorensen: Woodwind Diagrams
>> lead to  Ghostscript error in latest git
>> http://code.google.com/p/lilypond/issues/detail?id=1273
> 
>> 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.  This
report said the code worked properly on the latest development release
(2.13.34-1), but not in 2.13.35.  But there *isn't* a 2.13.35.  2.13.35 is
whatever I build on my machine based on latest git.  It's a moving target.

Problems with a git build are reported on -devel, with a reference to a
commit SHA1.  That way we can track it down, and hopefully get it fixed
before a development release happens.

Thanks,

Carl


_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Reply via email to