[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-devel-list
Subject:    Re: Plans for Node.js 6.x
From:       drago01 <drago01 () gmail ! com>
Date:       2016-05-01 15:59:46
Message-ID: CAMqY-FerK4U8iEMrN8RLfvSxxiVKNj2kCTiXV4mbDXX-Uveg3A () mail ! gmail ! com
[Download RAW message or body]

On Wed, Apr 27, 2016 at 4:00 AM, Stephen Gallagher <sgallagh@redhat.com> wrote:
> OK folks, it's Bad Decision Time.
>
> Today, Node.js 6.0 was released. This is a significant ABI-breaking release,
> which means there is no guarantee that existing modules will work with it at all.[1]
>
> Better still, Node.js 5.x is only going to be supported until sometime this
> summer, because they're aiming for the 6.x branch to become the new LTS in
> October[2]. This puts us in quite a bind.
>
> Fedora disallows major ABI changes in a stable release, so if Fedora 24 Final
> ships with Node.js 5.x, we will be stuck with maintaining it until Fedora 24 EOL

The whole thread is based on this wrong assumption. Quoting from the
update policy [1]:

"If upstream does not provide security fixes for a particular release,
and if backporting the fix would be impractical, then a package may be
rebased onto a version that upstream supports. The definition of
practicality is left to the judgment of FESCO and the packager. "

And from the discussion that seems to be the case here so I'd opt for

4) Leave 5.x in and once it becomes EOL and a security issues comes up
update to 6.x mid release. It would have had been tested in rawhide
(and possible COPR) in the meantime which would minimize the impact.

1: https://fedoraproject.org/wiki/Updates_Policy#Security_fixes
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

[prev in list] [next in list] [prev in thread] [next in thread]