@c when you add a new item, consider moving the lowest item(s)
@c into news-old.itexi.
-@newsItem
-@subsubheading New Website! @emph{October 3, 2009}
+@c FIXME: fill in number
+@c used for news about the upcoming release; see CG x.y
+@c DO NOT WRITE BETWEEN THESE LINES
+@c DO NOT WRITE BETWEEN THESE LINES
-As you can see, we have a new website design. Many thanks to
-texi2html and CSS for being so flexible!
+@newsItem
+@subsubheading LilyPond 2.13.16 released! @emph{March 15, 2010}
+We are happy to announce the release of LilyPond 2.13.16. This
+release is intended for developers only, and includes the usual
+round of bugfixes.
@newsEnd
+@newsItem
+@subsubheading LilyPond 2.13.15 released! @emph{March 4, 2010}
+
+We are happy to announce the release of LilyPond 2.13.15. This
+release is intended for developers only, and includes a few
+updates to the binary build process in addition to the usual round
+of bugfixes.
+@newsEnd
@newsItem
-@subsubheading LilyPond Report #16. @emph{September 6, 2009}
+@subsubheading LilyPond Report #17. @emph{March 1, 2010}
+
+Yay, the Report is back, with a new team! It has been said that
+two heads are better than one — does it apply to newsletters as
+well? Read on and let us know! In this issue we’ll talk about
+websites and poetry, frogs and bugs, not to mention an extensive
+review of the Frescobaldi editor!
-The LilyPond Report is back! This short, informal opinion column is
-about the LilyPond project: its team, its world, its community.
-Read @uref{http://news.lilynet.net/The-LilyPond-Report-16, issue 16}
-now!
+What are you waiting for? Come
+@uref{http://news.lilynet.net/The-LilyPond-Report-17, read
+LilyPond Report 17} now!
@newsEnd