Quote:
Originally Posted by pokerman64
not that i know all there ins and outs but seeing how im finishing up a systems analysis class, i would think they would have thought of a way to test all this out with another "test" client before actually trying to ship it "live", seems every time they do an update they extend their ETA, understandably you run into errors, but after running into errors so much, I would assume you would plan out the fastest and most efficient way to avoid these common recurring errors when updating.
There was a video of the jackpot spin with test accounts posted weeks ago...where did you hear they didn't "test" this?
Every single time they do scheduled maintenance it takes several hours longer than normal, you'd think they'd just tell us it'll take 12 hours and let us be happy when it only takes 8.