Page MenuHomePhabricator

1.37.0-wmf.4 deployment blockers
Open, MediumPublicRelease

Details

Backup Conductor
LarsWirzenius
Release Version
1.37.0-wmf.4
Release Date
Mon, May 3, 12:00 AM
Train Status

Currently stable on group1.

2021 week 18 1.37-wmf.4 Changes wmf/1.37.0-wmf.4

This MediaWiki Train Deployment is scheduled for the week of Monday, May 3rd:

Monday May 3rdTuesday, May 4thWednesday, May 5thThursday, May 6thFriday
Backports only.Branch wmf.4 and deploy to Group 0 Wikis.Deploy wmf.4 to Group 1 Wikis.Deploy wmf.4 to all Wikis.No deployments on fridays

How this works

  • Any serious bugs affecting wmf.4 should be added as subtasks beneath this one.
  • Any open subtask(s) block the train from moving forward. This means no further deployments until the blockers are resolved.
  • If something is serious enough to warrant a rollback then you should bring it to the attention of deployers on the #wikimedia-operations IRC channel.
  • If you have a risky change in this week's train add a comment to this task using the Risky patch template
  • For more info about deployment blockers, see Holding the train.

Related Links

Other Deployments

Previous: 1.37.0-wmf.3
Next: 1.37.0-wmf.5

Event Timeline

thcipriani triaged this task as Medium priority.
thcipriani updated Backup Conductor, added: LarsWirzenius.
brennen added a project: User-brennen.
brennen added subscribers: dancy, brennen.

Assigning to @dancy for coverage while I'm out on the 4th; will pick back up as primary after that.

Not very, but notably risky patch! 🚂🔥

Risky Patch! 🚂🔥

1.37.0-wmf.4 has been on group0 for several hours. No apparent errors. Train looks good.

Note the client side errors for T262470 are spiking today and potentially could meet the train rollback criteria tomorrow. When rolling the train out tomorrow we should keep an eye on logstash for any huge client error spikes relating to that. cc @egardner for someone who actually knows this code and can speak for any possible impact.

Chatted to @egardner and the above error is likely limited to commons so not likely to be an issue tomorrow.

Chatted to @egardner and the above error is likely limited to commons so not likely to be an issue tomorrow.

The "missing mediainfo tabs" error can only come from WikibaseMediaInfo, which is only deployed on Commons and is only active on File pages there. Why is it spiking now when the relevant code has not been touched in some time? That's another question.