Hi,
I'm interested in what part of the maintenance takes so much time. Are there parts of the program code to be changed in the last minute, bacause it was not well testet? Or something had to be changed on the hardware? Maybe because some harddrive failures or something like this? I really would like to know, what is going on there for so many hours, every week?
Just tell us, maybe we feel better, if we know whats going on, and we could understand. Or is that a big secret?
ZoS never really explain, but for a 96Mb patch it really shouldn't take >9 hours every week. Personally I think their staff isn't as competent as other gaming companies and it takes so long because they run into issues.

No, i am serious. I really would like to know.
With a project this size the list of things that could go wrong is so long that it would be impossible to summarize all of it in any concise fashion.ZoS never really explain, but for a 96Mb patch it really shouldn't take >9 hours every week. Personally I think their staff isn't as competent as other gaming companies and it takes so long because they run into issues.
The size of the client patch has exactly zero bearing on what they are doing to the servers.
With a project this size the list of things that could go wrong is so long that it would be impossible to summarize all of it in any concise fashion.ZoS never really explain, but for a 96Mb patch it really shouldn't take >9 hours every week. Personally I think their staff isn't as competent as other gaming companies and it takes so long because they run into issues.
The size of the client patch has exactly zero bearing on what they are doing to the servers.
And yet no other gaming company have these issues...
Warcraft, arguably a bigger worldspace and larger sever, takes no more than 15mins to 4 hours per maintenance. The extreme end of which is due to errors in the new code or extremely large patches. So what ZoS do for 9-12 hours every Monday is beyond me.
"Small update" that takes 5-6 hours to implement - "Oh we've run into an error." *fives hours later* "Still fixing it, brah."

I sometimes think, that they simply doing something wrong. But these are professionals (i guess), so it must be due to poor equipment ...
nordsavage wrote: »Cut them some slack. Coding for Dummies is at least an inch thick book and it doesn't have pictures.
