- 7.x-2.x contains code compatible with 7.x and jQuery 1.3
- 6.x-2.x contains code compatible with 6.x and jQuery 1.3
- 5.x-2.x contains code compatible with 5.x and jQuery 1.2.6
- 6.x-1.x contains code compatible with 6.x and jQuery 1.2.6
- 5.x-1.x contains code compatible with 5.x and jQuery ~1.1.x (can't remember)

Sorry, but it could have been so easy:

anything-3.x contains code compatible to jQuery 1.3
anything-2.x contains code compatible to jQuery 1.2.6
anything-1.x contains code compatible to jQuery ~1.1.x

I would like to change the current development release nodes before there are any official releases for jQuery 1.3.

Comments

mfer’s picture

mfer commented

I looked at that and completely agree that this is a mess.

But, I'm not sure about this.

anything-3.x contains code compatible to jQuery 1.3
anything-2.x contains code compatible to jQuery 1.2.6
anything-1.x contains code compatible to jQuery ~1.1.x

What happens when jQuery 2 comes out? Or, we get to jQuery 1.7.x?

I've started by unpublishing the 6.x-1.x development snapshot. We are working on the 2.x one now with jQuery 1.3.x. I'd like to release that soon but we have some stuff in other modules that needs to be cleaned up. It is usable, though.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented

What happens when jQuery 2 comes out? Or, we get to jQuery 1.7.x?

Well, it's simple: Just increase the major version.

The current mess is that the major versions changed this way:

1.x (for jQuery 1.1)
2.x (for jQuery 1.2.6)
1.x (for jQuery 1.2.6)
2.x (for jQuery 1.3 in D6 or?)
3.x (for jQuery 1.3 in D5 or?)

Like always, it boils down to the simple rule of thumb: Whenever a module introduces new features that are incompatible to the previous version, it should use a new major version.

Of course, the jquery_update module itself does not really introduce new features. However, the new jQuery library version it introduces is not completely compatible with 1.2.6.

I know many modules that explicitly direct users to download and use jQuery Update 2.x (because dependency on 1.2.6). Those installation instructions are completely broken if jQuery Update suddenly ships 2.x with jQuery 1.3.

Anything for jQuery 1.3 should use jquery_update x.x-3.x.

When there will be jQuery 1.3.5 or 1.4 or whatever new version that's incompatible with 1.3, jquery_update will up to 4.x.

robloach’s picture

robloach
he/him
commented

Although it might really mess up the Drupal.org release system, you could mimic what jQuery version you update to.

jQuery 1.1: jQuery Update 5.x-1.10, jQuery Update 5.x-1.11, jQuery Update 5.x-1.12, etc
jQuery 1.2.6: jQuery Update 6.x-1.260, jQuery Update 6.x-1.261, jQuery Update 6.x-1.262, jQuery Update 6.x-1.32, etc
jQuery 1.3.x: jQuery Update 7.x-1.320, jQuery Update 7.x-1.321, jQuery Update 7.x-1.322, etc

Probably wouldn't work at all, but would seem pretty neat.

jQuery x.y.z == jQuery Update a.b-x.yz

markhalliwell’s picture

markhalliwell
Primary language English
commented
Issue summary: View changes
Status: Active » Closed (won't fix)

This ship has sailed, long ago, and is no longer applicable. Never mind the fact there hasn't been any activity on this in 8 years...