On Tue, Jul 12, 2016 at 10:17:23PM +0200, Jérémy Lal wrote:
> Hi,
> 
> 2016-07-12 11:06 GMT+02:00 Moritz Muehlenhoff <j...@debian.org>:
> 
> > On Tue, Apr 26, 2016 at 11:32:54PM +0200, Jérémy Lal wrote:
> > > Update:
> > > https://nodejs.org/en/blog/announcements/v6-release
> > > """
> > > In October 2016, Node.js v6 will become the LTS release and the LTS
> > release
> > > line (version 4)
> > > will go under maintenance mode in April 2017, meaning only critical bugs,
> > > critical security
> > > fixes and documentation updates will be permitted.
> > > Users should begin transitioning from v4 to v6 in October when v6 goes
> > into
> > > LTS.
> > > """
> > >
> > > I guess it will be too late for next debian release - still, it's good to
> > > know.
> >
> > With the delayed freeze for jessie that would be doable again, right?
> > The nodejs LTS is more volatile than a traditional LTS (also including
> > bugfixes etc), but that seems ok (and is in line with e.g. security
> > support for Firefox ESR).
> >
> > If we include nodejs 6 with security support in jessie we would limit
> > it to the lifetime of that LTS branch. Is is already known how long
> > that will be?
> 
> The schedule [here](https://github.com/nodejs/LTS) states 2019-04-01
> for the end of LTS 6 branch.

To loop back to this; since 6.x didn't make it into stretch, nodejs
will need to be unsupported security-wise as we did for jessie.

Cheers,
        Moritz

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Reply via email to