Post on EQ forum from SKLug, an EQ coder:
Because players have no real window into the QA process. {And we are glad they don't}
The code that actually caused this bug in particular has been around since early April. {This has been broken for a long time}
It's something that's difficult to test for unless you're specifically looking for it, {We didn't want to spend the time to look for the problem because it takes a lot of effort}
though arguably better notes from code could have pointed QA in that direction. That's always something we try to improve. {The coders didn't take any notes of what in the hell they were doing so we can't reproduce what they did, although we have it on our 'to do' list to take more notes}
In terms of why we don't turn it around faster and patch immediately--that's because we've tried that before, and ended up causing worse problems. {When we try and repair stuff we break, we always seem to make it worse}
This is not a problem that causes people to not be able to play the game, which is the only kind of problem that gets patched immediately without the full QA process. {There is still a TON of content you can immerse yourself in while this remains broken, last I checked, Crushbone was empty, and as long as you keep paying, I mean playing, QA can give a rat's azz whether there is something else that is broken}
Even then, there is usually at least several hours of QA done. {Even when it involves losing the paying public, it takes us several hours to wake QA up and get them their meds and coffee}
In any case, I'm not in charge of when patches happen, etc. {Hey, thank goodness I am not in charge here, and really, I don't have a clue who is}
I'm only estimating from experiences in the past. I'm sure we'll know more Monday. {Well, maybe not Monday, but at least I can get away from here for the weekend without anyone hoping for a patch over the weekend}