Wikimedia Release Engineering Team

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

= Status =

Dec-Feb Goals
See the WMF Engineering 13-14 goals page for the yearly view.


 * Browser tests managed in feature repos with feature teams (Chris, Zeljko, Jeff, Rummana)
 * Successfully managed the first release of MediaWiki in conjunction with our outside contractor (Greg, Antoine)
 * More comprehensive quarter assessments of postmortems (Greg)
 * Create process documentation for ideal test/deployment steps (Greg, Reedy, Chris, and others)
 * Automated API integration tests in important areas (Chris, Zeljko, Jeff, Rummana, Antoine)

December
Greg
 * Create baseline flowchart of dev/deploy documentation for use in the January in-person meeting
 * Create plan to evaluate progress on postmortem/retrospective actions

Antoine
 * jenkins job for VisualEditor / Parsoid (reporting to James F / Gabriel Wicke)
 * making sure a change in VE or in Parsoid does not break the other since they are tightly coupled
 * browser tests in Gerrit.
 * First with ULS cause it is simpler, pairing with Zeljkof and i18n team
 * Second MobileFrontend
 * later VisualEditor
 * polishing up the mw release tarball job.

Reedy

Andre
 * Google Code-In: Run and organize contest with Quim.
 * Agree and finalize on "etiquette" for behavior in Bugzilla, as discussed on teampractices@. - discussion on teampractices mailing list and talk page
 * Start planning evaluation of Project management / issue tracking requirements and potential tools.
 * Test Bugzilla 4.4 with our custom patches on Labs (or zirconium in eqiad if production is still on kaulen in Tampa)., will need help from ops
 * Deploy Bugzilla 4.4 to production., will need help from ops

Chris
 * Get everyone interested in API testing and monitoring pulling together: Multimedia + Jenkins + QA
 * Move login method to shared code (Željko working on this right now), demonstrate improved pass rates pairticularly for IE
 * Concrete steps for Mobile QA after Michelle's departure
 * managing the backlog of mingle cards for tests immediately
 * Browser test coverage for Flow
 * continue to train S in this

Željko
 * move shared code from (10 or so) extension repositories to mediawiki-selenium Ruby gem
 * update QA/testing documentation (focused on new contributors)
 * mentor language team (Amir, Niklas): refactor existing tests, write new ones (8 hours every week)
 * Antoine: could pair up, since ULS going to trigger via Gerrit. Same needs to be done for MobileFrontend.
 * mentor Google Code-in students: write new Selenium tests, update QA/testing documentation (1-2 hours every day)
 * mentor random volunteers: write new Selenium tests, update QA/testing documentation (https://www.mediawiki.org/wiki/Pair_programming_Friday_for_fun_and_profit) (1 hour every week)

Jeff
 * Add automated Visual Editor tests to fill in gaps
 * Try and get Jenkins (CloudBees) versions of VE automated tests from red to green
 * Some tasking and mentoring for Google Code-in students
 * Working with James, Roan, and Rummana on QA verification of weekly VE releases

Rummana
 * Regular exploration testing on production
 * Verifying each week's VE deployment
 * Verifying resolved bugs
 * Track the already reported bugs on bugzilla and changing their status accordingly

Check-ins

 * /Checkin-20131202
 * /Checkin-20131119
 * /Checkin-20131105
 * /Checkin-20131008
 * /Checkin-20130924
 * /Checkin-20130917
 * /Checkin-20131022
 * /Checkin-20130910
 * /Checkin-20130903

Quarterly Reviews

 * November 2013
 * August 2013

Backlog/Wishlist
We maintain a list of projects that would be great to have done, but are not on our roadmap in in the near term. See the wishlist here.