|
Originally Posted by PanthroEldre
How the hell does something like this get past internal testers?
|
OT and all, but having a fair understanding of the processes involved, the only way to 100% guarentee that this never happens ever is to run the installer for every stable breed of the patch on clean installs, repeatedly. Even using extremely fast computers with great imaging software you're talking aobut a nontrivial amount of time for -every- build including ones with dealbreaking problems entirely unrelated. I'd say that odds are pretty good that there was a feature to do this very thing, fully functional in at least one push.
Not to mention the issues on patch day doubtless invovled slightly altering the installer in an extreme time crunch so some stuff gets overlooked.
I'm all for slagging blizz as much as the next guy, but this looks like a pretty easy one to miss as QA.