Wikimedia Release Engineering Team

This is the team responsible for Release Engineering/Management and Quality Assurance at the Wikimedia Foundation. We predominately use the QA mailing list for project coordination/discussion along with conversations on the appropriate IRC channels (especially, , , and ).

= Status =

Planning
Quarterly Reviews ...cont Archives Other
 * August 2014
 * April 2014
 * Mid-quarter checkin
 * February 2014
 * Mid-quarter checkin
 * November 2013
 * August 2013
 * Weekly checkin archive
 * Quarterly goal progress archive
 * Wishlist
 * Metrics
 * Ongoing Maintenance
 * Vagrant survey

Sept - Nov '14 Goals Progress

 * For past quarter's checkins, see the archives.
 * See the WMF Engineering 14-15 goals page for the yearly view.

Phabricator

 * - Developer support for Migration from Bugzilla completed - Mukunda
 * Be an example early adopter of features
 * - Developer support for Migration from RT completed - Mukunda

metrics
 * - Number of team migrated to Phabricator vs number of teams using Trello/Mingle right now

Deployment tooling

 * - scap(py) & trebuchet integration - Mukunda, Reedy
 * how much and what it looks like TBD, some from the requirements doc
 * - increasing bus factor (specifically: Mukunda can respond to deployment tooling related issues) - Mukunda, Reedy

Jenkins

 * - Jenkins performance improvements - Chris, Zeljko, Antoine
 * - Maintenance and new test infrastructure requests (ongoing) - Chris, Zeljko, Antoine

Beta cluster

 * - Add new services (-oids) - Antoine
 * - Swift cluster (remove NFS) - Antoine
 * - Beta Cluster monitoring (baseline) - Antoine (and Yuvi)
 * - Graphite
 * - Icinga alerts
 * - Yet Another Cluster - Antoine, Chris
 * the use cases for two clusters

metrics
 * - Real data and graphs from monitoring services

Browser tests

 * - Workshops/trainings in lieu of one-to-one pair programming - Zeljko, Chris, Dan
 * Meetup announcement for Exploratory Testing pending tentatively for Oct 22
 * Another training announcement also pending
 * - Improved "best practices" and "getting started" documentation - Zeljko, Chris
 * Chris started overhaul of QA pages on mediawiki.org
 * - Continued pairing with WMF Engineering teams - Zeljko, Chris, Dan
 * - Begin pairing with the Flow team - Chris, Dan
 * starting with refactoring in the Echo tests
 * - Environment abstraction layer in mediawiki-selenium to allow for less fragile and more advanced step definitions (strech goal) - Dan, Zeljko, Chris

metrics
 * - tracking state of browser tests before Thursday branch cut
 * - track days since last green build, per Jenkins job

Vagrant

 * - Wrap up pairing with MobileFrontend - Dan
 * - Investigate creating shareable vagrant- or docker-based test environments - Dan
 * see work from Bryan?
 * - Optimize memory hungry services running in the vagrant VM (reduce base memory usage) - Dan

metrics
 * - qualitative survey of WMF teams on their use of MW-Vagrant
 * - percentage of WMF production deployed extensions available in Vagrant

Hiring

 * - Complete hiring for QA Tester

Mukunda

 * - Phab data import, with Chase and Andre

Greg

 * - Hire QA Tester (jobvite announce

Dan

 * - MobileFrontend broswer tests in Vagrant
 * - Ruby style guide
 * - Refactor MediaWiki-Vagrant according to Ruby style guide

Chris

 * - Use tags to run builds appropriate to released versions (e.g. don't run master build on test2wiki)
 * Antoine fleshing out a start of this idea at Zurich
 * - hire new QA Tester

Antoine

 * - RFC for Jenkins tests isolation
 * wrote and published to ops and engineering lists OK
 * agreement by End of June -> slipped due to discussions
 * POC by End of July
 * - RFC for cross repositories testing and integration job in gate
 * - implementing cross repository cloner (aka have repositories match branches/zuul ref)
 * Example run: https://integration.wikimedia.org/ci/job/mediawiki-core-extensions-integration/56/testReport/