Page MenuHomePhabricator

1.36.0-wmf.35 deployment blockers
Closed, ResolvedPublicRelease


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

2021 week 11 1.36-wmf.35 Changes wmf/1.36.0-wmf.35

This MediaWiki Train Deployment is scheduled for the week of Monday, March 15th:

Monday March 15thTuesday, March 16thWednesday, March 17thThursday, March 18thFriday
Backports only.Branch wmf.35 and deploy to Group 0 Wikis.Deploy wmf.35 to Group 1 Wikis.Deploy wmf.35 to all Wikis.No deployments on fridays

How this works

  • Any serious bugs affecting wmf.35 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.34
Next: 1.36.0-wmf.36

Event Timeline

group0 and group1 at 1.36.0-wmf.35

T277702: GrowthExperiments\Maintenance\RefreshLinkRecommendations: no transaction to commit, something got out of sync produces some logspam ("no transaction to commit, something got out of sync") but is harmless otherwise. Fixed in master, only happening on testwiki, did not seem worth a backport. Just FYI.

Also a FYI, I have been dropping lots of code from flagged revs, if you see anything related to flaggedrevs in logs, let me know.

Mentioned in SAL (#wikimedia-operations) [2021-03-18T23:06:44Z] <brennen> train status: 1.36.0-wmf.35 (T274939) stable on all wikis after deploy of hotfix for T277795

@Ladsgroup any chance T277795 qualifies?

Fortunately for me, it doesn't :D

hashar subscribed.

1.36.0-wmf.35 is on all wikis. Next is 1.36.0-wmf.36 via T274940

Thank you everyone!