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 keep two blank lines between news entries
9 @c FIXME: fill in number
10 @c used for news about the upcoming release; see CG x.y
13 @subsubheading LilyPond 2.13.23 released! @emph{June 3, 2010}
15 We are happy to announce the release of LilyPond 2.13.23. This
16 release contains the usual number of bugfixes. However, a number
17 of critical issues still remain, so this release is intended for
22 @subsubheading LilyPond 2.13.22 released! @emph{May 27, 2010}
24 We are happy to announce the release of LilyPond 2.13.22. This
25 release contains the usual number of bugfixes. However, a number
26 of critical issues still remain, so this release is intended for
31 @subsubheading LilyPond 2.13.21 released! @emph{May 12, 2010}
33 We are happy to announce the release of LilyPond 2.13.21. This
34 release contains the usual number of bugfixes. However, a number
35 of critical issues still remain, so this release is intended for
38 This release should be of particular interest to package
39 maintainers: we have made a few changes to the configure script
40 and the required libraries. Barring any urgent bug reports, this
41 is the build system and libraries that will be used for the next
47 @subsubheading LilyPond Report #18. @emph{May 11, 2010}
49 The @emph{LilyPond Report} is back, with its two
50 @qq{grumpy-and-fluffy} editors! This issue will be filled
51 with emotion and coolness, paper bags and zigzag-ending
52 staves, plus the usual Frogs and Bugs.
55 @uref{http://news.lilynet.net/The-LilyPond-Report-18, read
56 LilyPond Report 18} now; comments and contributions are