- 8,426
- Rockay City
I imagine that upper management is almost 100% to blame here. I've seen this happen so many times in the industry and it's always the same story; QA tell the devs and middle management there are issues > they report that to the upper management and execs > they see the potential to miss a big sales push > game gets released too early. It's a common issue that needs to change and I hope that this situation will make them rethink a little.
I once worked on a product team where we had to release something before end of quarter or we would get financial penalties/fines from the customer. Our product was crap/not ready at the time and we knew it. We also knew they would not test it anytime soon as it was holiday season. So we made sure the software booted (mind you: literally almost nothing worked beyond that) and released it on the 24th of December. When the customer started testing two months later we shipped them the most recent version which worked a lot better. The project was labeled a success, both by us and the customer.
Lesson here: the decisions to release something doesn't necessarily mean the product is ready to release. It sometimes just means that delaying further is even worse from a commercial perspective, so just eat the frog and release it, then fix until it works.