Downtime Notice: Wednesday, August 4th 9:00 AM - 2:00 PM Eastern (-4 GMT)

[Randomdude1223]

The downtime has been extended until 4:00 PM Eastern (-4 GMT) due to additional time needed for the deployment. We will keep you updated.

Every single time there's an update you always delay why cant you just set the proper time from the beginning? you even do this delays with your deplorable weekly server restart seriously have some decency and do something about your time management.

[MJtheKing]

Every single time there's an update you always delay why cant you just set the proper time from the beginning? you even do this delays with your deplorable weekly server restart seriously have some decency and do something about your time management.

Not really. Most of the time worlds are up before the schedule time.

[donblas]

Every single time there's an update you always delay why cant you just set the proper time from the beginning? you even do this delays with your deplorable weekly server restart seriously have some decency and do something about your time management.

They nearly always beat their deadline - years ago this was not the case.

[rabidfox]

Need to follow the Scotty Star Trek rules for giving downtime reports: "It's gonna take a 8 days to fix that server's warp nacelle." 3 hours later: "Servers are up" Players: "You're a miracle worker!"

[Kylstrem]

They need to learn to under promise and overdeliver.

They gain nothing by setting expectation at say 2pm Eastern and meeting that time, but knowing there is a big risk to actually meeting that time.

If they announced downtime from 9am to 5pm Eastern, but then beat that time, they gain all sorts of goodwill by doing better than expected.

[Volumptuous]

Thanks for the heads up Cordo! Thanks to the Dev team for putting things on for us!

Yes even thought there are squeaky wheels that i am sure become redundant, there way more of us who actually like what you all are doing and are grateful for all your hard work, thank you from the silent majority!

[Mindos]

Need to follow the Scotty Star Trek rules for giving downtime reports: "It's gonna take a 8 days to fix that server's warp nacelle." 3 hours later: "Servers are up" Players: "You're a miracle worker!"

https://www.youtube.com/watch?v=8xRqXYsksFg

[Jerevth]

Kind of excited. This just builds the anticipation.
Having troubleshot gear in the past and everyone calling every ten minutes for an update, pfft.
"It'll be up when it's up, faster if you quit calling!"

I got my twenty ready. Gimme saltmarsh.

[Tyrande]

hey devs,

i know you LOVE dodging proper questions, but why - STILL - after all this time, all these updates, is it the same every.....single.....time

literally every time

and we all know the game will be down again either tonight, tomorrow, or both for a hotfix for oversights

every
single
time

I do not speak for them, but from my guesses:

1. There are no proper Quality Engineering involved, no automation, no test planning up front, and developers running the production QA and said its 'good', but in fact its not.
2. Last minute some feature request from management sneak in, scrum scope is updated and the devs were forced to put it in.
3. Found out last minute that the database was not updating as it should, this causes dups, database errors causing character load, ETR, LTR, TR problems. Inventory corruption.

[vms4ever]

Every single time there's an update you always delay why cant you just set the proper time from the beginning? you even do this delays with your deplorable weekly server restart seriously have some decency and do something about your time management.

i do IT-ish work for a living, including managing software development and scheduling production deployments. Scheduling is hard. Identically configured servers aren't identical. Any system sufficiently complicated is indistinguishable from magic and any computer that has a database is sufficiently complicated. And magic always makes things unpredictable.

And that isn't even taking into account the random actions of the Change Control Board (CCB). Whose primary motivation seems to be to making my life miserable.

All in all, I would say that if they get through the downtime with less than a 50% overrun they have done well and should count it as a success.

[WaxLyrical]

i do IT-ish work for a living, including managing software development and scheduling production deployments. Scheduling is hard. Identically configured servers aren't identical. Any system sufficiently complicated is indistinguishable from magic and any computer that has a database is sufficiently complicated. And magic always makes things unpredictable.

And that isn't even taking into account the random actions of the Change Control Board (CCB). Whose primary motivation seems to be to making my life miserable.

All in all, I would say that if they get through the downtime with less than a 50% overrun they have done well and should count it as a success.

You are kidding right? Who do you work for that a 50% downtime overrun is normal?

[vms4ever]

I do not speak for them, but from my guesses:

1. There are no proper Quality Engineering involved, no automation, no test planning up front, and developers running the production QA and said its 'good', but in fact its not.
2. Last minute some feature request from management sneak in, scrum scope is updated and the devs were forced to put it in.
3. Found out last minute that the database was not updating as it should, this causes dups, database errors causing character load, ETR, LTR, TR problems. Inventory corruption.

There are 15 classes, 22 races, 3 enhancement trees per class (45 total), 5 universal enhancement trees, scads of monsters, unique abilities, hundreds of quests (each with multiple triggered events), etcetera, etcetera, etcetera. I have pondered how many test cases would be needed to full test DDO and conclude that it would be in the millions, if not billions. I'm just surprised it all works as well as it does.

[Cordovan]

The game worlds have reopened.

[Qlumsee]

Bought my expansion and the client is updating as I type this.

[MJtheKing]

The game worlds have reopened.

Awesome! Release notes?

[Alrik_Fassbauer]

The Spooky Summer of the Sinister Secret of Saltmarsh ...

[vms4ever]

You are kidding right? Who do you work for that a 50% downtime overrun is normal?

I work in the real world. Simple tasks are more predictable. The more complicated things get, the less predictable they are. So far people seem to be happy with my performance, they keep giving me raises.

[Hulligan]

Awesome! Release notes?

https://www.ddo.com/en/update-50-release-notes

[MJtheKing]

https://www.ddo.com/en/update-50-release-notes

Thank you

[Sylvado]

i do IT-ish work for a living, including managing software development and scheduling production deployments. Scheduling is hard. Identically configured servers aren't identical. Any system sufficiently complicated is indistinguishable from magic and any computer that has a database is sufficiently complicated. And magic always makes things unpredictable.

And that isn't even taking into account the random actions of the Change Control Board (CCB). Whose primary motivation seems to be to making my life miserable.

All in all, I would say that if they get through the downtime with less than a 50% overrun they have done well and should count it as a success.

Try it for GxP applications for a real hell. I've even had my own signature rejected.