Re: Issue 1622 in lilypond: Dynamic spanner not printed within gracenotes

[Trevor Daniels]

Colin Campbell wrote Wednesday, May 04, 2011 2:08 AM


> On 11-05-03 01:01 PM, Keith OHara wrote:
> >   <lilypond<at>  googlecode.com>  writes:
> > > Updates:
> > > Status: Verified
> > >
> > > Comment #6 on issue 1622 by address@hidden: Dynamic 
> > > spanner not
> > > printed within grace notes
> > > http://code.google.com/p/lilypond/issues/detail?id=1622
> > >
> > > Verified 2.15.0
> > But 2.15.0 has not been released yet, Colin.
> >
> > Another change between now and the release might destroy the fix
> > (which has happened when a fix caused a worse problem an had to 
> > be taken back)
> > or the fix might not appear in the released build for which it 
> > was intended
> > (which has also happened recently).
> >
> > I am rubbish at understanding policy documents (and following 
> > instructions
> > in general) but I think the CG intends that we test only the 
> > released builds
> > when it says 'official GUB version'.
>
> Actually, 2.15.0 _is_ the version reported by the gub I built 
> yesterday, Keith:
>
> > address@hidden:~$ which lilypond
> > /home/colin/bin/lilypond
> > address@hidden:~$ lilypond -v
> > GNU LilyPond 2.15.0

Keith was quite right.  The point is that you should
test only the official releases built by Graham, and
he has not made a 2.15.0 release.  You should
never update the bug database by testing a locally
built release as the point in git history when it was
built is not defined, and will definitely be different
from the state of git when/if 2.15.0 is officially
released.

BTW, GUB is an acronym for Grand Unified Builder - the
name of the cross-platform building mechanism that
Graham uses to generate all the various binaries in
an official release.  Hence a GUB binary is a binary
version of LilyPond built by this mechanism.

Trevor