X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fweb%2Fnews-front.itexi;h=93ed4162df722a44bcb2c8c8fd03fa65173a5491;hb=f42142c17b68d84721597f8abf400fa18364b118;hp=a68b6571067b8f654c87ef1f7ea3aa447380571e;hpb=16ac0db39d8cca1de68ce79154386764172aca10;p=lilypond.git

diff --git a/Documentation/web/news-front.itexi b/Documentation/web/news-front.itexi
index a68b657106..93ed4162df 100644
--- a/Documentation/web/news-front.itexi
+++ b/Documentation/web/news-front.itexi
@@ -10,25 +10,38 @@
 
 
 @newsItem
-@subsubheading The LilyPond Report #25. @emph{Apr 1st, 2012}
+@subsubheading Release candidate withdrawn  @emph{July 11, 2012}
 
-The @emph{LilyPond Report} is back, with a rather unusual
-issue featuring our young Polish contributor Janek Warchoł!
-Also included in this issue are quite a few unexpected items,
-including (but not limited to)… a cooking recipe!
+We have discovered a regression since 2.14.2, so lilypond 2.15.41
+is no longer a candidate for the 2.16.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}.
 
-Come
-@uref{http://news.lilynet.net/?The-LilyPond-Report-25, read
-LilyPond Report 25} now; comments and contributions are
-warmly encouraged!
+@newsEnd
+
+
+@newsItem
+@subsubheading Release candidate 8 of 2.16 - LilyPond 2.15.41 released!  @emph{July 4, 2012}
+
+LilyPond 2.15.41 is out; this is the eighth 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}.
+
+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 18 July 2012.  If you discover any problems, please send us
+@ref{Bug reports}.
 
 @newsEnd
 
 
 @newsItem
-@subsubheading LilyPond 2.15.35 released!  @emph{Mar 28, 2012}
+@subsubheading LilyPond 2.15.40 released!  @emph{June 05, 2012}
 
-We are happy to announce the release of LilyPond 2.15.35.  This
+We are happy to announce the release of LilyPond 2.15.40.  This
 release contains the usual number of bugfixes.
 
 It is strongly recommended that normal users do @strong{not} use
@@ -40,15 +53,48 @@ candidate.
 
 
 @newsItem
-@subsubheading LilyPond 2.15.34 released!  @emph{Mar 19, 2012}
+@subsubheading Release candidate withdrawn  @emph{June 01, 2012}
 
-We are happy to announce the release of LilyPond 2.15.34.  This
-release contains the usual number of bugfixes.
+We have discovered a regression since 2.14.2, so lilypond 2.15.39
+is no longer a candidate for the 2.16.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}.
 
-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 7 of 2.16 - LilyPond 2.15.39 released!  @emph{May 22, 2012}
+
+LilyPond 2.15.39 is out; this is the seventh 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}.
+
+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 05 June 2012.  If you discover any problems, please send us
+@ref{Bug reports}.
+
+@newsEnd
+
+
+@newsItem
+@subsubheading The LilyPond Report #26. @emph{May 22, 2012}
+
+The @emph{LilyPond Report} is back, with a new editor on board -
+Pavel Roskin, who tells us about his adventures in strange lands
+of compiler bugs!  There is also a detailed report about current
+development status, and an analysis of example LilyPond output -
+see for yourself how close (or how far?) are we from matching
+the quality of hand-engraved scores.
+
+Come
+@uref{http://news.lilynet.net/?The-LilyPond-Report-26, read
+LilyPond Report 26} now; comments and contributions are
+warmly encouraged!
 
 @newsEnd