@c when you add a new item, consider moving the lowest item(s)
@c into news-old.itexi.
-@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
+@c keep two blank lines between news entries
-@newsItem
-@subsubheading LilyPond 2.13.18 released! @emph{April 16, 2010}
+@c used for news about the upcoming release; see CG 10.2
-We are happy to announce the release of LilyPond 2.13.18. This
-release contains the usual number of bugfixes, along with improved
-website translations. However, 14 critical issues still remain,
-so this release is intended for developers only.
-@newsEnd
@newsItem
-@subsubheading LilyPond 2.13.17 released! @emph{April 2, 2010}
+@subsubheading Alpha test four of 2.14 -- LilyPond 2.13.38 released! @emph{Oct 31, 2010}
+
+LilyPond 2.13.38 is out; this is the fourth alpha test of the
+upcoming 2.14 stable release. Users are invited to experiment
+with this version. New features since 2.12.3 are listed in the
+@qq{Changes} manual on the website section about
+@ref{Development}.
+
+There are still some Critical problems with this release: the
+vertical spacing is suspicious in two cases, and lilypond can
+crash with some odd input. If you decide to test 2.13.38, do not
+be surprised to discover problems; just send us polite
+@ref{Bug reports}.
-We are happy to announce the release of LilyPond 2.13.17. This
-release includes bugfixes for 4 critical issues. However, 15
-critical issues still remain, so this release is intended for
-developers only.
@newsEnd
+
@newsItem
-@subsubheading LilyPond 2.13.16 released! @emph{March 15, 2010}
+@subsubheading Alpha test three of 2.14 -- LilyPond 2.13.37 released! @emph{Oct 25, 2010}
+
+LilyPond 2.13.37 is out; this is the third alpha test of the
+upcoming 2.14 stable release. Users are invited to experiment
+with this version. New features since 2.12.3 are listed in the
+@qq{Changes} manual on the website section about
+@ref{Development}.
+
+There are still some Critical problems with this release: the
+vertical spacing is suspicious in two cases, and lilypond can
+crash with some odd input. If you decide to test 2.13.37, do not
+be surprised to discover problems; just send us polite
+@ref{Bug reports}.
-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}
+@subsubheading LilyPond 2.13.36 released! @emph{Oct 19, 2010}
+
+We are happy to announce the release of LilyPond 2.13.36. This
+release contains the usual number of bugfixes. However, a number
+of critical issues still remain, so this release is intended for
+developers only.
+
+Please note that this is @strong{not} the third alpha test. Due
+to a number of untested changes to our build process, we cannot be
+at all confident about the quality of this release.
-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 #17. @emph{March 1, 2010}
+@subsubheading The LilyPond Report #21. @emph{Oct 3, 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 @emph{LilyPond Report} is back, with its two
+@qq{grumpy-and-fluffy} editors! This issue mainly deals with
+microtonal notation in LilyPond, but does also include a how-to
+about running LilyPond from an USB key, not to forget the regular
+release news, the bug report of the Report, and some news from
+the frog pond!
-What are you waiting for? Come
-@uref{http://news.lilynet.net/The-LilyPond-Report-17, read
-LilyPond Report 17} now!
+Come
+@uref{http://news.lilynet.net/The-LilyPond-Report-21, read
+LilyPond Report 21} now; comments and contributions are
+warmly encouraged!
@newsEnd
+
projects / lilypond.git / blobdiff