X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fweb%2Fnews-front.itexi;h=77141c73b0d3c95eb07b438d5e33a48275a4fa98;hb=27477ca707bc97de3c401e41e16c4fbb7fa51c18;hp=2edf682350ca73389199761972adffc77e0f90bd;hpb=135a009da2996c41270466e9f1a3a1db898a4e76;p=lilypond.git

diff --git a/Documentation/web/news-front.itexi b/Documentation/web/news-front.itexi
index 2edf682350..77141c73b0 100644
--- a/Documentation/web/news-front.itexi
+++ b/Documentation/web/news-front.itexi
@@ -2,16 +2,17 @@
 @c This file is part of lilypond-web.texi and community.itexi
 
 @c when you add a new item, consider moving the lowest item(s)
-@c into news-old.itexi.
+@c into news.itexi.
 
 @c keep two blank lines between news entries
 
 @c used for news about the upcoming release; see CG 10.2
 
+
 @newsItem
-@subsubheading LilyPond 2.15.14 released!  @emph{October 7, 2011}
+@subsubheading LilyPond 2.15.28 released!  @emph{Feb 3, 2012}
 
-We are happy to announce the release of LilyPond 2.15.14.  This
+We are happy to announce the release of LilyPond 2.15.28.  This
 release contains the usual number of bugfixes.
 
 It is strongly recommended that normal users do @strong{not} use
@@ -23,9 +24,9 @@ candidate.
 
 
 @newsItem
-@subsubheading LilyPond 2.15.13 released!  @emph{September 27, 2011}
+@subsubheading LilyPond 2.15.27 released!  @emph{Jan 24, 2012}
 
-We are happy to announce the release of LilyPond 2.15.13.  This
+We are happy to announce the release of LilyPond 2.15.27.  This
 release contains the usual number of bugfixes.
 
 It is strongly recommended that normal users do @strong{not} use
@@ -37,41 +38,62 @@ candidate.
 
 
 @newsItem
-@subsubheading Release candidate 2 cancelled @emph{Sep 23, 2011}
+@subsubheading The LilyPond Report #23. @emph{Jan 20, 2012}
+
+The @emph{LilyPond Report} is back, with developer
+David Kastrup as a new editor!  This issue features
+an exposé on some of the new, handy commands
+recently added to LilyPond, as well as an interview
+with LilyPond contributor and composer Mike Solomon.
+
+Come
+@uref{http://news.lilynet.net/?The-LilyPond-Report-23, read
+LilyPond Report 23} now; comments and contributions are
++warmly encouraged!
+
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.15.26 released!  @emph{Jan 16, 2012}
+
+We are happy to announce the release of LilyPond 2.15.26.  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.
 
-The release countdown is cancelled due to the discovery of a
-Critical regression.
+The 2.15.25 has been skipped due to build problems.
 
 @newsEnd
 
 
 @newsItem
-@subsubheading Release candidate 2 of 2.16 - LilyPond 2.15.12 released!  @emph{Sep 20, 2011}
+@subsubheading LilyPond 2.15.24 released!  @emph{Jan 07, 2012}
 
-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}.
+We are happy to announce the release of LilyPond 2.15.24.  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.16.0 release will be
-on 27 Sep 2011.  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 LilyPond 2.15.11 released!  @emph{September 11, 2011}
+@subsubheading LilyPond 2.15.23 released!  @emph{Dec 21, 2011}
 
-We are happy to announce the release of LilyPond 2.15.11.  This
+We are happy to announce the release of LilyPond 2.15.23.  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.
+note that due to a few Critical bugs, this is not the next release
+candidate.
 
 @newsEnd