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, also with Mark Holmquist)

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
 * parsoid init script doesn't play well when run over ssh


 * browser tests in Gerrit.
 * ✅ First with ULS cause it is simpler, pairing with Zeljkof and i18n team
 * Second MobileFrontend https://gerrit.wikimedia.org/r/#/c/97497/
 * later VisualEditor


 * ✅ polishing up the mw release tarball job (was )

Andre

 * Google Code-In: Run and organize contest with Quim.
 * Agree and finalize on "etiquette" for behavior in Bugzilla, as discussed on teampractices@. - incorporated feedback from teampractices@, now asked for feedback on wikitech-l@
 * Evaluate Project management / issue tracking requirements and potential tools. - kicked off on teampractices@ and wiki on 2013-12-13
 * 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. Steps discussed between dzahn and aklapper on 2013-12-06; first dzahn to set up Bugzilla 4.4 on zirconium in eqiad (see RT #4783 to track progress)
 * 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
 * In process, met with Mark Holmquist and Aaron Aarcos Dec 5
 * Move login method to shared code (Željko working on this right now), demonstrate improved pass rates pairticularly for IE
 * In process, interim commit is https://gerrit.wikimedia.org/r/#/c/100579/
 * Concrete steps for Mobile QA after Michelle's departure
 * Mobile discussion scheduled. Chris/Jeff/Rummana to contribute as requested, e.g. https://gerrit.wikimedia.org/r/#/c/99690/ found while testing group0
 * managing the backlog of mingle cards for tests immediately
 * Browser test coverage for Flow
 * Added https://gerrit.wikimedia.org/r/#/c/99260/.
 * continue to train S in this

Jeff

 * Continuing to add Visual Editor browser 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
 * Blocked on developing a browser test for the "Nearby" page for the Mobile team due to an issue with GeoData in Betalabs :
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=57450
 * Will have a discussion this week with Tomasz Finc about Mobile team request for QA assistance with post-deploy verification
 * Looking at a request from Antoine to setup Visual Editor browser test triggers
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=53691

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.