Does anything about this release strike you as properly tested? By definition a release in this state was not tested in any meaningful sense of the word.
There's a difference between "tested" and "fixed". Which is what I was saying, the testing would have happened but that doesn't mean that enough time was allocated in the timeline to allow for those issues that were picked up to be fixed before launch. It is, sadly, something that happens quite often in the industry. There will be a set number of sprints assigned to design, development, implementation. Ideally, after that point, you'd have a testing period of the RC, smoke tests, automation, etc. with another (depends on the game) sprint to apply those fixes for launch.
That last part is most likely what was lacking. It's often what is lacking from a project/patch timeline. I doubt FD has changed much in the past ~1.5 years, but there was always a woeful lack chances for QA to say "this isn't ready, it must be delayed." The release date was already set with minimal time for issues picked up in QA to be implemented to game.
Oh well, such is life and it'll be fixed eventually. Just irks me that the first scapegoat is
always QA, where many of my friends within FD and the industry at large is busting their hides, and the real culprit is time & project management.