Release: update news.

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

diff --git a/Documentation/web/news-front.itexi b/Documentation/web/news-front.itexi
index fd3d97a018692946080c98e3bf761dea0d7987ab..d21890a977ec2a1a9da867c9220f79f891208c91 100644 (file)
--- a/Documentation/web/news-front.itexi
+++ b/Documentation/web/news-front.itexi
@@ -9,19 +9,16 @@
 @c used for news about the upcoming release; see CG 10.2
 
 @newsItem
-@subsubheading LilyPond 2.17.95 released!  @emph{November 3, 2013}
+@subsubheading LilyPond 2.17.96 released!  @emph{November 24, 2013}
 
-We are excited to announce the release of LilyPond@tie{}2.17.95 as
-beta release for the upcoming stable release@tie{}2.18.  The
-developers are still busy finding solutions for some last-minute
-problems, but the release is supposed to be feature-complete, the
+We are excited to announce the release of LilyPond@tie{}2.17.96 as
+a further beta release for the upcoming stable release@tie{}2.18.  The
+developers believe the release to be feature-complete, the
 documentation to be accurate, and no important issues to be
 overlooked.  For upgrading the syntax of your input files to the
-latest version, see
-@uref{http://www.lilypond.org/doc/v2.17/Documentation/usage/updating-files-with-convert_002dly.html,
-Updating files with convert-ly}.
+latest version, see @uref{http://www.lilypond.org/doc/v2.17/Documentation/usage/updating-files-with-convert_002dly, Updating files with convert-ly}.
 Please test this release and report back any problems, see
-@uref{http://www.lilypond.org/bug-reports.html, Bug reports}.
+@uref{http://www.lilypond.org/website/bug-reports.html, Bug reports}.
 
 @newsEnd