There's an analogy that we like to use at work, and in my experience it holds pretty well for code quality and bleeds
pretty well into the entire development process:

http://en.wikipedia.org/wiki/Broken_windows_theory

We do an ok job when it comes to the tests (though certainly not perfect). We've been getting a lot better at
addressing regressions, though there's still 4 open right now (1 phobos, 2 druntime, 1 dmd). Can we please make the
remaining open regressions a release blocker?