Eh, a problem with a major version upgrade to a network application that can be resolved in less than a couple of hours is actually pretty small. Big problems with such an upgrade can take several hours to fix.
In my industry, we typically pad our estimates of downtime for major rollouts by 10 to 20% to account for the unexpected. But I guess it's hard to do that in an industry where the customers so frequently have no understanding of the degree of work involved in such operations and scream about every moment of scheduled downtime.
Seems reasonable to expect large, high-traffic network game server software to be similar in that regard
Last edited:
