Wikimedia Release Engineering Team/Checkin archive/20180528

= 2018-05-28 =

Vacations/Important dates

 * https://office.wikimedia.org/wiki/HR_Corner/Holiday_List
 * How to do it


 * May 28 (Mon): Memorial Day (US Holiday)
 * May 31 (Thrusday): Željko (Holidays in Croatia - Corpus Christi)
 * June 1 (Friday): Željko vacation (git merge holiday weeked)

Train

 * Maniphest query for deployment blocker tasks: https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-fmcvjrkfvvzz3gxavs3a&statuses=open%28%29&group=none&order=newest#R


 * Apr 23 - 1.32.0-wmf.1 - Chad
 * Apr 30 - wmf.2 - Chad
 * May 07 - wmf.3 - Mukunda
 * May 14 - wmf.4 - Mukunda
 * May 21 - wmf.5 - Mukunda
 * May 28 - wmf.6 - Tyler <-
 * June 04 - wmf.7 - Tyler
 * June 11 - wmf.8 - Chad
 * June 18 - wmf.9 - Chad
 * June 25 - wmf.10 - Mukunda
 * July 02 - wmf.11 - Mukunda

SoS

 * Apr 23 - Tyler
 * Apr 30 - Tyler
 * May 07 - Chad
 * May 14 - Chad
 * May 21 - Chad
 * May 28 - Mukunda <-
 * June 04 - Mukunda
 * June 11 - Tyler
 * June 18 - Tyler
 * June 25 - Chad
 * July 02 - Chad

Scrum of Scrums

 * Greg to copy to etherpad after meeting: https://etherpad.wikimedia.org/p/Scrum-of-Scrums

Release Engineering

 * Blocking
 * Blocked
 * Updates
 * Train status: https://phabricator.wikimedia.org/T191051
 * 1.32.0-wmf.5 got held up last week by an incident that happened during the scheduled Thursday train deployment window.
 * https://wikitech.wikimedia.org/wiki/Incident_documentation/20180524-wikidata
 * We should be back on track this week, wmf.5 is clear of blockers and wmf.6 should be rolling out as usual
 * Quarterly cross-dependencies
 * We should be back on track this week, wmf.5 is clear of blockers and wmf.6 should be rolling out as usual
 * Quarterly cross-dependencies

Release Engineering

 * Blocking
 * Blocked
 * Updates
 * The MW Train and SWATs will be normal next week (before the Hackathon) as we have sufficient coverage in RelEng and SRE.
 * Quarterly cross-dependencies
 * The MW Train and SWATs will be normal next week (before the Hackathon) as we have sufficient coverage in RelEng and SRE.
 * Quarterly cross-dependencies

Train status and happenings

 * https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Roles#Train_Conductor


 * So this happened, delaying the train and frustrating Mukunda immensely: https://wikitech.wikimedia.org/wiki/Incident_documentation/20180524-wikidata
 * Resuming wmf.5 on Monday didn't work due to a new critical blocker: https://phabricator.wikimedia.org/T195514
 * I attempted to deploy the fix, however, tests are failing: https://integration.wikimedia.org/ci/job/mediawiki-extensions-hhvm-jessie/47836/
 * Test failure looks unrelated but I don't want to risk deploying something with failing tests. I've been yelled at enough recently.
 * ugh...

Past week status updates

 * All of it in table form: https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Goals/201718Q4

Program 1: Outcome 5: Objective 1: Maintain existing shared Continuous Integration infrastructure

 * Migrate away from Nodepool -
 * Migrate MediaWiki PHPUnit tests to Shipyard (docker-based CI) (~40% of Nodepool usage) -
 * Add Composer support to Blubber -
 * Add Python/Tox support to Blubber -
 * Add Ruby/Gem/Bundler/Rake support to Blubber -

Program 3: Outcome 1: Objective 2: Identify and find stewards for high-priority/high use code segment orphans

 * Broad role out of Code Stewardship model.
 * Update Maintainers/Developers page with currently known Code Stewards.
 * Use Code Stewardship review process to address gaps.
 * Deploy dashboard of Code Stewardship Coverage


 * Closed the discussion period for the Q4 Stewardship reviews.

Program 3: Outcome2: Objective 2: Define and implement a process to regularly address technical debt across the Foundation

 * Roll out of technical debt reduction approaches.
 * Identify early adopter engineering teams to test approaches.


 * scheduled engagement kickoff meetings with Search Plaform and Platform teams

Program 6: Outcome 2: Objective 2: Prove viability of testing staged service containers alongside MediaWiki extension containers

 * Add Composer support to Blubber -
 * Small, standalone, MediaWiki containers built using Blubber
 * Limited scope with: Debian Stretch, php7, composer dependencies, Mariadb, Apache (or last two with standalone containers)
 * Build MW base containers upon branch cut at master branch point from core
 * Build ext specific containers using MW image as base


 * Let's look at some of the composer related work from the Hackathon
 * https://github.com/davidbarratt/mediawiki
 * It appears that people are already successfully installing mediawiki with composer
 * Should we attempt to use it for this objective?

Program 1: Outcome 1: Objective 1: Scap (Tech Debt Sprint FY201718-Q2)

 * workboard

Program 1: Outcome 6: Milestone 2: Maintain Phabricator

 * Streamline logspam workflows by adding some integration with phabricator
 * Store git-lfs (and other phab uploads) in swift:


 * git-lfs stuff is working in my dev environment.
 * Getting it deployed to production is still another thing entirely.
 * Most of the puppet stuff is done but I'll have to work with filippo to get that finalized

Antoine

 * What I plan to do this week
 * Moar Quibble migrations
 * Attempt to migrate the gated extensions jobs (mediawiki-extensions-*)
 * What I'm blocked on
 * core wdio tests fail on some extensions
 * seems some extensions are not working at all
 * Other?

Chad

 * What I plan to do this week
 * What I'm blocked on
 * Other?
 * Other?
 * Other?

Dan

 * What I plan to do this week
 * Evaluate mediawiki/composer projects from the Hackathon
 * https://github.com/davidbarratt/mediawiki
 * Continue to hack on a blubber config for mediawiki/core
 * What I'm blocked on
 * Understanding of composer.json :)
 * Other?

Greg

 * What I plan to do this week
 * What I'm blocked on
 * Other?
 * Other?
 * Other?

Jean-Rene

 * What I plan to do this week
 * Stewardship Reviews
 * Meet up with Search Platform and Platform teams re Tech Debt engagement.
 * Think about various systems as data sources (follow-up to face to face discussion)
 * Send out Beta Cluster Survey
 * What I'm blocked on
 * Other?
 * Other?

Mukunda

 * What I plan to do this week
 * Vacation!!
 * Finish my cnc milling machine
 * Set up my wifi tower, finally (I hope)


 * What I'm blocked on
 * Other?
 * Other?

Tyler

 * What I plan to do this week
 * What I'm blocked on
 * Other?
 * Other?
 * Other?

Zeljko

 * What I plan to do this week
 * T195496 mediawiki-core-qunit-selenium-jessie sometimes fails for extensions
 * T194252 Configure the CI job that runs WikibaseLexeme's browser tests against beta wikidata
 * T167432 Run Wikibase daily browser tests on Jenkins
 * T194959 Write selenium tests for Newsletter extension
 * T193244 selenium-CirrusSearch-jessie does not run any tests
 * What I'm blocked on
 * T194252 Configure the CI job that runs WikibaseLexeme's browser tests against beta wikidata
 * T193883 `FATAL: java.io.IOException: java.nio.file.NoSuchFileException: ...build/screenshots.yml` for language-screenshots-VisualEditor
 * Other?
 * Holiday on Thursday, vacation on Friday (git merge holiday weekend)

Team Kanban Board Review and Triage

 * closed and touched in the 7 days
 * No update for 4 weeks
 * No update for 3 weeks
 * No update for 2 weeks
 * No update for 1 week
 * All Open
 * Review To Triage column of #releng
 * Assigned
 * Unassigned

Once / month-ish review of backlog(s)

 * releng Review To Triage column of #releng
 * releng-kanban Review unassigned in kanban
 * releng-kanban Review 'backlog' colum of -kanban
 * releng-next - Review for things we need to put on our kanban backlog
 * releng-backlog - oh my, the huge backlog of things...

Kanban stats

 * Burnup chart