Page MenuHomePhabricator

Tracking bug for MediaWiki 1.31.11/1.35.1
Closed, ResolvedPublic

Assigned To
Authored By
Reedy
Sep 24 2020, 11:28 PM
Referenced Files
F33947148: T120883-v9-1.patch
Dec 16 2020, 2:02 PM
F33947153: T120883-v9-REL1_31.patch
Dec 16 2020, 2:02 PM
F33947141: T120883-v8-1.patch
Dec 16 2020, 1:44 PM
F33942272: T120883.patch (v.8)
Dec 16 2020, 1:32 PM
F33946801: T120883-v8-REL1_31.patch
Dec 16 2020, 1:32 PM
F32423162: T205908.patch
Dec 15 2020, 1:52 PM

Description

Previous work: T256335: Tracking bug for MediaWiki 1.31.9/1.34.3/1.35.0

Tracking bug for next security release, 1.31.11/1.35.1

Maniphest IDCVE IDREL1_31REL1_35master
T268894CVE-2020-35474n/amergedmerged
T268917CVE-2020-35475mergedmergedmerged
T268938CVE-2020-35478, CVE-2020-35479merged (1/2 issues applicable)mergedmerged
T205908CVE-2020-35477
T120883CVE-2020-35480

Details

Due Date
Dec 17 2020, 11:59 PM

Event Timeline

Reedy renamed this task from Tracking bug for MediaWiki 1.31.11/1.34.5/1.35.1 to Tracking bug for MediaWiki 1.31.11/1.35.1.Nov 29 2020, 1:38 AM
Reedy set Due Date to Dec 17 2020, 11:59 PM.
Reedy updated the task description. (Show Details)

@Reedy can T120883 be included in the release? At least up through patch v8 (v9 isn't deployed yet on WMF wikis)

@Reedy can T120883 be included in the release? At least up through patch v8 (v9 isn't deployed yet on WMF wikis)

Maybe. The fact it's upto v8 already, and there's a v9... It doesn't seem the most stable, and it has caused at least some breakages already.

@Reedy can T120883 be included in the release? At least up through patch v8 (v9 isn't deployed yet on WMF wikis)

Maybe. The fact it's upto v8 already, and there's a v9... It doesn't seem the most stable, and it has caused at least some breakages already.

Its just that I keep discovering more divergent behavior, and am reusing the same task

@Reedy can T120883 be included in the release? At least up through patch v8 (v9 isn't deployed yet on WMF wikis)

Maybe. The fact it's upto v8 already, and there's a v9... It doesn't seem the most stable, and it has caused at least some breakages already.

Its just that I keep discovering more divergent behavior, and am reusing the same task

You don't really need to keep amending the same patch, unless you're fixing further issues in the same code you've already fixed

Reedy updated the task description. (Show Details)
Reedy updated the task description. (Show Details)
Reedy changed the visibility from "acl*security (Project)" to "Public (No Login Required)".Dec 18 2020, 12:26 AM
Reedy changed the edit policy from "acl*security (Project)" to "All Users".
DannyS712 closed subtask Restricted Task as Resolved.Dec 18 2020, 1:35 AM
Reedy claimed this task.