Quoting bulia byak <buliabyak@...400...>:
Third, strive to fix ASAP any bugs or regressions found in the code you checked in. If you know the code you're about to check in has some unfixable (in the short term, or even at all) regressions, please warn people on the list and try to find a consensus.
One thing in particular that I'd like to underscore for the benefit of the list: breakage is, fundamentally, a debt.
The longer code remains broken or disabled, the more difficult it becomes to fix or re-integrate later. This difficulty increases super-linearly with time.
In other words, he longer you remain in debt, the more interest you have to pay.
This is why small, incremental changes are best. It's also why I'm so aggressive about ripping out unused or commented-out code.
-mental