On Wed, Sep 14, 2016 at 08:53:40PM +0200, Paul Gevers wrote: > Hi all, > > [I am aware that this has probably been discussed before, but I fail to > find the right discussion in the archive. Please point me to it if you > know where it is.] > > I am currently preparing for a new major upstream version of my package > cacti (which I hope will be able to meet the stretch freeze). Upstream > has already for a long time been using jquery, and I have been able to > use the Debian package as my dependency. The next major version "needs > to avoid jQueryUI 1.2 as it's currently a hot stinking mess."¹
Note that jQueryUI and jQuery are not the same thing. > AFAIUI due to the nature of how the javascript eco-system works, it is > not trivial to "follow" newer versions. Could you please let me know > what the roadmap² of the javascript maintainer team is for the jquery > package and to jquery related packages. I see there is a 3.0 version in > experimental, but it is unclear to the outside world (and to me) when > that will migrate to unstable. Should I instead prepare for a > convenience copy of jquery (and related scripts), which I would really > hate to do? My plan is to have jQuery 3.x in stretch. Didn't do it yet because ENOTIME. So I guess I will just upload the version in experimental -- which according to upstream, is backwards-compatible wrt 1.x, except support for IE8 and earlier -- to unstable, soon.
signature.asc
Description: PGP signature
-- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel