Mobile web/MobileFrontend deployment

= Schedule =

Launch Sprint
Goal: Sprint Planning for deploying the Mobile frontend

Stories

What do we have to do in order to dark launch and have an opt in system for mobile? .. and then Production launch two week later


 * Install Varnish on tesla - high
 * Test Patricks new varnish code - high
 * Profile user agent detection - Will we need to expand the Bits Varnish cluster?
 * base64 encode images - http://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3/includes/libs/CSSMin.php?view=markup - low
 * Can we invalidate articles in varnish - will a single purge cover all possible variants of a document? - high
 * Where is the extension going to run?
 * Do we need to order hardware for this? - high
 * Add profiling for extension - high
 * Do we need to use .m urls? YES .. how can we do it? - high
 * Squid redirect patch
 * Don't redirect people who have opted out
 * Write udp log patch for Varnish using the same logformat - see: https://rt.wikimedia.org/Ticket/Display.html?id=85 - med
 * Can add an new column in the log to surface render type (wap vs smartphone)

External testing sites:
 * http://www.blaze.io/mobile/result/?testid=110617_4M_394