[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

avoid friday deployments?



Hi,

In my previous work, I learned, the hard way, the value of avoiding
major deployments on friday. With the updates of ca-certificates, puppet
*and* sudo pending in my queue, I figured it would be worth bringing
up this policy discussion here.

The basic idea is that when you do a deployment on a friday, you must be
ready to work on the weekend, because regardless of how much you tested
it, a deployment can always go wrong, and the closer to your weekend you
will do it, the harder it will fail. Therefore, my suggestion is we keep
the "casual friday" only for light work, testing and reviews. Push back
deployments to sunday or monday.

What do people think of such a policy? Should I refrain from uploading
those three packages today and complete that work monday?

Bonus points for horror stories (or positive experiences!) of friday
deployment shared.

Thanks!

A.

PS: I am aware that timezones may confuse this a little and that by the
time you read this, it may already be saturday in certain places on
earth (hello Australia!). The point is still valid, however: you'd be
doing a deployment on a saturday, which is already the weekend. And if
you do a deployment on thursday, it may be friday morning for those poor
australians, but at least they got their full extra magic day ahead of
them to fix stuff up...

PPS: I am ignoring other planets, for now, as there are all sorts of
other issues around *that* problem that go beyond our current scope. I
assume NASA handle that stuff on their own, but I'd be glad to be proven
wrong as well.

-- 
Software gets slower faster than hardware gets faster.
                         - Wirth's law


Reply to: