@c used for news about the upcoming release; see CG 10.2
@newsItem
-@subheading LilyPond 2.19.23 released @emph{July 12, 2015}
+@subheading LilyPond 2.19.28 released @emph{September 27, 2015}
We are happy to announce the release of LilyPond
-2.19.23. This release includes a number of enhancements, and contains some
+2.19.28. 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
@newsItem
@subheading The LilyPond Report #28. @emph{November 12, 2012}
-The @uref{http://news.lilynet.net/?The-LilyPond-Report-28, October
+The @uref{http://web.archive.org/web/20110325004849/http://news.lilynet.net/?The-LilyPond-Report-28, October
issue of the @emph{LilyPond Report}} focuses on the
-@uref{http://news.lilynet.net/?LilyPond-meeting-in-Waltrop,
+@uref{http://web.archive.org/web/20110325004849/http://news.lilynet.net/?LilyPond-meeting-in-Waltrop,
meeting of LilyPond developers and users} in Waltrop, Germany last
August. Of course, there are also some musings on LilyPond
triggered by the release of 2.16.0 and 2.17.0 occuring from that
There are also two monthly financial reports from David Kastrup
whose work on LilyPond is
-@uref{http://news.lilynet.net/?The-LilyPond-Report-24#an_urgent_request_for_funding,
+@uref{http://web.archive.org/web/20110325004849/http://news.lilynet.net/?The-LilyPond-Report-24#an_urgent_request_for_funding,
solely paid for} by financial contributions from other developer
and users (thank you!), and a report about experiences from
@uref{http://scorio.com, a web-based music typesetting service}
using LilyPond internally.
-Come @uref{http://news.lilynet.net/?The-LilyPond-Report-28, read
+Come @uref{http://web.archive.org/web/20110325004849/http://news.lilynet.net/?The-LilyPond-Report-28, read
LilyPond Report 28} now; comments and contributions are warmly
encouraged!
@newsEnd