If you do not have one already, create a gmail account and send
the email address to the @ref{Meisters, Bug Meister}.
+@item
+Subscribe your gmail account to @code{bug-lilypond}.
+
@item
Configure your google code account:
@enumerate
@item
-Log in to:
+Sign in to google code by clicking in the top-right corner of:
@example
-@uref{http://code.google.com}
+@uref{http://code.google.com/p/lilypond/issues/list}
@end example
@item
Any email sent with your gmail address in the @code{To:} or
@code{CC:} fields should go to a @code{bug-answers} folder.
+When setting up your filtering rules, be aware that Google Code
+might use different versions of your email address, such as ones
+ending in @code{@@googlemail.com} or @code{@@gmail.com}.
+
@item
Any other email either from, or CC'd to,
@subsubheading Daily schedule
+The Bug Meister is omitted from the daily schedule.
+
@example
Sunday: Valentin
Monday: Dmytro
Tuesday: James Bailey
Wednesday: Ralph
-Thursday: Phil Holmes
-Friday: Urs Liska, Patrick
+Thursday: Patrick
+Friday: Urs
Saturday: Kieren
@end example
@item
If the email is a question about how to use LilyPond, reply with
-this reponse:
+this response:
@example
For questions about how to use LilyPond, please read our
or ask the lilypond-user mailing list.
@end example
+@item
+If the email mentions @qq{the latest git}, or any version number
+that has not yet been officially released, forward it to
+@code{lilypond-devel}.
+
@item
If a bug report is not in the form of a Tiny example, direct the
user to resubmit the report with this response:
@uref{http://lilypond.org/website/bug-reports.html}
@end example
-
@item
If anything is unclear, ask the user for more information.
system (if this is a suspected cause of the problem)? In short,
if you cannot understand what the problem is, ask the user to
explain more. It is the user's responsibility to explain the
-problem, not your reponsibility to understand it.
+problem, not your responsibility to understand it.
@item
If the behavior is expected, the user should be told to read the
@uref{http://code.google.com/p/lilypond/issues/list?can=7}
@end example
+A few (approximately 10%) of these fixed issues relate to the
+build system or fundamental architecture changes; there is no way
+for you to verify these. Leave those issues alone; somebody else
+will handle them.
+
@end itemize
@item
Checking all issues: we try to mark each Issue @q{fixed} when we
fix it, but occasionally one or two issues will slip through the
-cracks. It is therefore good to check all Issues. If you see the
+cracks. It is therefore good to check all Issues. If you see the
same (broken) output as the initial report, then simply post a
@qq{Problem still exists in 2.x.y} message to the issue.
issue should also have an estimated time in a comment.
@item
-Maintainability: hinders developent of LilyPond. For example,
+Maintainability: hinders development of LilyPond. For example,
improvements to the build system, or @qq{helper} python scripts.
@item
@ref{Issue classification}. In particular, the item should have
@code{Status}, @code{Type-}, and @code{Priority-} labels.
+Include output with the first applicable method:
+
+@itemize
+
+@item
+If the issue has a notation example which fits in one system,
+generate a small @file{bug@/.preview@/.png} file with:
+
+@example
+lilypond -dpreview bug.ly
+@end example
+
+@item
+If the issue has an example which requires more than one system
+(i.e. a spacing bug), generate a @file{bug@/.png} file with:
+
+@example
+lilypond --png bug.ly
+@end example
+
+@item
+If the issue requires multi-page output, then generate a
+@file{bug@/.pdf} file with the normal:
+
+@example
+lilypond --png bug.ly
+@end example
+
+@end itemize
+
@item
After adding the issue, please send a response email to the same
group(s) that the initial patch was sent to. If the initial email