7 LilyPond development moves quickly, so if you have a problem, it is
8 wise to check if it has been fixed in a newer release. If you think
9 you found a bug, please send in a bugreport including the following
14 @item a sample input which causes the error. Without this, we can not
17 (and you will do us a favor if send a @strong{small} sample file)
19 @item which LilyPond version you use. Without this, we can not verify
22 @item A description of the platform you use (i.e., operating system,
23 system libraries, whether you downloaded a binary release)
25 @item If necessary, send a description of the bug itself.
30 You can send the report to @email{bug-gnu-music@@gnu.org}. This is a
31 mailinglist, but you don't have to be subscribed to it. You may also
32 enter the bug in the LilyPond wiki, at
33 @uref{http://appel.lilypond.org/wiki?LilyPondBugs}.