Hey all,
TL;DR: jQuery will soon be upgraded from v1.8.3 to v1.11.x (the latest). This
major release removes deprecated functionality. Please migrate away from this
deprecated functionality as soon as possible.
It's been a long time coming but we're now finally upgrading the jQuery package
that ships with MediaWiki.
We used to regularly upgrade jQuery in the past, but got stuck at v1.8 a couple
of years ago due to lack of time and concern about disruption. Because of this,
many developers have needed to work around bugs that were already fixed in later
versions of jQuery. Thankfully, jQuery v1.9 (and its v2 counterpart) has been
the first release in jQuery history that needed an upgrade guide[1][2]. It's a
major release that cleans up deprecated and dubious functionality.
Migration of existing code in extensions, gadgets, and user & site scripts
should be trivial (swapping one method for another, maybe with a slight change
to the parameters passed). This is all documented in the upgrade guide[1][2].
The upgrade guide may look scary (as it lists many of your favourite methods),
but they are mostly just addressing edge cases.
== Call to action ==
This is a call for you, to:
1) Get familiar with http://jquery.com/upgrade-guide/1.9/.
2) Start migrating your code.
jQuery v1.9 is about removing deprecated functionality. The new functionality is
already present in jQuery 1.8 or, in some cases, earlier.
3) Look out for deprecation warnings.
Once instrumentation has begun, using "?debug=true" will log jQuery deprecation
warnings to the console. Look for ones marked "JQMIGRATE" [7]. You might also
find deprecation notices from mediawiki.js, for more about those see the mail
from last October [8].
== Plan ==
1) Instrumentation and logging
The first phase is to instrument jQuery to work out all the areas which will
need work. I have started work on loading jQuery Migrate alongside the current
version of jQuery. I expect that to land in master this week [6], and roll out on
Wikimedia wikis the week after. This will enable you to detect usage of most
deprecated functionality through your browser console. Don't forget the upgrade
guide[1], as Migrate cannot detect everything.
2) Upgrade and Migrate
After this, the actual upgrade will take place, whilst Migrate stays. This
should not break anything since Migrate covers almost all functionality that
will be removed. The instrumentation and logging will remain during this phase;
the only effective change at this point is whatever jQuery didn't think was
worth covering in Migrate or were just one of many bug fixes.
3) Finalise upgrade
Finally, we will remove the migration plugin (both the Migrate compatibility
layer and its instrumentation). This will bring us to a clean version of latest
jQuery v1.x without compatibility hacks.
A rough timeline:
* 12 May 2014 (1.24wmf4 [9]): Phase 1 – Instrumentation and logging starts. This
will run for 4 weeks (until June 9).
* 19 May 2014 (1.24wmf5): Phase 2 – "Upgrade and Migrate". This will run for 3
weeks (upto June 9). The instrumentation continues during this period.
* 1 June 2014 (1.24wmf7) Finalise upgrade.
== FAQ ==
Q: The upgrade guide is for jQuery v1.9, what about jQuery v1.10 and v1.11?
A: Those are regular updates that only fix bugs and/or introduce non-breaking
enhancements. Like jQuery v1.7 and v1.8, we can upgrade to those without any
hassle. We'll be fast-forwarding straight from v1.8 to v1.11.
Q: What about the jQuery Migrate plugin?
A: jQuery developed a plugin that adds back some of the removed features (not
all, consult the upgrade guide[2] for details). It also logs usage of these to
the console.
Q: When will the upgrade happen?
A: In the next few weeks, once we are happy that the impact is reasonably low.
An update will be sent to wikitech-l just before this is done as a final reminder.
This will be well before the MediaWiki 1.24 branch point for extension authors
looking to maintain compatibility.
Q: When are we moving to jQuery v2.x?
A: We are not currently planing to do this. Despite the name, jQuery v2.x
doesn't contain any new features compared to jQuery v1 [3]. The main difference
is in the reduced support for different browsers and environments; most
noticeably, jQuery 2.x drops support for Internet Explorer 8 and below, which
MediaWiki is still supporting for now, and is outside the scope of this work.
Both v1 and v2 continue to enjoy simultaneous releases for bug fixes and new
features. For example, jQuery released v1.11 and v2.1 together[4][5].
-- Krinkle
[1] http://blog.jquery.com/2013/01/15/jquery-1-9-final-jquery-2-0-beta-migrate-
final-released/
[2] http://jquery.com/upgrade-guide/1.9/
[3] http://blog.jquery.com/2013/04/18/jquery-2-0-released/
[4] http://blog.jquery.com/2014/01/24/jquery-1-11-and-2-1-released/
[5] http://blog.jquery.com/2013/05/24/jquery-1-10-0-and-2-0-1-released/
[6] https://gerrit.wikimedia.org/r/131494
[7] https://github.com/jquery/jquery-migrate/blob/master/warnings.md
[8] http://www.mail-archive.com/[email protected]/msg72198.html
[9] https://www.mediawiki.org/wiki/MediaWiki_1.24/Roadmap
Adding wikitech-l
On Mon, Dec 1, 2014 at 2:59 PM, Greg Grossmeier <greg(a)wikimedia.org> wrote:
> tl;dr: Testing on deployment-salt (or other Beta
> Cluster/deployment-prep vms?): please watch out for "[LOCAL HACK]"
> commits and don't lose them.
>
>
> See:
> https://phabricator.wikimedia.org/T75947
>
> Basically: Some local puppet changes were committed on deployment-salt
> with "[LOCAL HACK]" in the summary (as is the practice to test/do
> things before they're merged in ops/puppet for a number of reasons,
> see: https://phabricator.wikimedia.org/T76392 for reducing that). They
> were, unfortunately lost somehow. Current theory is that someone
> accidentally clobbered them while doing their own testing.
>
> If it was you, no worries (Bryan's already fixed this specific case,
> thanks Bryan!) but please don't do it again. :)
>
> Feel free to talk with the QA mailing list if you have any questions
> on how to do testing of puppet changes in Beta Cluster:
> https://lists.wikimedia.org/mailman/listinfo/qa
>
> Best,
>
> Greg
>
> --
> Greg Grossmeier
> Release Team Manager
--
Greg Grossmeier
Release Team Manager
The original request behind Scribunto's mw.text.unstrip method was to undo
<nowiki> tags, as a mechanism for quoting arguments being passed into a
module. But the implementation was more broad, allowing access to the HTML
generated by the <ref> and <references> tags, by special page transclusion,
and so on. This caused problems such as T63268.[1]
With the merge of Gerrit change 171290,[2] the mw.text.unstrip method will
unstrip nowiki strip markers and will replace all other strip markers with
the empty string. A new method mw.text.unstripNoWiki is also provided to
unstrip nowiki markers while leaving other markers in place, and
mw.text.killMarkers to remove all strip markers from a string.
Modules using mw.text.unstrip should be checked to ensure they don't break
with this change. A list of modules on WMF wikis including the string
"unstrip" is at https://test.wikipedia.org/wiki/User:Jackmcbarn/unstrip.
See https://www.mediawiki.org/wiki/MediaWiki_1.25/Roadmap for the
deployment schedule.
[1]: https://phabricator.wikimedia.org/T63268
[2]: https://gerrit.wikimedia.org/r/#/c/171290/
--
Brad Jorsch (Anomie)
Software Engineer
Wikimedia Foundation
Google Code-in 2014 has started a few hours ago and the first Wikimedia
tasks got claimed and being worked on by students (one task already has
a patch in Gerrit)! GCI will run until January 19. Students are eager
and tasks get claimed quickly.
If you have not become a mentor yet:
WE WANT YOU TO BECOME A MENTOR AND ADD MORE TASKS!
* Provide 3 easy Phab tasks in your area that you could mentor
* OR: provide an easy clonable task (a type of task that is
generic and could be repeated many times - for example, Language
Engineering has several GCI tasks to write a help page for one
uncovered input method in ULS and the student has to choose and
mention the one input method s/he's going to work on)
* The tasks must include instructions and point to documentation
* You commit to answer to students' questions and to evaluate
their work within 36 hours (the better your task description the
less questions you get. And no worries, we're there to help you!)
Please check out
https://www.mediawiki.org/wiki/Google_Code-in_2014#Mentors.27_corner -
Don't hesitate to ask questions if something is unclear!
Thank you for giving young contributors the opportunity to learn about
and work on Free and Open Source Software projects!
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
As noted in the server admin log [1], Phabricator is currently down due to
a network outage impacting one of our racks in the Ashburn data-center.
We're investigating and will aim to restore service ASAP.
Erik
[1] https://wikitech.wikimedia.org/wiki/Server_Admin_Log
--
Erik Möller
VP of Product & Strategy, Wikimedia Foundation
Google Code-in 2014 has started a few hours ago and the first Wikimedia
tasks got claimed and being worked on by students! GCI will run until
January 19. Students are eager and tasks get claimed quickly.
If you have not become a mentor yet:
WE WANT YOU TO BECOME A MENTOR AND ADD MORE TASKS!
* Provide 3 easy Phab tasks in your area that you could mentor
* OR: provide an easy clonable task (a type of task that is
generic and could be repeated many times - for example, Language
Engineering has several GCI tasks to write a help page for one
uncovered input method in ULS and the student has to choose and
mention the one input method s/he's going to work on)
* The tasks must include instructions and point to documentation
* You commit to answer to students' questions and to evaluate
their work within 36 hours (the better your task description the
less questions you get. And no worries, we're there to help you!
)
Please check out
https://www.mediawiki.org/wiki/Google_Code-in_2014#Mentors.27_corner -
Don't hesitate to ask questions if something is unclear!
Thank you for giving young contributors the opportunity to learn about
and work on Free and Open Source Software projects!
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
Wikimedia is planning to participate in Google Summer of Code 2015 and the
simultaneous FOSS Outreach Program for Women round 10. We want to increase
geographical diversity among candidates by involving local Wikimedia groups
in the promotion of these programs. This, in turn, could help increasing
the technical capacity of these groups. Interested? Please check
Connect Wikimedia groups, Google Developer Groups, and computer science
university departments
https://phabricator.wikimedia.org/T925
Italy, Russia, China, and Japan have been mentioned already. Adding other
locations is up to you. We are looking for local drivers. The Engineering
Community team and others can help from a distance, but this won't work
without local promoters.
PS: you can register to Phabricator with your Wikimedia account, and you
can subscribe to tasks in order to receive updates -- see
https://www.mediawiki.org/wiki/Phabricator/Help
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Hello all,
I would like to announce the release of MediaWiki Language Extension
Bundle 2014.11. This bundle is compatible with MediaWiki 1.23.7 and
MediaWiki 1.24.0 releases. It should also work with 1.22.14 but we no
longer test against it.
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.11.tar…
* sha256sum: 39b397a05561f743962cfb499f59a58219338607ea13ebfcc7a8806105e7dedc
Quick links:
* Installation instructions are at: https://www.mediawiki.org/wiki/MLEB
* Announcements of new releases will be posted to a mailing list:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
* Report bugs to: https://phabricator.wikimedia.org/
* Talk with us at: #mediawiki-i18n @ Freenode
Release notes for each extension are below.
-- Kartik Mistry
== Babel, CleanChanges and LocalisationUpdate ==
* Only localisation updates.
== CLDR ==
* Fixed some time displays if CLDR had only partial localisation of time units.
== Translate ==
* Translate WebAPI documentation is now localized. Only works in
MediaWiki 1.24 and newer.
* Fixed a bug which prevented bootstrapping of shared TTMServer
database with the ElasticSearch backend.
* If you are using the '''Solr backend '''for the translation memory
or the translation search, please let us know. If there are no users
for the Solr backend, we will deprecate and later remove it in favor
of the better maintained ElasticSearch backend.
== UniversalLanguageSelector ==
* ULS WebAPI documentation is now localized. Only works in MediaWiki
1.24 and newer.
* T67516: Removed font-size for ULS language selection panel buttons,
which caused tiny font sizes on the Monobook skin.
* Small compatibility fix when both ULS and VisualEditor are in use.
* About 20 new languages are now supported in the language selector
and a couple language names were changes.
* A JavaScript error no longer happens on pages without any headings.
* Added support for WOFF2 webfont format. Note that there are no WOFF2
webfonts in the font repository yet due to pending issues in WOFF2
font generation.
Thanks!
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com