Guenter Milde wrote: > In normal inter-release development times, I think it is too restricting > to insist on tested regression-free patches.
I can only recommend to try to always work like that. I know it does not sound convincing (you really have to try it out), but I made the experience that I get stuff done quicker if I take the tests into account as soon as I think imy change might work (which it usually does not do, and the tests do usually show where it is broken). > IMO, a sane state of the test suite can also be maintained without > stifling work on the code if the test suite is cleaned up in a couple of > days whenever new test failures are noticed. True, but in total it will be even less work if coce and test changes are submitted in one go. Georg
