Reading/Web/Release process

Product release process

 * 1) Prototyping
 * 2) Define  quantitative testing plan
 * 3) Define deployment plan
 * 4) Do we roll out to several wikis at a time?
 * 5) Will testing on the beta cluster / reading web staging be sufficient?
 * 6) Will we roll out to beta mode than stable?
 * 7) Do we have any dependencies on other teams (e.g. security)?
 * 8) How will we achieve what we agree to?
 * 9) Development
 * 10) Development complete
 * 11) Feature flag/kill switch
 * 12) Code quality review
 * 13) Security Review
 * 14) BETA
 * 15) Full QA
 * 16) Instrumentation
 * 17) Testing (qualitative/quantitative)
 * 18) Bug Fixing
 * 19) Full documentation on-wiki and rollout plan
 * 20) Internal performance review
 * 21) API dashboard
 * 22) Performance review by the performance team
 * 23) Community consensus
 * 24) GO

Development release process
The reading web team current release process is the normal Wikimedia release process. See Version lifecycle, and Release checklist for more info.

We previously experimented with a branch based release process.