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 used for news about the upcoming release; see CG 10.2
13 @subsubheading LilyPond 2.13.45 released! @emph{Jan 3, 2010}
15 We are happy to announce the release of LilyPond 2.13.45. This
16 release contains the usual number of bugfixes. However, a number
17 of critical issues still remain, so this release is intended for
24 @subsubheading Beta test three of 2.14 -- LilyPond 2.13.44 released! @emph{Dec 25, 2010}
26 LilyPond 2.13.44 is out; this is the third beta test of the
27 upcoming 2.14 stable release. Users are invited to experiment
28 with this version. New features since 2.12.3 are listed in the
29 @qq{Changes} manual on the website section about
32 There is still one Critical problem with this release: in one
33 case, the vertical spacing is much too compressed. If you decide
34 to test this version, do not be surprised to discover problems;
35 just send us polite @ref{Bug reports}.
41 @subsubheading Beta test two of 2.14 -- LilyPond 2.13.43 released! @emph{Dec 14, 2010}
43 LilyPond 2.13.43 is out; this is the second beta test of the
44 upcoming 2.14 stable release. Users are invited to experiment
45 with this version. New features since 2.12.3 are listed in the
46 @qq{Changes} manual on the website section about
49 There is still one Critical problem with this release: in one
50 case, the vertical spacing is much too compressed. If you decide
51 to test this version, do not be surprised to discover problems;
52 just send us polite @ref{Bug reports}.
58 @subsubheading LilyPond 2.13.42 released! @emph{Dec 8, 2010}
60 We are happy to announce the release of LilyPond 2.13.42. This
61 release contains the usual number of bugfixes. However, a number
62 of critical issues still remain, so this release is intended for
65 Please note that this is @strong{not} the second beta test. Due
66 to a number of untested changes to our build process, we cannot be
67 at all confident about the quality of this release.