[Cubicweb] Upgrading CubicWeb's bundled jQuery ?

Aurélien Campéas aurelien.campeas at logilab.fr
Tue Apr 2 15:22:00 CEST 2013


Le 02/04/2013 15:14, Rémi Cardona a écrit :
[...]
>
> 1. Upgrade to 1.8.3. This looks like a safe upgrade. Its API is broadly
> compatible with the current (1.6.4). Though there have been a few
> removals, they are well documented in the upgrade guides[1][2] and it
> should be easy to spot and fix offending code.
>
> The options boil down to #1 and #2.
>
> #1 is definitely the conservative choice as the migration from 1.6.4
> seems very straightforward and should only require a few greps to make
> sure we're not using deprecated APIs. FTR, I have been running CubicWeb
> along with a full forge instance on 1.8.3 since December without any
> known issue.
>

+1 for me

> #2 (with the "migrate" plugin) is definitely more interesting as we get
> to dip our toes into 2.0 territory without loosing support for old IE
> versions. If the helper plugin does indeed work as intended, the porting
> work for us should be minimal and it buys us time to move to the new
> 1.9/2.0 API at our own pace.

That's cw 3.18 material imho.




More information about the Cubicweb mailing list