@c keep two blank lines between news entries
-@c FIXME: fill in number
-@c used for news about the upcoming release; see CG x.y
+@c used for news about the upcoming release; see CG 10.2
+
@newsItem
-@subsubheading LilyPond 2.13.22 released! @emph{May 27, 2010}
+@subsubheading LilyPond 2.13.42 released! @emph{Dec 8, 2010}
-We are happy to announce the release of LilyPond 2.13.22. This
+We are happy to announce the release of LilyPond 2.13.42. 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 second beta test. Due
+to a number of untested changes to our build process, we cannot be
+at all confident about the quality of this release.
+
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond 2.13.41 released! @emph{Dec 4, 2010}
+
+We are happy to announce the release of LilyPond 2.13.41. 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 second beta test. Due
+to a number of untested changes to our build process, we cannot be
+at all confident about the quality of this release.
+
@newsEnd
+
@newsItem
-@subsubheading LilyPond 2.13.21 released! @emph{May 12, 2010}
+@subsubheading LilyPond 2.13.40 released! @emph{Nov 21, 2010}
-We are happy to announce the release of LilyPond 2.13.21. This
+We are happy to announce the release of LilyPond 2.13.40. This
release contains the usual number of bugfixes. However, a number
of critical issues still remain, so this release is intended for
developers only.
-This release should be of particular interest to package
-maintainers: we have made a few changes to the configure script
-and the required libraries. Barring any urgent bug reports, this
-is the build system and libraries that will be used for the next
-stable release.
+Please note that this is @strong{not} the second beta test. Due
+to a number of untested changes to our build process, we cannot be
+at all confident about the quality of this release.
+
@newsEnd
@newsItem
-@subsubheading LilyPond Report #18. @emph{May 11, 2010}
+@subsubheading Beta test one of 2.14 -- LilyPond 2.13.39 released! @emph{Nov 15, 2010}
+
+LilyPond 2.13.39 is out; this is the first beta 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.39, do not
+be surprised to discover problems; just send us polite
+@ref{Bug reports}.
+
+@newsEnd
+
-The @emph{LilyPond Report} is back, with its two
-@qq{grumpy-and-fluffy} editors! This issue will be filled
-with emotion and coolness, paper bags and zigzag-ending
-staves, plus the usual Frogs and Bugs.
+
+
+@newsItem
+@subsubheading The LilyPond Report #22. @emph{Nov 3, 2010}
+
+The @emph{LilyPond Report} is back, with some surprises and exciting
+news for the whole LilyPond community! To be found in this issue is
+an up-to-date, complete list of all LilyPond mailing lists and forums
+around the world. Also, for the very first time our special guest
+today is LilyPond’s co-founder and core developer
+@strong{Jan Nieuwenhuizen}, who has been busy these past months --
+read on to find out what for!
Come
-@uref{http://news.lilynet.net/The-LilyPond-Report-18, read
-LilyPond Report 18} now; comments and contributions are
+@uref{http://news.lilynet.net/The-LilyPond-Report-22, read
+LilyPond Report 22} now; comments and contributions are
warmly encouraged!
+
@newsEnd
+
projects / lilypond.git / blobdiff