MediaWiki 1.19/Roadmap

Timeline

 * December 2011 - Reduce unreviewed revisions from over 1000 to under 300
 * January 2012 - Reduce unreviewed revisions from 300 to none, branch 1.19 for deployment
 * Our target is to have a completely reviewed trunk on January 31.
 * February 2012 - Deploy MediaWiki 1.19 to the production cluster

Deployment schedule

 * Monday, February 13 (-14), 2012, 23:00-01:00 UTC (3pm-5pm PST):
 * Test deployment to:
 * [//test2.wikipedia.org/wiki/Main_Page test2] ✅
 * Wednesday, February 15 (-16), 2012, 23:00-01:00 UTC (3pm-5pm PST):
 * Stage 1 deployment to:
 * mediawikiwiki, strategywiki, usabilitywiki, simplewiki, simplewiktionary, metawiki ✅
 * February 16 (-17), 2012, 23:00-01:00 UTC (3pm-5pm PST):
 * Stage 1 deployment (continued) to:
 * hewikisource, frwikisource, eowiki, betawikiversity, enwikiquote, enwikibooks  ✅
 * Tuesday, February 21 (-22), 2012, 23:00-03:00 UTC (3pm-7pm PST):
 * Stage 2 deployment to:
 * commons ✅
 * Thursday, February 23 (-24), 2012, 23:00-03:00 UTC (3pm-7pm PST):
 * Stage 3 deployment to:
 * All projects except Wikipedia ✅
 * Monday, February 27 (-28), 2012, 23:00-03:00 UTC (3pm-7pm PST):
 * Stage 4 deployment to:
 * nlwiki, plwiki ✅
 * Wednesday, February 29 (-March 1), 2012, 23:00-03:00 UTC (3pm-7pm PST):
 * Stage 5 deployment to:
 * All Wikipedia sites ✅

Significant code changes
This is a list of significant code changes for the purposes of code review organisation.

Core

 * {Request,I,Derivative}Context
 * Localisation Cache ACCEL store (r101507)
 * FileBackend refactoring, an important part of the SwiftMedia project
 * Other changes tagged "important"

Testing and release planning
Main testing charter Also to check: everything reported between Oct 4, 2011 (deploy day for 1.17) and Oct 15, that we fixed before Oct 31

Other TODOs:
 * Prepare for 1.19 beta testing by compiling a list of people who reported problems in 1.17.0, 1.17.1 & 1.18.0. Ask them to be on-call to test.
 * Mark and Chris to compile the list -- Amgine, et al.
 * Chris to possibly ask them to test trunk versions, definitely ask them to test the 1.19 branch.
 * Discuss testing community communication with Mark & Ashar (testing mailing list? meetings?)

Documents

 * Current code review numbers
 * Code review projection
 * Revision report — Remaining revisions and issues that need to be resolved before the release.
 * Status updates
 * Post-deploy retrospective — What went well, and what should we look into?
 * MediaWiki 1.19/Roadmap/Deployment checklist

Communications

 * MediaWiki 1.19/Communications — Communications plan around MediaWiki 1.19