On 02/20/2013 12:04 PM, Luke Welling WMF wrote:
I am strongly of the opinion that within broad ranges
deployment frequency
does not matter. It really does not matter if you deploy twice an hour or
every second day.
What teams deploy every second day?
But, having the machinery to make it so that you could
deploy twice an hour
if you wanted to is all kinds of valuable.
Putting time into building:
* Continuous integration with build-on-commit
* Tests with good coverage
* A staging environment that reflects production
* Managed configuration
* Scripted deployment to a large number of machines
pays dividends in uptime, ops sanity and developer productivity even if you
only use that machinery every few days.
We have some of that, but heading further down that road would be a good
thing even if we chose to keep organized periodic deployments.
I couldn't agree more. It's not that I feel a need of deploying
something every single day, I just want the whole process to be easier
and less scary, so that it doesn't disrupt everyone's work for half a
day. Also, it shouldn't be a big deal to push a quick fix in between
deployments.
--
Juliusz