+-@subsubheading LilyPond 2.16.1 released! @emph{November 9, 2012}
++@subsubheading LilyPond 2.16.2 released! @emph{January 4, 2013}
+
+-We are happy to announce the release of LilyPond 2.16.1. This has a number of
+-updates to the previous stable version, and should cause no problems. We
+-recommend that everybody upgrade to this version.
++We are happy to announce the release of LilyPond 2.16.2. This release is mainly
++to correct a problem with lilypond-book running on Windows. We recommend that
++only people requiring this functionality upgrade to this version.
+ @newsEnd
+
+ @newsItem
+-@subsubheading LilyPond 2.17.6 released! @emph{November 3, 2012}
++@subsubheading LilyPond 2.17.9 released! @emph{December 15, 2012}
+
+-We are happy to announce the release of LilyPond 2.17.6. This
++We are happy to announce the release of LilyPond 2.17.9. This
+ release contains the usual number of bugfixes and 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
+@@ -28,30 +28,41 @@ a stable version of Lilypond, we recommend using the 2.16 version.
+ @newsEnd
+
+ @newsItem
+-@subsubheading LilyPond 2.17.5 released! @emph{October 20, 2012}
++@subsubheading The LilyPond Report #28. @emph{November 12, 2012}
+
+-We are happy to announce the release of LilyPond 2.17.5. This
+-release contains the usual number of bugfixes and 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.16 version.
++The @uref{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,
++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
++venue.