The reason the graveyard shift bothers me is because it isn't what I was saying or thinking. It is the exact opposite of what I was thinking and trying to say - 100% opposite.
As for the 24 hour shift, I didn't include it in the original message because I didn't think it would be necessary. What I was asking SE was to consider players, when making non-urgent / non-monthly maintenance decisions.
I didn't suggest the 24 hour delay fix, as my goal was only to ask for them to include customers / players in their decision making process. Leaving it up to them to make the decision, while including consideration for players is ALL I WANTED TO SAY.
I gave the 24 hour delay example ONLY once I realized people thought I was asking the Japanese to work at say midnight their time. NO WAY WOULD I WANT OR THINK THEY SHOULD WORK AT MIDNIGHT THEIR TIME, especially when a simple 24 hour delay would be so simple.
As for the development team, I suspect they didn't control the hardware upgrade from the start, but did have control over the day, itself, but after someone earlier set the day.
The start to finish would be management, as the control of the budget and planning of events is higher up the food chain. They plan things far enough out a day change wouldn't matter to them during the initial planning phase.
It is easier to make good and cost effective decisions, when considering everything from the beginning. Customers are something a company should consider from the first day of the planning cycle. Isn't it?????