Last modified: 2013-11-15 19:20:20 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 56133 - Review and deploy CommonsMetadata extension
Review and deploy CommonsMetadata extension
Product: Wikimedia
Classification: Unclassified
Extension setup (Other open bugs)
All All
: High normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: 31235 wmf-deployment 53865 56140 56177
  Show dependency treegraph
Reported: 2013-10-24 22:50 UTC by Mark Holmquist
Modified: 2013-11-15 19:20 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Mark Holmquist 2013-10-24 22:50:19 UTC
Right, so.

Needed for to work (I'll file that bug in a sec)

All dev has happened in Gerrit already.

No design review necessary.


* Performance review
* Bugzilla component
* Security review

Anything else? I don't think so.
Comment 1 Mark Holmquist 2013-10-31 00:12:27 UTC
Ready for deployment.
Comment 2 MZMcBride 2013-11-15 05:36:00 UTC
Why is this bug marked fixed?
Comment 3 Andre Klapper 2013-11-15 10:45:21 UTC
(In reply to comment #2)
> Why is this bug marked fixed? I guess, but there's bug 53865 comment 8 contradicting.
Comment 4 Mark Holmquist 2013-11-15 19:20:20 UTC
Yeah, this is definitely deployed to the cluster, we're just slowly(ish) pushing it out to different wikis. It's at least on, meta, and commons. So, I closed the bug (like I did with BetaFeatures).

Note You need to log in before you can comment on or make changes to this bug.