TL;DR: In April 2017, the jQuery library in MediaWiki was upgraded from 1.x
to 3.x (the current stable version), with the jQuery Migrate plugin enabled
ease migration. We temporarily still load jQuery 1.x on Wikimedia wikis.
Read about the API changes at https://jquery.com/upgrade-guide/3.0/
== Upgrade guide ==
An overview of the important changes is available at:
This page also contains advice on how to migrate your code. In most cases
it involves fairly
simple changes, such as using a different method name, or adding quotes in
The vast majority of the added requirements and removed methods are
the jQuery Migrate plugin with a deprecation warning in the console. As
such, it's unlikely
your code will require any immediate changes.
If you do find a deprecation warning in the console, you can use the
to find out more:
Once jQuery 3 is in Wikimedia production (with jQuery Migrate) it will be
find uses of deprecated methods with the deprecation warnings. However, you
need to wait for August to start migrating. The methods removed in jQuery 3
been deprecated for a while already, and their replacements are already
in jQuery 1.x in production, today.
== Timeline ==
* April 2017: jQuery 3 lands in MediaWiki core master with jQuery Migrate
* April to July 2017: Testing and fixing of issues arising from the switch.
* July 2017: jQuery 3 enabled in Wikimedia's Beta Cluster. 
* August 2017: jQuery 3 enabled on Wikimedia wikis in production.
jQuery 3 will also be released as part of MediaWiki 1.30.0 (expected in
November 2017). 
As part of MediaWiki 1.30, inclusion of jQuery Migrate will made
configurable so that sites
that have already migrated may disable the plugin for better run-time
Track progress at <https://phabricator.wikimedia.org/T124742>.
as an update on the changes I flagged last month:
there are still several articles that need to be fixed, including some on
We put a lot of explanations and details at mediawiki.org.
Among the most affected wikis:
*Arab, Russian, Ukrainian, Farsi, Serbo-Croatian Wikipedias...*
*What does "broken" look like?*
(infobox exposing syntax in view mode; you may need to purge the cache to
actually be able to see the issue live in some articles.)
*How to check and fix:*
See the *latest list *at https://www.mediawiki.org/wiki/Parsoid/Language_
conversion/Preprocessor_fixups/20170620 , then head to
fixups#How_to_fix for *instructions*. When actually necessary, fixes are
fast and easy (speaking for personal experience). False positives are
possible. Tools-assisted fixing is also possible (AutoWikiBrowser has been
used to that effect); please ask if you need assistance with that.
*A note about communications:*
Throughout the year, the Parsing team will make several changes that will
require kind community assistance. So far, the preprocessor one looks quite
successful, with several volunteers coming to the rescue (thanks again!).
There have been multiple mentions and updates in Tech News, emails, Village
Pump announcements, talk pages at mw.org, Phabricator... most fixes are
done, and the remaining fixes to be done do not justify additional
communication effort. As said before, other breaking changes will occur in
time (which may affect way more pages), and over-communicating risks to
distract and confuse helpful volunteers.
This means you are welcome to communicate with the team directly at
conversion/Preprocessor_fixups , but shouldn't expect any more nudges on
this specific project, as we prepare to communicate about others (and the
current workflow is probably too heavy and time-consuming to be applied to
each and every of such changes). If you have feedback about current and
future communications strategy, we are looking forward to hearing from you
---------- Forwarded message ----------
From: "Aaron Halfaker" <aaron.halfaker(a)gmail.com>
Date: Jun 12, 2017 12:00 PM
Subject: [AI] ORES operating at slightly reduced capacity
To: "Application of Artificial Intelligence and other advanced computing
strategies to Wikimedia Projects" <ai(a)lists.wikimedia.org>
One of our worker nodes in CODFW went down (scb2005). See
https://phabricator.wikimedia.org/T167638 for details.
This should not affect the service except that we'll have a slightly
reduced capacity to handle high request rates. Let us know if you see any
issues with ORES.
AI mailing list