Page MenuHomePhabricator

1.38.0-wmf.11 deployment blockers
Closed, DeclinedPublic5 Estimated Story PointsRelease

Details

Backup Train Conductor
jeena
Release Version
1.38.0-wmf.11
Release Date
Mon, Nov 29, 12:00 AM

2021 week 48 1.38-wmf.11 Changes wmf/1.38.0-wmf.11

This MediaWiki Train Deployment is scheduled for the week of Monday, November 29th:

Monday November 29thTuesday, November 30thWednesday, December 1stThursday, December 2ndFriday
Backports only.Branch wmf.11 and deploy to Group 0 Wikis.Deploy wmf.11 to Group 1 Wikis.Deploy wmf.11 to all Wikis.No deployments on fridays

How this works

  • Any serious bugs affecting wmf.11 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.38.0-wmf.10
Next: 1.38.0-wmf.12

Event Timeline

thcipriani triaged this task as Medium priority.
thcipriani updated Other Assignee, added: brennen.
thcipriani set the point value for this task to 5.
thcipriani changed Release Date from Nov 23 2020, 12:00 AM to Tue, Nov 23, 12:00 AM.Oct 21 2021, 12:31 AM
thcipriani changed Release Date from Tue, Nov 23, 12:00 AM to Mon, Nov 29, 12:00 AM.Oct 21 2021, 12:41 AM
thcipriani updated Other Assignee, added: jeena; removed: brennen.
thcipriani added a subscriber: dancy.
Risky Patch! 🚂🔥

[mediawiki/core@master] mediawiki.base: Deprecate stateful use of toString()

https://gerrit.wikimedia.org/r/726291

  • Summary: This potentially affects all uses of JS-rendered interface messages.
  • Test plan: Testing by @Krinkle in beta and major wikis as they reach the deployment group.
  • Places to monitor: If it goes wrong, likely a cosmetic issue and not a mechanal one, so no error logs. Look out for reports by users via IRC, Phab, and through local wiki ambassadors.
  • Revert plan: Yes, the patch is small and separated from the rest of the refactor. Easy and uncontroversial to revert.
  • Affected wikis: All.
  • IRC contact: Krinkle
  • UBN Task Projects/tags: MediaWiki-ResourceLoader Performance-Team
Risky Patch! 🚂🔥
  • Change: Rollout of patches to implement T261181: Make Translate extension compatible with Parsoid
  • Summary: Parsoid is changing its support for the Translate extension so that pages with translate markup can be edited via VE (including being able to edit translatable regions). But, since this is the first rollout, things might break on mediawiki.org and metawiki.org (the two main users of this extension right now). Secondly, Parsoid v0.15.0-a10 (the version deployed with 1.38.0-wmf.9) does not have forward compatibility code for the HTML changes being rolled out. So, this means if the train is rolled back, we will need to purge RESTBase content (See T296425) as well.
  • Test plan: This functionality has been tested locally during development and has been put through multiple rounds of round-trip testing. The identified bugs and crashers have been fixed. On rollout to group 0 wikis, @ihurbain will test this again extensively on testwiki.
  • Places to monitor: Logstash: Parsoid.
  • Revert plan: Rollback train and purge RESTBase cache (needs @Pchelolo or someone from PET who can run the RESTBase purge script)
  • Affected wikis: mediawiki.org and metawiki.wikimedia.org
  • IRC contact: subbu[m], ihurbain(WMF staff can find us on slack on #content-transformers and has a bigger set of eyes there)
  • UBN Task Projects/tags: Parsoid