X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fweb%2Fnews-front.itexi;h=e37cf8c74bf9b7e398d2e160c355379586c455b4;hb=2b55f813985dd14f8e61011d1c76ecf00e45691e;hp=ed54e0c5d1faa8a660e59f1346ac36c7f245902b;hpb=bcc614a22846155a863b2d3a6cd5f3e7ff106fd5;p=lilypond.git diff --git a/Documentation/web/news-front.itexi b/Documentation/web/news-front.itexi index ed54e0c5d1..e37cf8c74b 100644 --- a/Documentation/web/news-front.itexi +++ b/Documentation/web/news-front.itexi @@ -8,69 +8,91 @@ @c used for news about the upcoming release; see CG 10.2 - @newsItem -@subsubheading LilyPond 2.15.34 released! @emph{Mar 19, 2012} +@subsubheading Lilypond 2.16.0 released! @emph{August 24, 2012} -We are happy to announce the release of LilyPond 2.15.34. This -release contains the usual number of bugfixes. +We are proud to announce the release of GNU LilyPond 2.16.0. +LilyPond is a music engraving program, devoted to producing the +highest-quality sheet music possible. It brings the aesthetics of +traditionally engraved music to computer printouts. -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. +Many improvements have been made in the past year since the previous +main stable version. A few major improvements are: -@newsEnd +@itemize +@item +Support for kievan square notation +@item +User and programming interfaces have greatly improved +@item +Music functions have become quite more versatile +@end itemize +A full list of new features is given in: -@newsItem -@subsubheading LilyPond 2.15.33 released! @emph{Mar 08, 2012} +@example +@uref{http://lilypond.org/doc/v2.16/Documentation/changes/index.html} +@end example -We are happy to announce the release of LilyPond 2.15.33. This -release contains the usual number of bugfixes. +Happy music typesetting! LilyPond 2.16 was brought to you by... -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. +Main development team: -@newsEnd +Bertrand Bordage, Trevor Daniels, Colin Hall, Phil Holmes, Ian Hulin, +Reinhold Kainhofer, David Kastrup, Jonathan Kulp, Werner Lemberg, +John Mandereau, Patrick McCarty, Joe Neeman, Han-Wen Nienhuys, +Jan Nieuwenhuizen, Graham Percival, Mark Polesky, Neil Puttock, +Mike Solomon, Carl Sorensen, Francisco Vila, Valentin Villenave, +Jan Warchoł +Programming contributors: -@newsItem -@subsubheading The LilyPond Report #24. @emph{Mar 5, 2012} +Aleksandr Andreev, Sven Axelsson, Peter Chubb, Karin Hoethker, +Marc Hohl, David Nalesnik, Justin Ohmie, Benkő Pál, Julien Rioux, Patrick Schmidt, +Adam Spiers, Heikki Taurainen, Piers Titus van der Torren, +Jan-Peter Voigt, Janek Warchol -A new issue of the @emph{LilyPond Report} is now -available for reading; topics include a request for funding, -an article about exciting new features in LilyPond grammar, -and an overview of LilyPond-based web applications. +Documentation contributors: -Come -@uref{http://news.lilynet.net/?The-LilyPond-Report-24, read -LilyPond Report 24} now; comments and contributions are -warmly encouraged! +James Lowe, Pavel Roskin, Alberto Simoes, Stefan Weil + +Bug squad: + +Colin Campbell, Eluze, Phil Holmes, Marek Klein, Ralph Palmer, +James Lowe + +Support: + +Colin Campbell, Christian Hitz, Phil Holmes + +Translation contributors: + +Jean-Charles Malahieude, Till Paala, Yoshiki Sawada @newsEnd @newsItem -@subsubheading LilyPond 2.15.32 released! @emph{Mar 03, 2012} +@subsubheading Lilypond 2.15.95 released! @emph{August 11, 2012} -We are happy to announce the release of LilyPond 2.15.32. This -release contains the usual number of bugfixes. +We are excited to announce the release of LilyPond 2.15.95. +With this release, development on version 2.15 is frozen for the +upcoming 2.16 stable release and only open to bug fixes. -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. +All users are urged to try this version to ensure the best +quality of the upcoming stable release. If you discover any +problems, please send us @ref{Bug reports}. + +New features since 2.14.2 are listed in the @qq{Changes} manual +on the website section about @ref{Development}. @newsEnd @newsItem -@subsubheading LilyPond 2.15.31 released! @emph{Feb 29, 2012} +@subsubheading LilyPond 2.15.42 released! @emph{August 02, 2012} -We are happy to announce the release of LilyPond 2.15.31. This +We are happy to announce the release of LilyPond 2.15.42. This release contains the usual number of bugfixes. It is strongly recommended that normal users do @strong{not} use @@ -82,17 +104,18 @@ candidate. @newsItem -@subsubheading Release candidate 3 of 2.16 - LilyPond 2.15.30 released! @emph{Feb 17, 2012} - -LilyPond 2.15.30 is out; this is the third 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 02 March 2012. If you discover any problems, please send us -@ref{Bug reports}. +@subsubheading The LilyPond Report #27. @emph{August 2, 2012} + +The @emph{LilyPond Report} is back, with some interesting insights on +new Scheme-related features recently added by our community’s only paid +developer David Kastrup (thanks to your +@uref{http://lilypond.org/sponsoring.html, continuing donations}). Also +to be found in this issue are an overview of some lesser-known LilyPond +companion projects, and a handful of more shallow factoids. + +Come +@uref{http://news.lilynet.net/?The-LilyPond-Report-27, read +LilyPond Report 27} now; comments and contributions are +warmly encouraged! @newsEnd