@newsItem
-@subsubheading LilyPond 2.15.32 released! @emph{Mar 03, 2012}
+@subsubheading Release candidate withdrawn @emph{Jan 13, 2011}
-We are happy to announce the release of LilyPond 2.15.32. This
-release contains the usual number of bugfixes.
+We have discovered a regression since 2.14.2, so lilypond 2.15.39
+is no longer a candidate for the 2.16.0 release. However, please
+continue testing it -- we would like to discover (and fix!) any
+more regressions as soon as possible. If you discover any
+problems, please send us @ref{Bug reports}.
-It is strongly recommended that normal users do @strong{not} use
-this release, and instead use the stable 2.14 version. Please
-note that due to a few Critical bugs, this is not the next release
-candidate.
+@newsEnd
+
+
+@newsItem
+@subsubheading Release candidate 7 of 2.16 - LilyPond 2.15.39 released! @emph{May 22, 2012}
+
+LilyPond 2.15.39 is out; this is the seventh release candidate of
+the upcoming 2.16 stable release. All users are invited to
+experiment with this version. New features since 2.14.2 are
+listed in the @qq{Changes} manual on the website section about
+@ref{Development}.
+
+There are no known Critical issues with this release. If no
+Critical bugs are found, then the official 2.16.0 release will be
+on 05 June 2012. If you discover any problems, please send us
+@ref{Bug reports}.
@newsEnd
@newsItem
-@subsubheading LilyPond 2.15.31 released! @emph{Feb 29, 2012}
+@subsubheading The LilyPond Report #26. @emph{May 22, 2012}
-We are happy to announce the release of LilyPond 2.15.31. This
-release contains the usual number of bugfixes.
+The @emph{LilyPond Report} is back, with a new editor on board -
+Pavel Roskin, who tells us about his adventures in strange lands
+of compiler bugs! There is also a detailed report about current
+development status, and an analysis of example LilyPond output -
+see for yourself how close (or how far?) are we from matching
+the quality of hand-engraved scores.
-It is strongly recommended that normal users do @strong{not} use
-this release, and instead use the stable 2.14 version. Please
-note that due to a few Critical bugs, this is not the next release
-candidate.
+Come
+@uref{http://news.lilynet.net/?The-LilyPond-Report-26, read
+LilyPond Report 26} now; comments and contributions are
+warmly encouraged!
@newsEnd
@newsItem
-@subsubheading Release candidate 3 of 2.16 - LilyPond 2.15.30 released! @emph{Feb 17, 2012}
+@subsubheading Release candidate 6 of 2.16 - LilyPond 2.15.38 released! @emph{May 3, 2012}
-LilyPond 2.15.30 is out; this is the third release candidate of
+LilyPond 2.15.38 is out; this is the sixth release candidate of
+the upcoming 2.16 stable release. All users are invited to
+experiment with this version. New features since 2.14.2 are
+listed in the @qq{Changes} manual on the website section about
+@ref{Development}.
+
+@strong{Update:} Due to a few Critical bugs, another release
+candidate will be required.
+
+@newsEnd
+
+
+@newsItem
+@subsubheading LilyPond takes part in Google Summer of Code 2012! @emph{April 25, 2012}
+
+Being a part of @uref{http://www.gnu.org/, GNU project}, we are participating in
+@uref{http://www.google-melange.com/gsoc/homepage/google/gsoc2012,
+Google Summer of Code program}, which offers students stipends for
+working on open source software.
+
+Our contributor Janek WarchoĊ was accepted for 2012 edition of GSoC.
+He will be working on advanced lyrics positioning in LilyPond.
+
+@newsEnd
+
+
+@newsItem
+@subsubheading Release candidate 5 of 2.16 - LilyPond 2.15.37 released! @emph{April 19, 2012}
+
+LilyPond 2.15.37 is out; this is the fifth release candidate of
the upcoming 2.16 stable release. All users are invited to
experiment with this version. New features since 2.14.2 are
listed in the @qq{Changes} manual on the website section about
There are no known Critical issues with this release. If no
Critical bugs are found, then the official 2.16.0 release will be
-on 02 March 2012. If you discover any problems, please send us
+on 03 May 2012. If you discover any problems, please send us
@ref{Bug reports}.
@newsEnd
-
-
projects / lilypond.git / blobdiff