Last modified: 2013-11-15 19:16:02 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 53865 - Review and deploy BetaFeatures extension
Review and deploy BetaFeatures 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: 56133 56140 56333
Blocks: 31235 wmf-deployment 56177
  Show dependency treegraph
Reported: 2013-09-06 21:47 UTC by Mark Holmquist
Modified: 2013-11-15 19:16 UTC (History)
9 users (show)

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


Description Mark Holmquist 2013-09-06 21:47:09 UTC
The Multimedia team has come up with this framework, wrapped in an extension, for experimental features. It's part of our rollout plan to get it on test2 and, so we can also start deploying extensions that use its framework.

VisualEditor, Multimedia, Mobile, and E2 are all planning on using this framework in the coming quarter to gate features they aren't ready to release on an opt-out basis.

Please review for security and performance (in particular the update jobs for user counts may be tricky for the latter) and add it to the extensions enabled on and test2.

Comment 1 Greg Grossmeier 2013-09-06 22:41:19 UTC
Hello, this is a quasi-automated-but-not-really message:

I am reviewing all tracking bugs for extensions to review and deploy to WMF servers. See the list here:

The [[mw:Review queue]] page lists the steps necessary to complete the review. I have copied them below and done some initial filling out based on what I can easily gleen from this bug and any linked to sources that are obvious. If I miss something/state something false, please do correct me.

Also, if you haven't yet done so, please review the information on and linked to from:

== TODO/Check list ==
Extension page on yes 
Bugzilla component: yes
Extension in Gerrit: yes
Design Review: yes
Archeticecture/Performance Review: no
Security Review: no
Screencast (if applicable): no
Community support: I believe so
Comment 2 Mark Holmquist 2013-09-20 18:54:04 UTC
Reedy did architecture/performance review. Chris will be doing security review sometime early next week. Design review is being finalized as we speak.

We'll be rolling this out in tandem with a bunch of other changes, so the deployment won't happen right away, and it will happen in stages (like Notifications, basically).
Comment 3 Mark Holmquist 2013-09-23 23:27:18 UTC
Design review is done - security review only remaining review.

== TODO/Check list ==
Extension page on yes 
Bugzilla component: yes
Extension in Gerrit: yes
Design Review: yes
Archeticecture/Performance Review: yes
Security Review: no
Screencast (if applicable): N/A
Community support: I believe so
Comment 4 Mark Holmquist 2013-09-25 20:03:10 UTC
Security fixes in should close the review portion of this bug - ready for deployment.

We'll discuss deployment strategy after that patch is merged and we have a better idea of what we want out of it.
Comment 5 Mark Holmquist 2013-10-28 17:08:07 UTC
Adding dependencies - we're not deploying BF until the three listed extensions are also deployable. We're hoping that'll happen by Thursday morning.

Comment 6 Mark Holmquist 2013-10-31 00:15:59 UTC
Ready to deploy.
Comment 7 MZMcBride 2013-11-15 05:35:19 UTC
Why is this bug marked fixed?
Comment 8 Bartosz Dziewoński 2013-11-15 09:55:14 UTC
Because this was supposed to happen yesterday, but the servers crapped themselves. I think the new deployment date is Monday.
Comment 9 Mark Holmquist 2013-11-15 19:16:02 UTC
We deployed to already. We were trying to deploy VectorBeta yesterday, but as you said, it crapped out - hence, bug 55749 stays open but this one got closed (and should have been closed much earlier)

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