@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-old.itexi. @c keep two blank lines between news entries @c used for news about the upcoming release; see CG 10.2 @newsItem @subsubheading Release candidate 4 of 2.14 - LilyPond 2.13.56 released! @emph{Mar 29, 2011} LilyPond 2.13.56 is out; this is the fourth release candidate of the upcoming 2.14 stable release. All users are invited to experiment with this version. New features since 2.12.3 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.14.0 release will be on April 2, 2011. If you discover any problems, please send us @ref{Bug reports}. @newsEnd @newsItem @subsubheading LilyPond 2.13.55 released! @emph{Mar 22, 2011} We are happy to announce the release of LilyPond 2.13.55. This release contains the usual number of bugfixes. Please note that this is @strong{not} the fourth release candidate, due to a few remaining Critical bugs. @newsEnd @newsItem @subsubheading Release candidate 3 withdrawn @emph{Mar 15, 2011} We have discovered a regression since 2.12.3, so lilypond 2.13.54 is no longer a candidate for the 2.14.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 3 of 2.14 - LilyPond 2.13.54 released! @emph{Mar 13, 2011} LilyPond 2.13.54 is out; this is the third release candidate of the upcoming 2.14 stable release. All users are invited to experiment with this version. New features since 2.12.3 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.14.0 release will be on March 27, 2011. If you discover any problems, please send us @ref{Bug reports}. @newsEnd