Last modified: 2014-08-09 18:24:48 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 65399 - (jqmigrate) Don't use deprecated features removed in jQuery 1.9 (tracking)
(jqmigrate)
Don't use deprecated features removed in jQuery 1.9 (tracking)
Status: NEW
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
wmf-deployment
All All
: High normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: tracking
Depends on: 69349 65400 65404 65428 65562 65666 65667 65804 66064 jqmigrate-$.browser 66520 66522 67356 68998 69350
Blocks: tracking 44740
  Show dependency treegraph
 
Reported: 2014-05-16 15:35 UTC by Krinkle
Modified: 2014-08-09 18:24 UTC (History)
5 users (show)

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


Attachments

Description Krinkle 2014-05-16 15:35:59 UTC
Tracking bug for reports of JQMIGRATE calls on Wikimedia wikis.
Comment 1 Krinkle 2014-05-19 15:26:06 UTC
Time line:

* 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.


http://www.mail-archive.com/wikitech-l@lists.wikimedia.org/msg75735.html


1.24wmf7 will be cut from master on May 30, so must be migrated before that.

https://www.mediawiki.org/wiki/MediaWiki_1.24/Roadmap#Deployment_schedule
Comment 2 Nemo 2014-05-23 08:07:29 UTC
Who/how to test the severity of e.g. bug 65666? We need to know how much jQuery 1.9 would break LQT.
Comment 3 James Forrester 2014-05-23 16:05:59 UTC
(In reply to Nemo from comment #2)
> Who/how to test the severity of e.g. bug 65666? We need to know how much
> jQuery 1.9 would break LQT.

On a test instance, pull Gerrit change #133719 for MW-core to test it.
Comment 4 Nemo 2014-05-23 16:08:39 UTC
(In reply to James Forrester from comment #3)
> On a test instance, pull Gerrit change #133719 for MW-core to test it.

Spiritosone. In case the "Who" part was unclear, I don't plan to set up a test instance for LQT.
Comment 5 James Forrester 2014-05-23 16:15:33 UTC
(In reply to Nemo from comment #4)
> (In reply to James Forrester from comment #3)
> > On a test instance, pull Gerrit change #133719 for MW-core to test it.
> 
> Spiritosone. In case the "Who" part was unclear, I don't plan to set up a
> test instance for LQT.

Then don't ask how when all you care about is 'who'. :-)
Comment 6 Nemo 2014-05-23 16:19:54 UTC
(In reply to James Forrester from comment #5)
> Then don't ask how when all you care about is 'who'. :-)

The "who" depends on the "how", so don't put words in my mouth.

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


Navigation
Links