Merge branch 'master' into lilypond/translation

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

diff --git a/Documentation/contributor/issues.itexi b/Documentation/contributor/issues.itexi
index 5ea4b952d349831514013941d66746f47e8455cd..041e1ece064ce7df5f3ed52b8c36b4e910d25ada 100644 (file)
--- a/Documentation/contributor/issues.itexi
+++ b/Documentation/contributor/issues.itexi
@@ -78,8 +78,8 @@ Sign in to google code by clicking in the top-right corner of:
 @uref{http://code.google.com/p/lilypond/issues/list}
 @end example
 
 @uref{http://code.google.com/p/lilypond/issues/list}
 @end example
 

-You cannot log if you have Google Sharing
-@uref{http://www.googlesharing.net/} enabled.
+You cannot log on if you have Google Sharing enabled
+@uref{http://www.googlesharing.net/}.

 
 @item
 Go to your @qq{Profile}, and select @qq{Settings}.
 
 @item
 Go to your @qq{Profile}, and select @qq{Settings}.


@@ -137,7 +137,7 @@ should go into a separate @code{bug-current} folder.
 @section Bug Squad checklists
 
 When you do Bug Squad work, start at the top of this page and work
 @section Bug Squad checklists
 
 When you do Bug Squad work, start at the top of this page and work

-your way down.  Stop when you've done 15 minutes.
+your way down.  Stop when you've done 20 minutes.

 
 Please use the email sorting described in @ref{Bug Squad setup}.
 This means that (as Bug Squad members) you will only ever respond
 
 Please use the email sorting described in @ref{Bug Squad setup}.
 This means that (as Bug Squad members) you will only ever respond


@@ -147,7 +147,7 @@ to emails sent or CC'd to the @code{bug-lilypond} mailing list.
 @subsubheading Emails to you personally
 
 You are not expected to work on Bug Squad matters outside of your
 @subsubheading Emails to you personally
 
 You are not expected to work on Bug Squad matters outside of your

-15 minutes, but sometimes a confused user will send a bug report
+20 minutes, but sometimes a confused user will send a bug report

 (or an update to a report) to you personally.  If that happens,
 please forward such emails to the @code{bug-lilypond} list so that
 the currently-active Bug Squad member(s) can handle the message.
 (or an update to a report) to you personally.  If that happens,
 please forward such emails to the @code{bug-lilypond} list so that
 the currently-active Bug Squad member(s) can handle the message.


@@ -155,16 +155,16 @@ the currently-active Bug Squad member(s) can handle the message.
 
 @subsubheading Daily schedule
 
 
 @subsubheading Daily schedule
 

-The Bug Meister is omitted from the daily schedule.
+@c spacing is deliberate to help reinforce the "cyclic" nature

 
 @example
 
 @example

-Sunday: Colin
-Monday: Dmytro
-Tuesday: James Bailey
-Wednesday: Ralph
-Thursday: Patrick
-Friday: Urs
-Saturday: Kieren
+Monday:    Dmytro
+Tuesday:    Colin
+Wednesday:   Brett
+Thursday:  Dmytro
+Friday:     Colin
+Saturday:    Brett
+Sunday:       Phil

 @end example
 
 
 @end example
 
 


@@ -315,7 +315,17 @@ After @strong{every release} (both stable and unstable):
 
 @item
 Regression test comparison: if anything has changed suspiciously,
 
 @item
 Regression test comparison: if anything has changed suspiciously,

-ask if it was deliberate.  The official comparison is online, at:
+ask if it was deliberate.  If the text output from LilyPond (the
+logfile) changes, the differences will be displayed with a +
+before text added to the logfile and - before any text removed
+from the logfile.  This may or may not be suspicious.
+
+There is one test designed to produce output every time the
+regtests are created. @code{test-output-distance.ly} creates
+randomly spaced notes and will always have different output if the
+regtest checker is working.
+
+The official comparison is online, at:

 
 @c NOTE: leave this here.  In this case, it's worth duplicating
 @c       the link.  -gp
 
 @c NOTE: leave this here.  In this case, it's worth duplicating
 @c       the link.  -gp


@@ -553,7 +563,7 @@ some cases, the developer's concerns can be resolved simply by
 discussion the situation or providing notation examples.
 
 If the patch is updated, the category should be changed to
 discussion the situation or providing notation examples.
 
 If the patch is updated, the category should be changed to

-@code{patch-new} (for normal contributors) or @code{patch-new}
+@code{patch-new} (for normal contributors) or @code{patch-review}

 (for developers who are very confident about their patch).
 
 @item
 (for developers who are very confident about their patch).
 
 @item


@@ -681,6 +691,15 @@ If the issue requires one or two pages of output, then generate a
 lilypond --png bug.ly
 @end example
 
 lilypond --png bug.ly
 @end example
 

+@item
+Images created as @file{bug.png} may be trimmed to a minimum size
+by using the @code{trimtagline.sh} script, which can be found at
+@uref{https://raw.github.com/gperciva/lilypond-extra/master/bug-squad/trimtagline.sh}
+
+@example
+trimtagline.sh bug.ly
+@end example
+

 @item
 If the issue cannot be shown with less than three pages, then
 generate a @file{bug.pdf} file with:
 @item
 If the issue cannot be shown with less than three pages, then
 generate a @file{bug.pdf} file with:


@@ -836,17 +855,17 @@ weeks.
 
 Grid view provides the best overview:
 
 
 Grid view provides the best overview:
 

-@example
+@smallexample

 @uref{http://code.google.com/p/lilypond/issues/list?mode=grid&y=Priority&x=Type&cells=ids}
 @uref{http://code.google.com/p/lilypond/issues/list?mode=grid&y=Priority&x=Type&cells=ids}

-@end example
+@end smallexample

 
 @subsubheading Hindering development
 
 These issues stop or slow development work:
 
 
 @subsubheading Hindering development
 
 These issues stop or slow development work:
 

-@example
-@uref{http://code.google.com/p/lilypond/issues/list?can=2&q=label:Maintainability&mode=grid&y=Priority&x=Type&cells=ids}
-@end example
+@smallexample
+@uref{http://code.google.com/p/lilypond/issues/list?can=2&q=label:Maintainability}
+@end smallexample

 
 @subsubheading Easy tasks
 
 
 @subsubheading Easy tasks
 


@@ -856,9 +875,9 @@ relatively new contributor.  The time given is a quick
 familiar with material in this manual, but does not know anything
 else about LilyPond development.
 
 familiar with material in this manual, but does not know anything
 else about LilyPond development.
 

-@example
-@uref{http://code.google.com/p/lilypond/issues/list?can=2&q=label:Frog&mode=grid&y=Priority&x=Type&cells=ids}
-@end example
+@smallexample
+@uref{http://code.google.com/p/lilypond/issues/list?can=2&q=label:Frog}
+@end smallexample

 
 @subsubheading Patches to review
 
 
 @subsubheading Patches to review