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. This is @strong{important
15 } to determine the cause of the problem.
17 (and you will do us a favor if send a @strong{small} sample file)
19 @item which LilyPond version you use. This is @strong{important information}
22 This information tells us if you've found a new bug, or an old one.
24 @item A description of the platform you use (i.e., operating system,
25 system libraries, whether you downloaded a binary release)
27 @item If necessary, send a description of the bug itself.
32 You can send the report to @email{bug-gnu-music@@gnu.org}---You don't
33 have to be subscribed to this mailinglist, or you can enter the bug in
35 @uref{http://appel.lilypond.org/wiki?LilyPondBugs}.