Merge branch 'master' of git://git.savannah.gnu.org/lilypond.git

[lilypond.git] / Documentation / web / news-front.itexi

diff --git a/Documentation/web/news-front.itexi b/Documentation/web/news-front.itexi
index 4df56f242713c64909c5a84216af4a1bb1e70a4a..4464586067f990ea2f3064ac466eda1c384fe132 100644 (file)
--- a/Documentation/web/news-front.itexi
+++ b/Documentation/web/news-front.itexi
@@ -9,29 +9,36 @@
 @c used for news about the upcoming release; see CG 10.2
 
 @newsItem
-@subsubheading LilyPond 2.13.32 released!  @emph{Sep 3, 2010}
+@subsubheading LilyPond 2.15.7 released!  @emph{July 29, 2011}
 
-We are happy to announce the release of LilyPond 2.13.32.  This
-release contains the usual number of bugfixes.  However, a number
-of critical issues still remain, so this release is intended for
-developers only.
+We are happy to announce the release of LilyPond 2.15.7.  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.
+
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.15.6 released!  @emph{July 26, 2011}
+
+We are happy to announce the release of LilyPond 2.15.6.  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.
 
 @newsEnd
 
 
 @newsItem
-@subsubheading LilyPond Report #20.  @emph{Sep 2, 2010}
-
-The @emph{LilyPond Report} is back, with its two
-@qq{grumpy-and-fluffy} editors! This issue contains a review of an
-online notation editor using lilypond, along with the regular
-release news, snippet of the report, news from the frog pond, and
-the bug report of the report!
-
-Come
-@uref{http://news.lilynet.net/The-LilyPond-Report-20, read
-LilyPond Report 20} now; comments and contributions are
-warmly encouraged!
+@subsubheading LilyPond 2.14.2 released!  @emph{July 25, 2011}
+
+We are happy to announce the release of LilyPond 2.14.2.  This
+fixes a few minor bugs in the stable version, and should cause no
+problems.  We recommend that everybody upgrade to this version.
+
 @newsEnd