Wikimedia Platform Engineering/MediaWiki Core Team/Quarterly review, July 2013/Release Management and QA

Date: July 31st, 2013

Time: 8:30am Pacific (15:30 UTC)

Who: Topics: Deploy process/pipeline, release process, bug fixing, code review, code management, security deploy/release, automation prioritization
 * Leads: Greg G, Chris M
 * Participants (invited): Antoine, Sam, Chris S, Chad, Zeljko, Michelle G, Robla, Sumana, Quim, Maryana, James F, Ryan Lane, Ken, Terry, Tomasz, Alolita

Deployment sprint
We plan to put the items below in a deployment infrastructure sprint sometime between July and December 2013:

(All bugs listed in sortable BZ search)


 * git-deploy
 * tracking
 * - auditing salt scripts for completeness
 * - deal with dirty git fetches properly
 * Questions:
 * Will Platform take over maintenance of git-deploy?
 * monitoring
 * - Better 500 error/PHP exception monitoring
 * - create monitoring for the issue in that bug
 * Questions:
 * Where should this be stashed in our monitoring?
 * deployment script improvements
 * - Make updates atomic (e.g. symlink + directory move tricks or git-deploy?)
 * - Some improvements for the deployment scripts
 * - Reconciling the use of timestamps on Javascript files (rsync vs ResourceLoader vs git)
 * - resetUserTokens.php not usable on large wikis
 * Kill deployment hacks with fire - live hacks that are still applied as of 2013-05-16
 * multi-site awareness
 * - mwscript.php/mctest.php does not know about memcache in both datacenters
 * - migrate scripts from hume to terbium
 * Database config cleanup -- multisite awareness in MediaWiki
 * Beta related
 * - the use of BetaLabs as a true canary (tracking)
 * - allowing extensions to be run from not master
 * Monitoring of betalabs?
 * on Ops to set that up, whether or not it actually alerts
 * vagrant on labs for quick dev environments? Probably Q4