X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fweb%2Fnews-front.itexi;h=2cc23dce1a5238d0added11e196ae527c7ec2572;hb=66b2a060d7402e0d9d42586207b71ca3eda752f1;hp=021a1f7f5db86b5affc855e2dd54dfa8c4f97a3b;hpb=84e144718964f20c48ff8dccaea8de9741df07e4;p=lilypond.git diff --git a/Documentation/web/news-front.itexi b/Documentation/web/news-front.itexi index 021a1f7f5d..f380a23b65 100644 --- a/Documentation/web/news-front.itexi +++ b/Documentation/web/news-front.itexi @@ -2,31 +2,63 @@ @c This file is part of lilypond-web.texi and community.itexi @c when you add a new item, consider moving the lowest item(s) -@c into news-old.itexi. +@c into news.itexi. @c keep two blank lines between news entries @c used for news about the upcoming release; see CG 10.2 @newsItem -@subsubheading LilyPond 2.15.9 released! @emph{August 11, 2011} +@subsubheading Release candidate 7 of 2.16 - LilyPond 2.15.39 released! @emph{May 22, 2012} -We are happy to announce the release of LilyPond 2.15.9. This -release contains the usual number of bugfixes, and also adds -support for MacOS X 10.7. +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}. -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 outstanding Critical bugs, this is not the -next release candidate. +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 Release candidate 1 of 2.16 - LilyPond 2.15.8 released! @emph{Aug 01, 2011} +@subsubheading Release candidate 6 of 2.16 - LilyPond 2.15.38 released! @emph{May 3, 2012} -LilyPond 2.15.8 is out; this is the first 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 @@ -34,44 +66,69 @@ 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 08 Aug 2011. If you discover any problems, please send us +on 03 May 2012. If you discover any problems, please send us @ref{Bug reports}. @newsEnd @newsItem -@subsubheading LilyPond 2.15.7 released! @emph{July 29, 2011} +@subsubheading Release candidate 4 of 2.16 - LilyPond 2.15.36 released! @emph{April 6, 2012} -We are happy to announce the release of LilyPond 2.15.7. This -release contains the usual number of bugfixes. +LilyPond 2.15.36 is out; this is the fourth 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}. -It is strongly recommended that normal users do @strong{not} use -this release, and instead use the stable 2.14 version. +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 20 April 2012. If you discover any problems, please send us +@ref{Bug reports}. @newsEnd @newsItem -@subsubheading LilyPond 2.15.6 released! @emph{July 26, 2011} +@subsubheading The LilyPond Report #25. @emph{Apr 1st, 2012} -We are happy to announce the release of LilyPond 2.15.6. This -release contains the usual number of bugfixes. +The @emph{LilyPond Report} is back, with a rather unusual +issue featuring our young Polish contributor Janek Warchoł! +Also included in this issue are quite a few unexpected items, +including (but not limited to)… a cooking recipe! -It is strongly recommended that normal users do @strong{not} use -this release, and instead use the stable 2.14 version. +Come +@uref{http://news.lilynet.net/?The-LilyPond-Report-25, read +LilyPond Report 25} now; comments and contributions are +warmly encouraged! @newsEnd @newsItem -@subsubheading LilyPond 2.14.2 released! @emph{July 25, 2011} +@subsubheading LilyPond 2.15.35 released! @emph{Mar 28, 2012} -We are happy to announce the release of LilyPond 2.14.2. This -fixes a few minor bugs in the stable version, and should cause no -problems. We recommend that everybody upgrade to this version. +We are happy to announce the release of LilyPond 2.15.35. This +release contains the usual number of bugfixes. + +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 LilyPond 2.15.34 released! @emph{Mar 19, 2012} + +We are happy to announce the release of LilyPond 2.15.34. This +release contains the usual number of bugfixes. + +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