I know from experience that all the testing in the world in a closed test environment doesn't begin to cover the things users do once a program gets out in the wild. We release a major version of our software about yearly. We have a couple of QA people who have multiple automated test systems on various operating systems and machine configurations. Our Support group tests it in advance of release to make sure we don't find anything and are aware of new functionality. We generally feel really solid on our releases. Sure enough, as soon as we let it out the door, a customer finds a show stopping, billing level issue that brings the world to a halt.
I'm not saying that reported bugs haven't gone unfixed and get released anyway. But I am saying that with any software that is beyond version 1, two things tend to happen. #1 You fix one thing that impacts and breaks four more. #2 The minute you let a customer touch it you are going to stand back and go "huh, they pushed what button how? why on earth would they do that?"
And just to let you know, I've worked in my current company for 16 years and done software support for 23 years. It's happened with every single software release I've ever been part of. There's a reason Microsoft puts out updates. LOL No matter how much testing is done, internally, on TC and on Origin, until this gets onto a bigger shard or more people pound away, bugs are gonna get released. Just the nature of software.
The really important thing is how quickly the showstoppers get fixed. Not that they got released.