In support of T191231: RFC: Abstract schemas and schema changes, CentralNotice should be migrated to using Abstract Schema
Description
Description
Details
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Convert to abstract schema | mediawiki/extensions/CentralNotice | master | +1 K -227 |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | Ladsgroup | T191231 RFC: Abstract schemas and schema changes | |||
Open | None | T259374 Convert extensions to using abstract schema | |||
Resolved | None | T261912 Convert WMF Deployed Extensions to Abstract Schema | |||
Resolved | Umherirrender | T271002 CentralNotice doesn't work with Postgres: ERROR: relation "cn_notices" does not exist | |||
Resolved | Umherirrender | T268539 Convert CentralNotice to AbstractSchema | |||
Resolved | Umherirrender | T310447 Standardise type for timestamp columns in CentralNotice extension |
Event Timeline
Comment Actions
Change 805233 had a related patch set uploaded (by Umherirrender; author: Umherirrender):
[mediawiki/extensions/CentralNotice@master] Convert to abstract schema
Comment Actions
Change 805233 merged by jenkins-bot:
[mediawiki/extensions/CentralNotice@master] Convert to abstract schema
Comment Actions
This is now landed in master but not wmf-deploy; I guess that's sufficient for this to count as Resolved?