Those of us with modules that have dependencies on JQuery 1.3 are having to tell people "you have to use the dev release", which of course is error-prone.

Can we just get a 2.0 release? The module seems quite stable and does the job at this point. Further work can then go on in dev, and a 2.1 release.

Thanks for your work on this!

Comments

f1mishutka’s picture

f1mishutka commented

And 2.1-dev branch can introduce jQuery 1.4 ;)

vacilando’s picture

vacilando commented

Same problem - see this; subscribing.

frjo’s picture

frjo commented

I have this problem with the Colorbox module. I would very much like to see a stable 2.0 release.

markus_petrux’s picture

markus_petrux commented

+1

markus_petrux’s picture

markus_petrux commented
Title: Create 2.0 release » Create stable 2.0 release for jQuery Update

Better title when using the [#issue-number] macro from other projects.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Active » Fixed

Created 6.x-2.0-alpha1.

You won't get more until the known bugs are resolved:
http://drupal.org/project/issues/jquery_update?status=Open&version=409588

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

markus_petrux’s picture

markus_petrux commented
Status: Closed (fixed) » Active

I hate to do this, but I think alpha <> stable. Also, the 6.x-1.x branch is giving support to a Drupal core release that is not supported. I think the main release of jQuery Update module should really point to a version that covers the current Drupal core update. Current situation is still misleading.

To get to a stable release, I would propose to list all the issues that are critical to reach that point. None I can't think of. There are issues, yes, but I think they are not so critical to lock the module to reach a stable point that cover s 99% cases.

Let's deal with issue that are tested and reviewed by the community:

http://drupal.org/project/issues/jquery_update?text=&status=14&prioritie...

Next, please create a really stable release, so that 6.x-2.0 shows as the main stable release for this module. Please.

markhalliwell’s picture

markhalliwell
Primary language English
commented
Issue summary: View changes
Status: Active » Closed (outdated)

Drupal 6 reached EOL (end-of-life) on February 24, 2016.