@c FIXME: fill in number
@c used for news about the upcoming release; see CG x.y
@c DO NOT WRITE BETWEEN THESE LINES
-@newsItem
-@subsubheading LilyPond 2.13.10 released! @emph{December 31, 2009}
-
-We are happy to announce the release of LilyPond 2.13.10. This
-release is intended for developers only, and brings a number of
-improvements such as predictable regression test output filenames
-and English names for feta filenames.
-
-@newsEnd
@c DO NOT WRITE BETWEEN THESE LINES
-
@newsItem
-@subsubheading LilyPond 2.12.3 released! @emph{December 20, 2009}
-
-We are happy to announce the release of LilyPond 2.12.3. This
-version contains the long-awaited fix for our GUI on MacOS X 10.5
-and 10.6. In addition to the GUI fixes, this version contains
-dozens of bugfixes backported from the unstable development
-version.
-
-We recommend that all users upgrade to this version. This is the
-last planned release in the 2.12 stable series; development now
-shifts towards the upcoming 2.14 series.
+@subsubheading LilyPond 2.13.13 released! @emph{February 13, 2010}
+We are happy to announce the release of LilyPond 2.13.13. This
+release is intended for developers only, and fixes various
+problems with documentation build system as well as adding an
+output-preview-framework for our SVG backend. In addition, the
+binaries are now approximately 6 megabytes smaller.
@newsEnd
@newsItem
-@subsubheading LilyPond 2.13.9 released! @emph{December 12, 2009}
-
-LilyPond 2.13.9 is now out. From 2.13.9 onwards, LilyPond is
-licensed under the GNU GPL v3+ for code, and the GNU FDL 1.3+ for
-documentation. In addition to the usual round of bugfixes, this
-release adds a shortcut for repeated chords.
-
-Please note that 2.13 is an @strong{unstable development} branch;
-normal users should continue to use 2.12.
+@subsubheading LilyPond 2.13.12 released! @emph{February 2, 2010}
+We are happy to announce the release of LilyPond 2.13.12. This
+release is intended for developers only, and brings more stability
+and fewer bugs to the build system and Contributor's Guide.
@newsEnd