CG: clarify lack of policy for adding regtests.

diff --git a/Documentation/contributor/regressions.itexi b/Documentation/contributor/regressions.itexi
index e2216f1a0bbc9c0052f30d80726882c9a4d91006..3ec39d49cf201b83e7beaaa516a7e4bff66bf28d 100644 (file)
--- a/Documentation/contributor/regressions.itexi
+++ b/Documentation/contributor/regressions.itexi
@@ -22,9 +22,11 @@ These regression tests comprise small LilyPond snippets that test
 the functionality of each part of LilyPond.
 
 Regression tests are added when new functionality is added to
-LilyPond.  They are also added when bugs are identified.  The
-snippet that causes the bug becomes a regression test to verify
-that the bug has been fixed.
+LilyPond.
+We do not yet have a policy on when it is appropriate to add or
+modify a regtest when bugs are fixed.  Individual developers
+should use their best judgement until this is clarified during the
+@ref{Grand Organization Project (GOP)}.
 
 The regression tests are compiled using special @code{make}
 targets.  There are three primary uses for the regression