Doc: cleanup @file{}, take 2: remove all @/ escaping sequences.

[lilypond.git] / Documentation / contributor / issues.itexi

diff --git a/Documentation/contributor/issues.itexi b/Documentation/contributor/issues.itexi
index 72509d080f72c0172afe2166e7cce1b150f6c3b4..2d496e830e79f9ba489902a06199232c0880685c 100644 (file)
--- a/Documentation/contributor/issues.itexi
+++ b/Documentation/contributor/issues.itexi
@@ -58,16 +58,19 @@ from @ref{Bug Squad checklists}.
 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
@@ -88,6 +91,10 @@ Configure your email client:
 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,
 
@@ -140,13 +147,15 @@ the currently-active Bug Squad member(s) can handle the message.
 
 @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
 
@@ -186,7 +195,7 @@ check to see who else has replied to it), delete it.
 
 @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
@@ -195,6 +204,11 @@ documentation available from:
 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:
@@ -206,7 +220,6 @@ step 2 in our bug reporting guidelines:
   @uref{http://lilypond.org/website/bug-reports.html}
 @end example
 
-
 @item
 If anything is unclear, ask the user for more information.
 
@@ -215,7 +228,7 @@ What version of lilypond was used (if not given) and operating
 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
@@ -315,6 +328,11 @@ version; if you cannot reproduce the bug, mark the item
 @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
 
 
@@ -364,7 +382,7 @@ information is available from in @ref{Regression tests}.
 @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.
 
@@ -534,7 +552,7 @@ Frog: the fix is believed to be suitable for a new contributor
 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
@@ -586,6 +604,36 @@ Add the issue and classify it according to the guidelines in
 @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