Update CG with website build and bug squad

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

diff --git a/Documentation/contributor/issues.itexi b/Documentation/contributor/issues.itexi
index c51b3f07e979d243e445ba330699176ac6200234..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
 
-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}.
@@ -155,14 +155,16 @@ the currently-active Bug Squad member(s) can handle the message.
 
 @subsubheading Daily schedule
 
+@c spacing is deliberate to help reinforce the "cyclic" nature
+
 @example
 Monday:    Dmytro
-Tuesday:   Colin
-Wednesday: Derek
+Tuesday:    Colin
+Wednesday:   Brett
 Thursday:  Dmytro
-Friday:    Colin
-Saturday:  Dmytro
-Sunday:    Phil
+Friday:     Colin
+Saturday:    Brett
+Sunday:       Phil
 @end example
 
 
@@ -313,7 +315,17 @@ After @strong{every release} (both stable and unstable):
 
 @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
@@ -679,6 +691,15 @@ If the issue requires one or two pages of output, then generate a
 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: