Le 19/10/13 00:26, Erik Moeller a écrit :
Are there other ways to optimize / issues I'm missing or misrepresenting above?
Hello,
As a summary we deploy a new release in three stages spanned over a one week window. The last stage of the previous window occurring the same day as the first stage of the next window.
The three stages are:
1) test wikis (ie mediawiki) 2) non-wikipedias 3) wikipedias
The stages are scheduled as:
Thursday window 1 stage 1 Monday window 1 stage 2 Thursday+7 window 1 stage 3, window 2 stage 1 Monday window 2 stage 2 ...
What about doing all three stages the same day? We could take advantage of our 18 hours presence from Europe to San Francisco. Hence we could go with something like:
8:00 UTC (1am PST): deploy on test wikis (Europe folks) 16:00 UTC (9am PST): deploy non wikipedias (Europe, East Coast + SF) 20:00 UTC (1pm PST): deploy on wikipedias (East Coast + SF)
European folks would catch issues appearing on test wikis, the non wikipedias could be done with Europe+SF and the wikipedias by SF. We also have ops coverage on all that time frame.
With such a system, we could keep deploying on Thursdays and Mondays, though we will deploy two releases per weeks.
Evil plan: deploy automatically on merge. But we are not ready yet :-]