1 @c -*- coding: utf-8; mode: texinfo; -*-
2 @c This file is part of lilypond-web.texi and community.itexi
4 @c when you add a new item, consider moving the lowest item(s)
5 @c into news-old.itexi.
7 @c FIXME: fill in number
8 @c used for news about the upcoming release; see CG x.y
9 @c DO NOT WRITE BETWEEN THESE LINES
10 @c DO NOT WRITE BETWEEN THESE LINES
13 @subsubheading LilyPond 2.13.19 released! @emph{April 24, 2010}
15 We are happy to announce the release of LilyPond 2.13.19. This
16 release contains the usual number of bugfixes. However, 11
17 critical issues still remain, so this release is intended for
22 @subsubheading LilyPond 2.13.18 released! @emph{April 16, 2010}
24 We are happy to announce the release of LilyPond 2.13.18. This
25 release contains the usual number of bugfixes, along with improved
26 website translations. However, 14 critical issues still remain,
27 so this release is intended for developers only.
31 @subsubheading LilyPond 2.13.17 released! @emph{April 2, 2010}
33 We are happy to announce the release of LilyPond 2.13.17. This
34 release includes bugfixes for 4 critical issues. However, 15
35 critical issues still remain, so this release is intended for
40 @subsubheading LilyPond 2.13.16 released! @emph{March 15, 2010}
42 We are happy to announce the release of LilyPond 2.13.16. This
43 release is intended for developers only, and includes the usual
48 @subsubheading LilyPond 2.13.15 released! @emph{March 4, 2010}
50 We are happy to announce the release of LilyPond 2.13.15. This
51 release is intended for developers only, and includes a few
52 updates to the binary build process in addition to the usual round
57 @subsubheading LilyPond Report #17. @emph{March 1, 2010}
59 Yay, the Report is back, with a new team! It has been said that
60 two heads are better than one — does it apply to newsletters as
61 well? Read on and let us know! In this issue we’ll talk about
62 websites and poetry, frogs and bugs, not to mention an extensive
63 review of the Frescobaldi editor!
65 What are you waiting for? Come
66 @uref{http://news.lilynet.net/The-LilyPond-Report-17, read
67 LilyPond Report 17} now!