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 9683cd4651812c3850ea1921cced18f4d933dd82..46d45d3e3148f9f8122eef885a4a8ec90f42c5ae 100644 (file)
--- a/Documentation/web/news-front.itexi
+++ b/Documentation/web/news-front.itexi
@@ -9,10 +9,10 @@
 @c used for news about the upcoming release; see CG 10.2
 
 @newsItem
-@subheading LilyPond 2.19.40 released  @emph{April 17, 2016}
+@subheading LilyPond 2.19.42 released  @emph{May 15, 2016}
 
 We are happy to announce the release of LilyPond
-2.19.40.  This release includes a number of enhancements, and contains some
+2.19.42.  This release includes a number of enhancements, and contains some
 work in progress.  You will have access to the very latest features, but
 some may be incomplete, and you may encounter bugs and crashes.  If you
 require a stable version of Lilypond, we recommend using the 2.18
@@ -34,6 +34,24 @@ updated manuals.  We recommend all users to upgrade to this version.
 @newsEnd
 
 
+@newsItem
+@subheading Two LilyPond projects in Google Summer of Code 2016  @emph{April 23, 2016}
+
+We are happy to see two students, Nathan Chou and Jeffery Shivers, working on
+LilyPond as participants in the Google Summer of Code this year.  We hope they
+produce great results and stay in the developer community afterwards.
+
+Nathan will tackle an annoying limitation, namely the unability of spanners
+to cross voices.  His work will make a class of ugly workarounds obsolete.
+Jeffery will bring the ScholarLY package[1] to production quality and add a
+LaTeX package to it, making it possible to create beautiful critical reports
+from data encoded directly in the LilyPond score.
+
+[1] @uref{https://github.com/openlilylib/scholarly}@*
+
+@newsEnd
+
+
 @newsItem
 @subheading Lilypond 2.18.0 released!  @emph{December 29, 2013}