Please review or create your update deployment process

[[email protected] 2]

Hello DayZ (and six updater) devs,

I'd like to take the opportunity to let you know some of the problems we've met when 1.7.2.4 was deployed. To be honest, the deployment schedule was messed up. From my admin point of view, the server update wasn't even available in Vilayer's UI when the client update was. This messed up my team's clients as Six Updater thought it would be a good thing to update all clients, even though they still tried to connect to a 1.7.2.3 server.

We had to roll back our clients using dropboxes as, fortunately, one of us didn't used Six updater and still had the right version.

TL;DR:

So please, make sure the server hosting services you work with have made your update available, before you start distributing the client version. This way, it's much easier for us to manage the migration to the new version.

[Jukez 44]

Hello DayZ (and six updater) devs,

I'd like to take the opportunity to let you know some of the problems we've met when 1.7.2.4 was deployed. To be honest, the deployment schedule was messed up. From my admin point of view, the server update wasn't even available in Vilayer's UI when the client update was. This messed up my team's clients as Six Updater thought it would be a good thing to update all clients, even though they still tried to connect to a 1.7.2.3 server.

We had to roll back our clients using dropboxes as, fortunately, one of us didn't used Six updater and still had the right version.

TL;DR:

So please, make sure the server hosting services you work with have made your update available, before you start distributing the client version. This way, it's much easier for us to manage the migration to the new version.

I suggest you to stop using 6updater and switch to DayZ Commander, that actually tells how many servers use the updates and lets you decide when you want to update your arma2beta/dayz.

Edited August 3, 2012 by Jukez

[Bobcomss 189]

Use DayZ Commander :)