Last modified: 2014-07-08 07:42:57 UTC
Which "test wikis" specifically?
"Test wikis" typically means the phase 0 wikis these days, I think. That's four wikis: testwiki, test2wiki, mediawikiwiki, and testwikidata. Probably makes sense to make this change on those four or tweak the bug summary. :-)
What are the default settings for the production wikis?
Indeed, it is not currently overridden in wmf-config:
Change 139569 had a related patch set uploaded by Withoutaname:
Gadget authors have not yet been given a fair chance to migrate their scripts. Disabling this now will needlessly upset users and break actively deployed user applications on mediawiki.org. Given the complex nature of our user scripts (cross-loading from different wikis), we'll definitely need a phase where these emit deprecation notices so that developers have the chance of migrating their scripts *before* we boldly remove it hoping they'll quickly fix it. That's counting on breakage as the means to communicate change and I dont like that.
Right now we have about a dozen other highly visible migrations going on in the front-end. These legacy globals is not one of them. They haven't been announced very publicly, have no deprecation warnings for developers either.
They're also cheap to maintain compatibility for. I wouldn't prioritise pushing for the removal of these in the current MediaWiki release cycle.
Those comments were intended for bug 33837.
I think disabling it anywhere is ahead of the curve right now (we should do announcements and deprecation first), and that curve has not yet started due to other priorities right now.
However if users themselves are volunteering to test on testwikis, I think disabling this on test2wiki only would be fine. We do the same currently for the jQuery Migration (although that has already gone through announcements and deprecation warnings first).
Change 139569 merged by jenkins-bot: