On Wed, Sep 02, 2015 at 10:21:12PM +0200, Luca Bruno wrote:
> On Wednesday 02 September 2015 15:21:51 Debian FTP Masters wrote:
> > Version: 3.0.0~alpha1+dfsg-1
> > Description:
> >  libjs-jquery - JavaScript library for dynamic web applications
> > Changes:
> >  jquery (3.0.0~alpha1+dfsg-1) experimental; urgency=medium
> >  .
> >    * New upstream release. Includes:
> >      - the regular release (successor to jQuery 2.x) in
> >        /usr/share/javascript/jquery/
> >      - the "compat" branch (successor to jquery 1.x) in
> >        /usr/share/javascript/jquery-compat/
> I'm sorry if this was discussed before and I missed it, but...

There was no discussion yet, thanks for bringing it up.

> How is jquery3 compatibility wrt to previous releases?
> Will they break 1.x and 2.x compatibility in the future?

2.x and 1.x provide the same API. 2.x only supports modern/good
browsers, and 1.x retains compatibility with older/crappier browsers
such as IE8.

> MY fear is that shipping a single binary and just bumping the version could 
> (at some point) break a lot of legacy code needing 1.x or 2.x.

AIUI from the upstream documentation and announcements, most reasonable
code that works today with 1.x should not break with 2.x or 3.x, since
the only difference is browser support.

> Wouldn't be better to introduce separate packages for the two pre-3 branches 
> and the two post-3 branches, as to avoid surprises for the future?

In practice, the 2 active branches are released in lockstep and are
identical except for a very few details, so I don't see much of a point
in having separate, almost-identical packages. And given the above wrt
API compatibility, I also don't see a point in keeping the older
versions around.

Antonio Terceiro <terce...@debian.org>

Attachment: signature.asc
Description: Digital signature

Pkg-javascript-devel mailing list

Reply via email to