@c -*- coding: utf-8; mode: texinfo; -*-
@c This file is part of lilypond-web.texi and community.itexi

@c when you add a new item, consider moving the lowest item(s)
@c into news.itexi.

@c keep two blank lines between news entries

@c used for news about the upcoming release; see CG 10.2


@newsItem
@subsubheading LilyPond 2.15.42 released!  @emph{August 02, 2012}

We are happy to announce the release of LilyPond 2.15.42.  This
release contains the usual number of bugfixes.

It is strongly recommended that normal users do @strong{not} use
this release, and instead use the stable 2.14 version.  Please
note that due to a few Critical bugs, this is not the next release
candidate.

@newsEnd


@newsItem
@subsubheading The LilyPond Report #27. @emph{August 2, 2012}

The @emph{LilyPond Report} is back, with some interesting insights on
new Scheme-related features recently added by our community’s only paid
developer David Kastrup (thanks to your
@uref{http://lilypond.org/sponsoring.html, continuing donations}).  Also
to be found in this issue are an overview of some lesser-known LilyPond
companion projects, and a handful of more shallow factoids.

Come
@uref{http://news.lilynet.net/?The-LilyPond-Report-27, read
LilyPond Report 27} now; comments and contributions are
warmly encouraged!

@newsEnd


@newsItem
@subsubheading Release candidate withdrawn  @emph{July 11, 2012}

We have discovered a regression since 2.14.2, so lilypond 2.15.41
is no longer a candidate for the 2.16.0 release.  However, please
continue testing it -- we would like to discover (and fix!) any
more regressions as soon as possible.  If you discover any
problems, please send us @ref{Bug reports}.

@newsEnd


@newsItem
@subsubheading Release candidate 8 of 2.16 - LilyPond 2.15.41 released!  @emph{July 4, 2012}

LilyPond 2.15.41 is out; this is the eighth release candidate of
the upcoming 2.16 stable release.  All users are invited to
experiment with this version.  New features since 2.14.2 are
listed in the @qq{Changes} manual on the website section about
@ref{Development}.

There are no known Critical issues with this release.  If no
Critical bugs are found, then the official 2.16.0 release will be
on 18 July 2012.  If you discover any problems, please send us
@ref{Bug reports}.

@newsEnd