Doc: CG: updates to Bug Squad.

diff --git a/Documentation/contributor/administration.itexi b/Documentation/contributor/administration.itexi
index 54bd3c2cfeed6cf8c81c6754427a8be0d3222071..ecdb3469dd8db4bb4bb609274daa78a43edb4c11 100644 (file)
--- a/Documentation/contributor/administration.itexi
+++ b/Documentation/contributor/administration.itexi
@@ -87,7 +87,7 @@ Bug Meister: trains new Bug Squad volunteers, organizes who works
 on which part of their job, checks to make sure that everything is
 running smoothly, and has final say on our policy for Issues.
 
-Currently: Graham
+Currently: Phil
 
 @item
 Doc Meister: trains new doc editors/writers, organizes who works

diff --git a/Documentation/contributor/issues.itexi b/Documentation/contributor/issues.itexi
index a93b767b09421b089dae332223e334db6f8f7896..df1a6cb2bc371548fd99347b231be35178850004 100644 (file)
--- a/Documentation/contributor/issues.itexi
+++ b/Documentation/contributor/issues.itexi
@@ -147,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
 

diff --git a/Documentation/contributor/regressions.itexi b/Documentation/contributor/regressions.itexi
index f421a007d92ef2f79e4917968f8fcb8ba2824571..70fbcf18a2f4e7e2e9c97126be8f33f6933d028a 100644 (file)
--- a/Documentation/contributor/regressions.itexi
+++ b/Documentation/contributor/regressions.itexi
@@ -80,28 +80,46 @@ comparisons is archived online:
 @uref{http://lilypond.org/test/}
 @end example
 
-The test comparison shows all of the changes that occurred between
-the current release and the prior release.  Each test that has
-a significant difference in output is displayed, with the old
-version on the left and the new version on the right.  Blurs
-in the regression tests for the new version show the approximate
-location of elements in the old version.
-
-Regression tests whose output is the same for both versions are not
-shown in the test comparison.
-
 Checking these pages is a very important task for the LilyPond project.
 You are invited to report anything that looks broken, or any case
 where the output quality is not on par with the previous release,
 as described in @rweb{Bug reports}.
 
+@subheading What to look for
+
+The test comparison shows all of the changes that occurred between
+the current release and the prior release.  Each test that has a
+significant difference in output is displayed, with the old
+version on the left and the new version on the right.
+
+Regression tests whose output is the same for both versions are
+not shown in the test comparison.
+
+@itemize
+@item
+Images: green blurs in the new version show the approximate
+location of elements in the old version.
+
+There are often minor adjustments in spacing which do not indicate
+any problem.
+
+@item
+Log files: show the difference in command-line output.
+
+The main thing to examine are any changes in page counts -- if a
+file used to fit on 1 page but now requires 4 or 5 pages,
+something is suspicious!
+
+@item
+Profile files: give information about
+TODO?  I don't know what they're for.
+
+@end itemize
+
 @warning{
-The automatic comparison of the regtests checks the
-LilyPond bounding boxes and the log files.  This means that
-Ghostscript changes and changes in
-lyrics or text are not found.  However, errors and warnings that
-are printed to the log file but
-do not change the graphical layout are also identified.
+The automatic comparison of the regtests checks the LilyPond
+bounding boxes.  This means that Ghostscript changes and changes
+in lyrics or text are not found.
 }
 
 @node Compiling regression tests