Page MenuHomePhabricator

1.36.0-wmf.30 deployment blockers
Closed, ResolvedPublicRelease


Backup Train Conductor
Release Version
Release Date
Feb 8 2021, 12:00 AM
Train Status
T274589 has been occurring since at least wmf.27 so it has been removed as a blocker. As of Tuesday morning 1.36.0-wmf.30 has been deployed to all wikis.

2021 week 06 1.36-wmf.30 Changes wmf/1.36.0-wmf.30

This MediaWiki Train Deployment is scheduled for the week of Monday, February 8th:

Monday February 8thTuesday, February 9thWednesday, February 10thThursday, February 11thFriday
Backports only.Branch wmf.30 and deploy to Group 0 Wikis.Deploy wmf.30 to Group 1 Wikis.Deploy wmf.30 to all Wikis.No deployments on fridays

How this works

  • Any serious bugs affecting wmf.30 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.29
Next: 1.36.0-wmf.31

Event Timeline

Note: New extension (PageNotice) will be branched starting with this train; it won't be configured or anything, so it shouldn't cause any issues. See T61245 for details.

mmodell raised the priority of this task from Medium to High.Feb 9 2021, 4:00 PM

What is the plan for this week given the situation over the last 2 trains?

Mentioned in SAL (#wikimedia-operations) [2021-02-10T00:01:19Z] <twentyafterfour> train status: wmf.28 and wmf.29 are undeployed. wmf.27 is everywhere with the exception of testwikis which is at wmf.30 refs T271344

End of Tuesday status: wmf.30 on test wikis; wmf.27 on all other wikis
Needs attention: -- code review for backport to wmf.30
Train status: blocked going to group0

Mentioned in SAL (#wikimedia-operations) [2021-02-10T15:05:27Z] <hashar> group0 wikis to 1.36.0-wmf.30 T271344

In T271344#6822691, @Majavah wrote:

T274526: Ranges in block logs can't be clicked to view contributions anymore seems to be a new issue in this train, not sure if a blocker.

It seems to be a 1.36.0-wmf.30 regression indeed. Then it is very very minor and should not hold, we can just backport it after we have rolled to all wikis, that seems pretty trivial to do.

Mentioned in SAL (#wikimedia-operations) [2021-02-11T20:26:03Z] <twentyafterfour> new train blocker preventing deploy of 1.36.0-wmf.30 to all wikis. T274589 blocks T271344

Mentioned in SAL (#wikimedia-operations) [2021-02-11T23:44:47Z] <twentyafterfour> Train status for wmf.30 (T271344) is blocked until monday. leaving wmf.30 on group1 and wmf.27 on group2 in spite of T260401

Mentioned in SAL (#wikimedia-operations) [2021-02-12T19:34:22Z] <twentyafterfour> Train status: Rolling back commonswiki to wmf.27 due to T274589 (refs T271344)

@mmodell @hashar At T274589#6832821, it is proven that the only task marked as blocker with no fix actually happens even in wmf.27. Should we roll forward with wmf.30?

Mentioned in SAL (#wikimedia-operations) [2021-02-16T14:24:08Z] <twentyafterfour> MediaWiki train: prepare to promote all wikis to 1.36.0-wmf.30 refs T271344

Mentioned in SAL (#wikimedia-operations) [2021-02-16T14:38:07Z] <twentyafterfour@deploy1001> rebuilt and synchronized wikiversions files: all wikis to 1.36.0-wmf.30 refs T271344 bfc73b6e8b33e49e916d9d93cf5cdb7624297d44