The easiest way to keep touch is by reading our community newsletter, the LilyPond Report:
This mailing list is a low-volume, read-only list which receives notifications of new releases.
If you have input that results in a crash or wrong output, then that is a bug.
第 1 步：检查是否已知错误
We may already know about this bug. Check here:
注意：Please DO NOT add bug reports directly to the bug tracker. Once an issue has been added to the tracker, feel free to add more information to that report.
We need you!
Thank you for your interest in helping us — we would love to see you get involved! Your contribution will help a large group of users make beautifully typeset music.
Even working on small tasks can have a big impact: taking care of them allows experienced developers work on advanced tasks, instead of spending time on those simple tasks.
For a multi-faceted project like LilyPond, sometimes it’s tough to know where to begin. In addition to the avenues proposed below, you can send an e-mail to the email@example.com mailing list, and we’ll help you to get started.
No programming skills required!
Mailing list support: answer questions from fellow users.
(This may entail helping them navigate the online documentation;
in such cases it may sometimes be appropriate to point them
to version-agnostic URL paths such as
/stable/, which are automatically redirected.)
- Bug reporting: help users create proper Bug reports, and/or join the Bug Squad to organize Issues.
- Documentation: small changes can be proposed by following the guidelines for Documentation suggestions.
- LilyPond Snippet Repository (LSR): create and fix snippets following the guidelines in Adding and editing snippets.
- Discussions, reviews, and testing: the developers often ask for feedback about new documentation, potential syntax changes, and testing new features. Please contribute to these discussions!
These jobs generally require that you have the source code and can compile LilyPond.
注意：We suggest that contributors using Windows or MacOS X do not attempt to set up their own development environment; instead, use Lilydev as discussed in Quick start.
Begin by reading Summary for experienced developers.
- Documentation: for large changes, see Documentation work.
- Website: the website is built from the normal documentation source. See the info about documentation, and also Website work.
- Translations: see Translating the documentation, and Translating the website.
- Bugfixes or new features: read Programming work.
In the past,
- some users have paid for new features
- some developers have added new features for hire
The LilyPond project does not organize such efforts; we neither endorse nor discourage such agreements. Any contracts between private individuals is the business of those individuals, not ours.
Any user wanting to offer money in exchange for work should bear in mind the following points:
- LilyPond developers may advertise their services on the lilypond email lists from time to time.
- Any agreements between private individuals should include the normal precautions when conducting business: who pays, how much do they pay, with what method of payment, and upon what set of conditions. We suggest that any ambiguity or uncertainty in these questions should be resolved before any work begins.
Development for LilyPond 2.21.2
Release numbers 发行号
There are two sets of releases for LilyPond: stable releases, and unstable development releases. Stable versions have an even-numbered ‘minor’ version number (e.g., 2.8, 2.10, 2.12). Development versions have an odd-numbered ‘minor’ version number (e.g., 2.7, 2.9, 2.11).
Instructions for git and compiling are in the Contributor’s Guide.
Documentation writers and testers will generally want to download the latest binary:
LilyPond development is a fairly complicated matter. In order to help new contributors, and to keep the whole system (mostly) stable, we have written a manual for development tasks.
- Regression tests for 2.21.2 (PDF of regtests for 2.21.2)
- MusicXML Regression tests for 2.21.2 (PDF of MusicXML regtests for 2.21.2)
- abc2ly Regression tests for 2.21.2 (PDF of abc2ly regtests for 2.21.2)
- lilypond-book Regression tests for 2.21.2 (PDF of lilypond-book regtests for 2.21.2)
- Regression tests for 2.20.0 (PDF of regtests for 2.20.0)
- MusicXML Regression tests for 2.20.0 (PDF of MusicXML regtests for 2.20.0)
- abc2ly Regression tests for 2.20.0 (PDF of abc2ly regtests for 2.20.0)
- lilypond-book Regression tests for 2.20.0 (PDF of lilypond-book regtests for 2.20.0)
What is Google Summer of Code?
It is a global program run by Google that offers students stipends for working on open source software projects during summer vacations.
The LilyPond Team decided that this is an excellent opportunity to find new contributors and encourage students already participating in LilyPond development to become more involved. One of our contributors was accepted for 2012 edition of the program as part of the GNU project; we hope to participate in future editions as well.
- Trevor Daniels: firstname.lastname@example.org, Assistant documentation editor
- Colin Hall: Bug meister
- Phil Holmes: email@example.com http://www.philholmes.net Build unentangler, Bug squad member
- David Kastrup: firstname.lastname@example.org, hard core developer, user and programming interfaces, bug squashing and swamp drainage.
- Werner Lemberg, email@example.com, Fonts, bug squasher
- Han-Wen Nienhuys: firstname.lastname@example.org, http://www.xs4all.nl/~hanwen/, Main author
- Jan Nieuwenhuizen: email@example.com, http://JoyofSource.com, http://AvatarAcademy.nl, Main author
- Mark Polesky: Documentation, Code cleanup
- Carl Sorensen: firstname.lastname@example.org, Core developer
- Francisco Vila: Translation Meister
- Valentin Villenave: Core developer
- Janek Warchoł: email@example.com, Core developer
- Mats Bengtsson: firstname.lastname@example.org, https://www.kth.se/profile/matben/, Support guru
- Bertrand Bordage: email@example.com, Core developer, font designer
- Ian Hulin: Core developer
- Reinhold Kainhofer: firstname.lastname@example.org, http://reinhold.kainhofer.com, Core developer, Music2xml wrangler
- Pedro Kroeger: Build meister
- Jonathan Kulp: Assistant documentation editor
- Joe Neeman: Core developer
- John Mandereau: email@example.com, Translation meister
- Patrick McCarty: SVG guru, bug squad member, bug squasher, text handling
- Graham Percival: http://percival-music.ca, Bug meister, Grand Documentation Project leader
- Neil Puttock: Core developer
- Jürgen Reuter: firstname.lastname@example.org, http://www.juergen-reuter.de, Ancient notation
- Mike Solomon: email@example.com, Core developer, Frog meister
- Erik Sandberg: Bug meister
- Nicolas Sceaux: Core developer, Schemer extraordinaire
Guido Aulisi, Joe Austin, Federico Bruni, Nathan Chou, Dan Eble, John Gourlay, Marc Hohl, Masamichi Hosoda, Mark Knoop, Tobias Kretschmar, Vincent Le Ligeour, James Lowe, Thomas Morley, Paul Morris, David Nalesnik, Keith OHara, Benkő Pál, Knut Petersen, Julien Rioux, Ben Rudiak-Gould, Devon Schudy, Heikki Tauriainen
Jay Anderson, Masamichi Hosoda, Abraham Lee
Simon Albrecht, Frédéric Bron, Federico Bruni, Colin Campbell, Urs Liska, James Lowe, Thomas Morley, Jean-Charles Malahieude, Patrick Schmidt, Pierre Perol-Schneider, Greg Swinford, Martin Tarenskeen
错误组 (Bug squad)
Simon Albrecht, Federico Bruni, Colin Campbell, Phil Holmes, Ralph Palmer
Simon Albrecht, Colin Campbell, Eluze, Marc Hohl, Phil Holmes, Marek Klein, Alex Loomis, Kieren MacMillan, Thomas Morley, Tim McNamara, Paul Morris, David Nalesnik, Urs Liska, Ralph Palmer, Pierre Perol-Schneider, Neil Puttock, Tao
Federico Bruni, Luca Rossetto Casel, Felipe Castro, Pavel Fric, Walter Garcia-Fontes, Tommaso Gordini, Erika Griechisch, Denes Harmath, Masamichi Hosoda, Jean-Charles Malahieude, Till Paala, Yoshiki Sawada, Tomohiro Tatejima, Paco Tomillo
我们写的有关 LilyPond 的文章
- Server Acim. GNU/LilyPond (Turkish Language). 2013. (PDF 2100k).
- Graham Percival. Sustainability in F/OSS: developers as a non-renewable resource. In Rencontres Mondiales du Logiciel Libre 2010 (RMLL2010), 2010. (PDF 333k).
- Han Wen Nienhuys and Jan Nieuwenhuizen. LilyPond, a system for automated music engraving. In Colloquium on Musical Informatics (XIV CIM 2003), May 2003. (PDF 95k).
- Han Wen Nienhuys. LilyPond, Automated music formatting and the Art of Shipping. In Forum Internacional Software Livre 2006 (FISL7.0), 2006. (PDF 1095k).
- Margarethe Maierhofer Lischka & Florian Hollerweger. Lilypond: music notation for everyone!. In Linux Audio Conference 2013 (LAC2013), 2013. (PDF 890k).
- Reinhold Kainhofer. OrchestralLily: A Package for Professional Music Publishing with LilyPond and LATEX. In The Linux Audio Conference 2010 (LAC2010), 2010. (PDF 767k).
- Erik Sandberg. Separating input language and formatter in GNU LilyPond. Master’s thesis, Uppsala University, Department of Information Technology, March 2006. (PDF 750k).
注意：Many old announcements and changelogs can be found in the Attic
New Italian mailing list
June 22, 2020 - All Italian users are welcome to join the new Italian mailing list, where they can get help and discuss about LilyPond in their mother language.
LilyPond 2.21.2 released June 21, 2020
We are happy to announce the release of LilyPond 2.21.2. This is a development version, but these are usually reliable. If you want to use the latest stable version of LilyPond, we recommend using the 2.20.0 version.
LilyPond 2.20.0 released! March 1, 2020
We are proud to announce the release of GNU LilyPond 2.20.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.
This version provides a number of updates, including updated manuals. We recommend all users to upgrade to this version.