X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fweb%2Fnews-front.itexi;h=2edf682350ca73389199761972adffc77e0f90bd;hb=84fa3cb9de968a45ef1bd07e9fe96cec1f3eaf87;hp=dbb6831bd9d12b290cb5379d4de98af621a84e8a;hpb=60fc32ec59fd97456218332612b87b821968da84;p=lilypond.git

diff --git a/Documentation/web/news-front.itexi b/Documentation/web/news-front.itexi
index dbb6831bd9..2edf682350 100644
--- a/Documentation/web/news-front.itexi
+++ b/Documentation/web/news-front.itexi
@@ -8,54 +8,70 @@
 
 @c used for news about the upcoming release; see CG 10.2
 
+@newsItem
+@subsubheading LilyPond 2.15.14 released!  @emph{October 7, 2011}
+
+We are happy to announce the release of LilyPond 2.15.14.  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 Alpha test three of 2.14 -- LilyPond 2.13.37 released!  @emph{Oct 25, 2010}
+@subsubheading LilyPond 2.15.13 released!  @emph{September 27, 2011}
 
-LilyPond 2.13.37 is out; this is the third alpha test of the
-upcoming 2.14 stable release.  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.15.13.  This
+release contains the usual number of bugfixes.
 
-There are still some Critical problems with this release: the
-vertical spacing is suspicious in two cases, and lilypond can
-crash with some odd input.  If you decide to test 2.13.37, do not
-be surprised to discover problems; just send us polite
-@ref{Bug reports}.
+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 Release candidate 2 cancelled @emph{Sep 23, 2011}
+
+The release countdown is cancelled due to the discovery of a
+Critical regression.
 
 @newsEnd
 
 
 @newsItem
-@subsubheading LilyPond 2.13.36 released!  @emph{Oct 19, 2010}
+@subsubheading Release candidate 2 of 2.16 - LilyPond 2.15.12 released!  @emph{Sep 20, 2011}
 
-We are happy to announce the release of LilyPond 2.13.36.  This
-release contains the usual number of bugfixes.  However, a number
-of critical issues still remain, so this release is intended for
-developers only.
+LilyPond 2.15.12 is out; this is the second 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}.
 
-Please note that this is @strong{not} the third alpha test.  Due
-to a number of untested changes to our build process, we cannot be
-at all confident about the quality of this release.
+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 27 Sep 2011.  If you discover any problems, please send us
+@ref{Bug reports}.
 
 @newsEnd
 
 
 @newsItem
-@subsubheading The LilyPond Report #21. @emph{Oct 3, 2010}
-
-The @emph{LilyPond Report} is back, with its two
-@qq{grumpy-and-fluffy} editors! This issue mainly deals with
-microtonal notation in LilyPond, but does also include a how-to
-about running LilyPond from an USB key, not to forget the regular
-release news, the bug report of the Report, and some news from
-the frog pond!
-
-Come
-@uref{http://news.lilynet.net/The-LilyPond-Report-21, read
-LilyPond Report 21} now; comments and contributions are
-warmly encouraged!
+@subsubheading LilyPond 2.15.11 released!  @emph{September 11, 2011}
+
+We are happy to announce the release of LilyPond 2.15.11.  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 the possibility of a few Critical bugs, this is
+not the next release candidate.
 
 @newsEnd