From: Graham Percival Date: Tue, 12 Apr 2011 06:08:09 +0000 (+0100) Subject: CG: clarify lack of policy for adding regtests. X-Git-Tag: release/2.13.60-1~9 X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=5ad4b3a291571e83bcf402656d346e46d8d9e667;p=lilypond.git CG: clarify lack of policy for adding regtests. --- diff --git a/Documentation/contributor/regressions.itexi b/Documentation/contributor/regressions.itexi index e2216f1a0b..3ec39d49cf 100644 --- 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