I wonder what is wrong with giving out a "firm date". That demonstrates good management and things going well at the business, instead of "done when its done".
I realize that release dates usually are not given past the original release of a game but where I work, yes, in software, as a programmer, we do have release dates, and not just oh well, when it is ready.
Dates can be missed but it is frowned upon and the reasons why generally need to be explained...internally...that is generally true...but surely to clients by a more official spokesperson. Missed target dates and QA bugs mean rework in DEV and QA and you are not spending time on your NEXT project which affects your business plan.
Alternatively, secondary resources, if available, are assigned to this 'thorn-in-the-side" while the "A" team is busy with a new product and so things here can 'slide' as they have.
QA is not the only department that finds bugs. Developers often find their own; as a footnote. They hit a 'regression' variance; broke something while fixing something. Not unheard of either.
I am a customer. I am not that happy with the current state of affairs, have every right to be that way and I know that I have no rights to expect anything by any date, so I may assuage my disappointment with the purchase of some other game this weekend and not give a favorable recommend to another person if asked about customer support and the fixing of problems with this new "flagship" product.
Alternatively here, what one should do is not be on the 'bleeding edge". Do not purchase a new game for 6 months or so until the bugs are worked out via a few good patches. This is the "cardinal" rule for game customers but where, I suspect, the zealous multitude and many an innocent consumer would outweigh this perhaps somber strategy to avoid disapointment.