X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;ds=sidebyside;f=Documentation%2Fweb%2Fnews-front.itexi;h=8d45279fb857c7aee23067d83d36de39f509ca76;hb=7e3df6b879dcd850a4e7645b1afc151111c77436;hp=3dce6210a3d01efd6872dfb54bb0ab9bbf71dfed;hpb=9def640bf6a0a5feb863c75c8a31e138fbe4043b;p=lilypond.git diff --git a/Documentation/web/news-front.itexi b/Documentation/web/news-front.itexi index 3dce6210a3..8d45279fb8 100644 --- a/Documentation/web/news-front.itexi +++ b/Documentation/web/news-front.itexi @@ -8,110 +8,132 @@ @c used for news about the upcoming release; see CG 10.2 - @newsItem -@subsubheading LilyPond 2.15.40 released! @emph{June 05, 2012} - -We are happy to announce the release of LilyPond 2.15.40. 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. +@subsubheading LilyPond 2.17.95 released! @emph{November 3, 2013} + +We are excited to announce the release of LilyPond@tie{}2.17.95 as +beta release for the upcoming stable release@tie{}2.18. The +developers are still busy finding solutions for some last-minute +problems, but the release is supposed to be feature-complete, the +documentation to be accurate, and no important issues to be +overlooked. For upgrading the syntax of your input files to the +latest version, see @rprogram{Updating files with convert-ly}. +Please test this release and report back any problems, see +@rweb{Bug reports}. @newsEnd - @newsItem -@subsubheading Release candidate withdrawn @emph{June 01, 2012} +@subsubheading LilyPond blog. @emph{June 2, 2013} -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}. +Janek Warchoł has created a LilyPond blog. You can find it at +@uref{http://lilypondblog.org/, lilypondblog.org}! @newsEnd - @newsItem -@subsubheading Release candidate 7 of 2.16 - LilyPond 2.15.39 released! @emph{May 22, 2012} +@subsubheading LilyPond 2.16.2 released! @emph{January 4, 2013} -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}. +We are happy to announce the release of LilyPond 2.16.2. This release is mainly +to correct a problem with lilypond-book running on Windows. We recommend that +only people requiring this functionality upgrade to this 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 05 June 2012. If you discover any problems, please send us -@ref{Bug reports}. +@newsEnd +@newsItem +@subsubheading The LilyPond Report #28. @emph{November 12, 2012} + +The @uref{http://news.lilynet.net/?The-LilyPond-Report-28, October +issue of the @emph{LilyPond Report}} focuses on the +@uref{http://news.lilynet.net/?LilyPond-meeting-in-Waltrop, +meeting of LilyPond developers and users} in Waltrop, Germany last +August. Of course, there are also some musings on LilyPond +triggered by the release of 2.16.0 and 2.17.0 occuring from that +venue. + +There are also two monthly financial reports from David Kastrup +whose work on LilyPond is +@uref{http://news.lilynet.net/?The-LilyPond-Report-24#an_urgent_request_for_funding, +solely paid for} by financial contributions from other developer +and users (thank you!), and a report about experiences from +@uref{http://scorio.com, a web-based music typesetting service} +using LilyPond internally. + +Come @uref{http://news.lilynet.net/?The-LilyPond-Report-28, read +LilyPond Report 28} now; comments and contributions are warmly +encouraged! @newsEnd +@newsItem +@subsubheading LilyPond 2.16.1 released! @emph{November 9, 2012} + +We are happy to announce the release of LilyPond 2.16.1. This has a number of +updates to the previous stable version, and should cause no problems. We +recommend that everybody upgrade to this version. +@newsEnd @newsItem -@subsubheading The LilyPond Report #26. @emph{May 22, 2012} +@subsubheading Lilypond 2.16.0 released! @emph{August 24, 2012} -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. +We are proud to announce the release of GNU LilyPond 2.16.1. +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. -Come -@uref{http://news.lilynet.net/?The-LilyPond-Report-26, read -LilyPond Report 26} now; comments and contributions are -warmly encouraged! +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 Release candidate 6 of 2.16 - LilyPond 2.15.38 released! @emph{May 3, 2012} +@example +@uref{http://lilypond.org/doc/v2.16/Documentation/changes/index.html} +@end example -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}. +Happy music typesetting! LilyPond 2.16 was brought to you by... -@strong{Update:} Due to a few Critical bugs, another release -candidate will be required. +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 LilyPond takes part in Google Summer of Code 2012! @emph{April 25, 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 -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. +Documentation contributors: -Our contributor Janek Warchoł was accepted for 2012 edition of GSoC. -He will be working on advanced lyrics positioning in LilyPond. +James Lowe, Pavel Roskin, Alberto Simoes, Stefan Weil -@newsEnd +Bug squad: +Colin Campbell, Eluze, Phil Holmes, Marek Klein, Ralph Palmer, +James Lowe -@newsItem -@subsubheading Release candidate 5 of 2.16 - LilyPond 2.15.37 released! @emph{April 19, 2012} +Support: + +Colin Campbell, Christian Hitz, Phil Holmes -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 -@ref{Development}. +Translation contributors: -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 03 May 2012. If you discover any problems, please send us -@ref{Bug reports}. +Jean-Charles Malahieude, Till Paala, Yoshiki Sawada @newsEnd + +