Flow/2013-12 Deployment

We have the Tuesday 2013-12-10 1pm (13:00-15:00 PDT) deployment window for our deployment to enable Flow on a few pages on mediawiki.org


 * gerrit config patch is
 * tracking bug

The pages

 * mediawiki.org
 * Talk:Flow QA, Talk:Sandbox, Talk:Flow


 * testwiki
 * testwiki:Talk:Flow QA, testwiki:Talk:Sandbox


 * test2
 * test2wiki:Talk:Flow QA, test2wiki:Talk:Sandbox

There's no content to archive:
 * Talk:Flow QA doesn't exist
 * Talk:Sandbox is a redirect to Project:Sandbox and nothing links to it.
 * Talk:Flow is a redirect to Talk:Flow Portal and only has two links.

Checklist

 * ❌ Reedy +1 on
 * Chris Steipp security review, met Monday 2013-12-01 9:30 PST
 * ✅ ops (Faidon) OK
 * ✅ We won't have dedicated memcache servers for this
 * this plan

Pre-deploy

 * ✅ Edit the pages to say "Flow team will enable Flow on this page on 2013-12-04. After that, if you can see this then we reverted or something has gone wrong." For bonus points, make Flow-enabled.

Deploy steps
It's How to deploy code, with some database changes.
 * push out extension code
 * run scap to push it and rebuild l10n cache
 * do we need to push any other file to get l19n cache to rebuild? (extension-list?)
 * Should we ask push the (inactive) extension code out during the MW regular deploy window prior?


 * install db changes on extension1 cluster
 * mwscript sql.php --wiki=flowdb --cluster=extension1 extensions/Flow/flow.sql (?)
 * run mwscript xxxx maintenance/FlowDefaultDefinitions.php


 * push out config changes that switch it on
 * +2
 * sync-file the config files
 * any particular order?
 * monitor for errors
 * xx
 * run QA tests on test2.mediawiki.org
 * probably have to fix beta cluster for Flow on separate flowdb (see Matthias comment)

Testing

 * Visit the URLs.
 * Point browsertests at test2wiki.