Comments

elachlan’s picture

Issue summary:View changes

Added another issue

quicksketch’s picture

Title:[Meta] - 7.x-1.14 Release Issues» [Meta] - 7.x-1.15 Release Issues
Issue summary:View changes

We've got a pretty serious problem with a lack of jQuery 1.9+ compatibility (#2124457: compatibility of jquery >=1.9), so I'm going to make a 1.14 release to solve this problem.

quicksketch’s picture

Title:[Meta] - 7.x-1.15 Release Issues» [Meta] - 7.x-1.17 Release Issues

Actually to make it so D6 and D7 have the same release numbers, I've tagged the new release as 1.16 (skipping 1.14 and 1.15). The two branches had been feature equivalent, though recent changes have started going only into the 7 and 8 branches instead of 6/7/8 (which is fine, that's a lot of work); and having the versions line up indicates feature parity.

quicksketch’s picture

Doh, I realized there are several issues where changes were made *only* to D7, but apparently the intention was to port them to other branches later. I'm fine with moving to D6 as a maintenance-only branch, but I'm uncertain as to your intentions @elachlan. Are you trying to keep the D8 branch in sync as well? Or are you waiting to update the module all at once at some point?

elachlan’s picture

I haven't touched the D8 branch in a long time. It will probably have to be re-written due to so many of the changes being made in D8.

quicksketch’s picture

It will probably have to be re-written due to so many of the changes being made in D8.

Yep, understood. At this point it seems like it'd be best to leave as-is for the time being and potentially re-port again closer to release. Thanks for all your work on this module! :)