Shearwater is facing the consequences of an expanding product line. Their various computer models share a certain amount of common hardware and shared software code bases. As they add new features and segment other features to be only on model-A but not model-B the complexity and test matrix gets exponentially bigger.
It's not helpful in an engineering organization to punish people for bugs or mistakes. That just makes people hide and cover up the next mistake. Instead, you RCA the issue and adjust the process to catch the missed bugs and any others that might slip through the same cracks in the old process. Between automation, code review, unit testing, and user testing, these problems get screened out. But it's an iterative process that never ends. As long as the hardware, software and products are evolving new bugs will crop up. Most will be found early on, but it's inevitable that something sneaks out the door.