Timeline for jquery migration from 1.2.6 to 1.7.x
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 2, 2012 at 14:39 | comment | added | ThiefMaster | So you are seriously suggestion to test something like this on a production system? On a development system you could simply update jQuery and test - no need for odd GET variables to select the jQuery version. | |
| Jul 2, 2012 at 14:38 | history | edited | Esailija | CC BY-SA 3.0 |
deleted 8 characters in body
|
| Jul 2, 2012 at 13:43 | comment | added | ZeeCoder | You should use something like: only use jQuery 1.7 when the GET var 'v'=="on" or something. Like this only you would use the page with the new version, for testing purposes. Or if you want to be absolutely certain, you can search for every command's possible compatibility issue, but that's really a lots of work to do. O.o | |
| Jul 2, 2012 at 13:39 | comment | added | Bora | Well, that is what I am attempting right now. The problem is, I cannot afford any problems when this goes live. | |
| Jul 2, 2012 at 13:37 | comment | added | ZeeCoder | That's what beta-versions are for I guess, but you are right. Anyway I still encourages keeping websites up-to-date with -let's say- the latest safe release. | |
| Jul 2, 2012 at 13:33 | comment | added | Anthony Grist | Higher version number doesn't necessarily mean less bugs; if the newer version has new features or functions, it could well introduce more bugs than it fixed. | |
| Jul 2, 2012 at 13:32 | history | answered | ZeeCoder | CC BY-SA 3.0 |