Page MenuHomePhabricator

1.36.0-wmf.33 deployment blockers
Closed, ResolvedPublicRelease


Backup Train Conductor
Release Version
Release Date
Mar 1 2021, 12:00 AM
Train Status

Train is at Group0

2021 week 09 1.36-wmf.33 Changes wmf/1.36.0-wmf.33

This MediaWiki Train Deployment is scheduled for the week of Monday, March 1st:

Monday March 1stTuesday, March 2ndWednesday, March 3rdThursday, March 4thFriday
Backports only.Branch wmf.33 and deploy to Group 0 Wikis.Deploy wmf.33 to Group 1 Wikis.Deploy wmf.33 to all Wikis.No deployments on fridays

How this works

  • Any serious bugs affecting wmf.33 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.36.0-wmf.32
Next: 1.36.0-wmf.34

Event Timeline

Change 667743 had a related patch set uploaded (by DannyS712; owner: trainbranchbot):
[mediawiki/core@wmf/1.36.0-wmf.33] Branch commit for wmf/1.36.0-wmf.33

Change 667743 merged by jenkins-bot:
[mediawiki/core@wmf/1.36.0-wmf.33] Branch commit for wmf/1.36.0-wmf.33

Not sure if T276307: Expectation (masterConns <= 0) not met (via GrowthExperimentsLinkRecommendationStore constructor) should be a blocker considering the volume of logspam it's generating, but in any case backporting a fix to wmf.33 now.

All wikis on 1.36.0-wmf.33 now. Watching logs for problems.

CLosing this, new train starting.