There are cases where a major change to a software project caused a handful of minor regressions but added new functionality, vastly improved performance in the

There are cases where a major change to a software project caused a handful of minor regressions but added new functionality, vastly improved performance in the majority of cases, etc. In these cases, a Zero Regressions policy is a bit silly. You can flip things around and look at the new code as baseline and from that perspective the old code has many more regressions relative to it. There seems to be a pretty stark divide between these mindsets.