Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | Reedy | T289585 Release MW 1.37.0 | |||
Resolved | Reedy | T289595 Branch and tag a final version of Parsoid for REL1_37 | |||
Resolved | Jdforrester-WMF | T295797 Fix mwgate-node12-docker failures in Parsoid branches |
Event Timeline
Change 722442 had a related patch set uploaded (by Jforrester; author: C. Scott Ananian):
[mediawiki/vendor@REL1_37] Bump wikimedia/parsoid to 0.14.0-a19 for 1.37.0-rc.0
Change 722442 merged by Jforrester:
[mediawiki/vendor@REL1_37] Bump wikimedia/parsoid to 0.14.0-a19 for 1.37.0-rc.0
It also looks like we're still to create a REL1_37 branch inside the parsoid repo (incase of future backports etc).
Can we just use v0.14.0-a19 for that branch point, and then also tag that commit as v0.14.0?
Aaaand.... https://gerrit.wikimedia.org/r/c/mediawiki/services/parsoid/+/725913 needs to go into that branch seemingly, based on https://github.com/wikimedia/parsoid/blob/v0.14.0-a19/composer.json#L57
REL1_37 branch created from rGPAR5102525d6f33: Improve mw-empty-elt detection in Cleanup DOM handler, which is also the commit of v0.14.0-a19
Yes, that's a good plan. Looks like you're doing that? I can also do it if that helps.
And now falling over T295797: Fix mwgate-node12-docker failures in Parsoid branches :)
Change 739357 had a related patch set uploaded (by Reedy; author: Reedy):
[mediawiki/vendor@REL1_37] Upgrading wikimedia/parsoid (v0.14.0-a19 => v0.14.0)
Change 739358 had a related patch set uploaded (by Reedy; author: Reedy):
[mediawiki/core@REL1_37] Upgrading wikimedia/parsoid (v0.14.0-a19 => v0.14.0)
Change 739357 merged by Reedy:
[mediawiki/vendor@REL1_37] Upgrading wikimedia/parsoid (v0.14.0-a19 => v0.14.0)
Change 739358 merged by jenkins-bot:
[mediawiki/core@REL1_37] Upgrading wikimedia/parsoid (v0.14.0-a19 => v0.14.0)
v0.14.0 created against rGPARaa88828c6619: .gitreview: Swap defaultbranch for track=1