Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 1
    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. Commented Jul 2, 2012 at 13:33
  • 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.
    – ZeeCoder
    Commented Jul 2, 2012 at 13:37
  • Well, that is what I am attempting right now. The problem is, I cannot afford any problems when this goes live.
    – Bora
    Commented Jul 2, 2012 at 13:39
  • 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
    – ZeeCoder
    Commented Jul 2, 2012 at 13:43
  • 1
    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. Commented Jul 2, 2012 at 14:39