Name: Schema-change-in-production
Description: Database schema changes for WMF production wikis
Type of Project: Release is the closest, though schema changes don't necessarily coincide with MW releases if they can be disabled in config.
Policy: default
Description
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | None | T192655 Replace all "tracking" tasks with tags/projects (if unbounded), relabel them to outcome tasks (if bounded), or kill them entirely (if pointless) | |||
Resolved | None | T97412 replace schema change tracking task T51188 by project #blocked-on-schema-change |
Event Timeline
Comment Actions
Name: Database-Schema-Changes ?
As pointed out in T51188#1339454, Schema-change already exists. Wondering if that should become #MediaWiki-Schema-Change and this request #Wikimedia-Schema-Change ? But all together that's pretty confusing.
Better proposals very welcome here.
Comment Actions
Again: Better proposals very welcome here.
Until that happens, setting task status to "stalled".
Comment Actions
This task is stalled for more than one year. There's not much backlog in our workboard but maybe we can have a decision on this one?
Comment Actions
I'd love to see feedback from the DBA folks (as the project desc lists "Validating and executing schema changes") if they care (also in combination with Schema-change-in-production)