Clarify MediaWiki and WMF Backporting requests process with regard to Phabricator tasks
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	Aklapper
	Mar 2 2015, 1:28 PM

Description

Maybe this works, but it feels really messy and unclear to me.
Needs more investigation, filing this ticket so I don't forget.

Wiki-Release-Team project is archived (T88263) and handled by Release-Engineering-Team now.
We have T40865: [DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports] from Bugzilla times for WMF deployments.
We also have the project MediaWiki-Tarball-Backports.
Documentation (not sure if still up-to-date?): https://www.mediawiki.org/wiki/Backporting_fixes
SWAT request seem to work anyway, not even sure we need to keep/define a heavy process here.

Related Objects

Mentioned Here: T88263: Clean #Wiki-Release-Team project
T40865: [DO NOT USE] Next wmf deployment (tracking) [superseded by #WMF-Server-Backports]

Event Timeline

Aklapper created this task.Mar 2 2015, 1:28 PM

Aklapper claimed this task.

Aklapper raised the priority of this task from to Medium.

Aklapper updated the task description. (Show Details)

Aklapper added a project: ECT-March-2015.

Aklapper added subscribers: Aklapper, greg.

T40865 was closed as superseded by WMF-Server-Backports (though it only lists greg as watcher, not sure if that's "enough") and the docs are correct so this looks all clear enough to me now.

Clarify MediaWiki and WMF Backporting requests process with regard to Phabricator tasksClosed, ResolvedPublicActions

Description

Related Objects

Event Timeline

Clarify MediaWiki and WMF Backporting requests process with regard to Phabricator tasks
Closed, ResolvedPublic
Actions