@c used for news about the upcoming release; see CG 10.2
@newsItem
-@subsubheading Release candidate 2 of 2.14 - LilyPond 2.13.49 released! @emph{Feb 9, 2011}
+@subsubheading LilyPond 2.13.59 released! @emph{April 10, 2011}
-LilyPond 2.13.49 is out; this is the second 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}.
+We are happy to announce the release of LilyPond 2.13.59. This
+release contains the usual number of bugfixes.
-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 Feb 23, 2011. If you discover any problems, please send us
-@ref{Bug reports}.
+Please note that this is @strong{not} the next release candidate,
+due to a few remaining Critical bugs.
@newsEnd
@newsItem
-@subsubheading LilyPond 2.13.48 released! @emph{Feb 5, 2011}
-
-We are happy to announce the release of LilyPond 2.13.48. This
-release contains the usual number of bugfixes. However, a number
-of critical issues still remain, so this release is intended for
-developers only.
-
-@newsEnd
-
+@subsubheading Release candidate 6 of 2.14 - LilyPond 2.13.58 released! @emph{April 7, 2011}
+LilyPond 2.13.58 is out; this is the sixth 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}.
-@newsItem
-@subsubheading LilyPond 2.13.47 released! @emph{Jan 28, 2011}
-
-We are happy to announce the release of LilyPond 2.13.47. This
-release contains the usual number of bugfixes. However, a number
-of critical issues still remain, so this release is intended for
-developers only.
+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 14, 2011. If you discover any problems, please send us
+@ref{Bug reports}.
@newsEnd
-
-