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 along with conversations on the appropriate IRC channels (especially, , , and ).

= Status =

Planning
Quarterly Reviews ...cont Checkins Other
 * August 2014
 * April 2014
 * Mid-quarter checkin
 * February 2014
 * Mid-quarter checkin
 * November 2013
 * August 2013
 * Monthly Checkin Archive
 * Wishlist
 * Metrics
 * Ongoing Maintenance
 * Vagrant survey

Sept - Nov '14 Goals Progress

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

Phabricator

 * - Migration from Bugzilla completed
 * Be an example early adopter of features
 * - Migration from Trello/Mingle started
 * - Migration from Gerrit completed (pending unforeseen issues)

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

Deployment tooling

 * - scap(py) & trebuchet integration
 * how much and what it looks like TBD, some from the requirements doc
 * - increasing bus factor (important due to new hires/team changes)

Jenkins

 * - Jenkins performance improvements
 * -maintenance and new test infrastructure requests (ongoing)

Beta cluster

 * -Add new services (-oids)
 * - Swift cluster (remove NFS)
 * - Beta Cluster monitoring (baseline)
 * - Yet Another Cluster(s)

metrics
 * - Real data and graphs from monitoring services

Browser tests

 * - Workshops/trainings in lieu of one-to-one pair programming
 * - Improved "best practices" and "getting started" documentation
 * - Continued pairing with WMF Engineering teams
 * - Begin pairing with the Flow team
 * - Environment abstraction layer in mediawiki-selenium to allow for less fragile and more advanced step definitions

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

Vagrant

 * - Wrap up pairing with MobileFrontend
 * - Better browser test runner, eg "vagrant run-browser-tests"
 * - Investigate creating shareable vagrant- or docker-based test environments
 * see work from Bryan?
 * - Optimize memory hungry services running in the vagrant VM (reduce base memory usage)

metrics
 * - qualitative survey of WMF teams on their use of Vagrant
 * - number of/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/