Re: misplaced composer field

[David Kastrup]

Martin Tarenskeen <address@hidden> writes:

> Hi,
>
> Using Lilypond 2.19.14 I see the "composer" field is completely
> misplaced in the output.

<URL:https://code.google.com/p/lilypond/issues/detail?id=4102>

Will be fixed in 2.19.15.  I quote the announcement of 2.19.14:

    LilyPond 2.19.14 released September 14, 2014

    We are happy to announce the release of LilyPond 2.19.14. This
    release includes a number of enhancements, and contains some work in
    progress. You will have access to the very latest features, but some
    may be incomplete, and you may encounter bugs and crashes. If you
    require a stable version of Lilypond, we recommend using the 2.18
    version.

The release schedule of developer releases basically provides regular
indiscriminate snapshots of the current development, so even when
blunders like that are reported and corrected reasonably fast, they may
make it into developer releases.  The only advantages a developer
release has over just getting and compiling master is that someone else
does the work, that it's available on a number of platforms where doing
compilation yourself would be rather tricky, and that it is known to
work with a larger variety of compilers and crosscompiling environments
(the cross-compiled build results are not actually tested before
distribution, but the overall track record for them tends to be quite
consistent).

-- 
David Kastrup