Roan Kattouw (2011-02-01 10:14):
2011/2/1 Rob Lanphierrobla@robla.net:
Can you explain why you're rolling out when it's the middle of the night where Wikimedia is headquartered? I have a few different theories (site traffic, time zones of the operations team, etc.), but a clarification here would be good.
We lost the game of rock/paper/scissors. :) We decided to do this very late U.S. west coast time so that our European and Australian contingents would be well rested in case there are problems. Given that we have key personnel pretty much all over the globe, there wasn't going to be a great time for this, and this has the added advantage of being a relatively low traffic time for us.
Look at http://torrus.wikimedia.org/torrus/CDN?path=%2FTotals%2F and you'll see that, for the past two days, the time of lowest traffic was between 06:00 and 07:00 UTC. This has been a quite reliable pattern for quite some time now (except that it shifts by an hour in Northern Hemisphere summer, due to DST), and we've also used this time for the first few Vector deployments.
[...]
Can you set a different deploy date for different projects? E.g. 18.00 UTC for Poland. I will not be able to be there when hell will brake loose as I will be working and I'm sure most of the Polish tech admins will be too. Note that we was able test Vector with current scripts before the deploment so this is a bit different. And I still remember the ammount of complaints bouncing here and there when Vector came and broke Wikipedia and what not... Not that they were all valid and could have been avoided, but maybe some could.
Not that I'm complaining ;-), but prototype is... well it's empty for now and it would be good if we could test scripts and do it as fast (and as soon) as possible. I've already asked Leinad, but maybe someone could import current Mediawiki namespace to prototype quicker.
For one thing - I think our script for moving the search bar to the left side panel will be probably broken (as you make it wider now) and this will probably have to be fixed right after deployment...
Regards, Nux.