On 8/3/07, Peter Dimov <pdimov@pdimov.com> wrote:
Martin Wille wrote:
Peter Dimov wrote:
Another interesting example is adding a new test that exposes an existing bug. This test has never passed, but its inclusion is prevented by the stability requirement.
No, in this scenario, the bug has been there before. There's no break of stability if the bug gets indicated by the testing harness from some point in time on.
There is no break in stability, but there is a violation of the stability requirements, which demand that there should be no test failures on the stable branch. This prevents the merge of the new test unless the same merge also contains a fix.
Or you check in the test, and roll back 'stable' until the test passes! Or make it something of a 'all hands on deck' situation - lock SVN until there is a fix or something like that (maybe not quite so drastic...) Tony