Software updates doesn't require server maintenance. These are for two things:
- Server software update, maintenance or changes to server capacity.
- Maintenance or changes to infrastructure (data-center, hardware related).
Including a new VGT, paint colors, other cars, tracks doesn't require maintenance. (well, it depends, tracks and cars maybe needs a counterpart in the server, it depends on how they built it).
We can follow two lines of thought:
1) Data center maintenance:
It happens and it doesn't depend on PDI. For instance, Microsoft Azure is giving a 5 hours maintenance in its Virtual Machines. I'll be affected when it's day 10. (I don't have any idea where PDI hosts its servers, otherwise we could just look up their schedule. Azure, Amazon or Sony's own server)
If it's it, then we have no hope.
2) Software changes on the sever:
Usually we do all stuff on a development server. So we can test, manipulate data, test again and so forth. Then a few days before a release things are posted to the production server. Where you can test things again and see how they are going to behave before allowing users to do so.
Those updates from development server to production server should be fast and (at least where I work) I doesn't take more than 5 minutes when it's relate only to update the server application (exe, dll). When it's on a database it can take more time when creating a table or fields (it all depends on your infrastructure and number of users. GT has a few
). And finally when it's related to changing server capacity or even the server itself, it takes a loooooot longer.
If I could bet, I would bet it's the last one: Server capacity changes to support a more demanding software. If it has community features it is justified.
Kaz already said he was testing the new Course Maker, and it was a while ago. Recently he said it was giving them more trouble than expected. What justifies the long period of testing.
If it's not day 9 we are getting it. It's really close.
