You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Chris Brody <ch...@gmail.com> on 2019/09/09 15:36:36 UTC
Re: [DISCUSS] Node 6.x & 8.x Deprecation & Node 12.x Support
Here is my response to what looks like the original discussion on Node.js
versions 6 and 8:
Considering that the Apache Cordova maintainers do not even have enough
time resources to keep up with bugs and features on the current platform
stack versions, I find it ridiculous that we should even consider
maintaining support for old tool versions such as Node.js 8.
For example, I think migration of packages such as cordova-android to
fs-extra should only target Node.js 10(+)
https://github.com/apache/cordova-android/issues/781
On Thu, Apr 11, 2019 at 12:42 AM Jesse <pu...@gmail.com> wrote:
> There is an issue with the language in the blog post.
> Deprecation means that support will be removed in the future, we should
> deprecate now, and remove support somewhere down the road. The sooner the
> better for Node 6.x imho
>
>
> On Wed, Apr 10, 2019 at 8:17 PM Gedas Gardauskas <
> gedas.gardauskas@gmail.com>
> wrote:
>
> > +1
> >
> > I believe it is a good idea to hold out until December. Keeping in fact
> > that there is little time to take action right now (except informing the
> > user) and that we have released Cordova 9.0 not so long ago. Plus, the
> fact
> > that the Android and iOS new versions are coming later this year. As
> Bryan
> > said, I think, everything would line up nicely for the Cordova 10 release
> > in December.
> >
> >
> >
> > On April 10, 2019 at 16:42:45, Bryan Ellis (erisu@apache.org) wrote:
> >
> > I would like to start the discussion around Cordova's planning for
> > deprecating Node 6.x and Node 8.x as well as starting to support Node
> 12.x.
> >
> > Since Node 6.x is being deprecated by the end of this month, I am not
> > expecting drastic action.
> >
> > Additionally, Node 8.x is expected to be deprecated by December.
> >
> > IMO, we could hold out till December to deprecate both versions and just
> > warn users about our recommendation to upgrade in the meantime. These
> > notices and warnings can be added in April and September as a patch or
> > minor release.
> >
> > As a side note, I suspect Android Q's release (August?) and possible iOS
> > (Sept?) to be out before December. For a major release for these new
> > platforms, adding Node will fall in nicely.
> >
> > Blog Post PR: https://github.com/apache/cordova-docs/pull/965
> > GH Issue Ticket: https://github.com/apache/cordova/issues/79
> >
>
Re: [DISCUSS] Node 6.x & 8.x Deprecation & Node 12.x Support
Posted by Norman Breau <no...@normanbreau.com>.
For example, I think migration of packages such as cordova-android to
fs-extra should only target Node.js 10(+)
https://github.com/apache/cordova-android/issues/781
fs-extra supports >= Node 8, so I don't think not deprecating/dropping
node8 will be a blocker here.
There is an issue with the language in the blog post.
Deprecation means that support will be removed in the future, we should
deprecate now, and remove support somewhere down the road.
- Jesse
100% agree with this. Makes sense to add the deprecation notices now, so
that support can be removed in
the following major release.
On 2019-09-09 12:36 p.m., Chris Brody wrote:
> Here is my response to what looks like the original discussion on Node.js
> versions 6 and 8:
>
> Considering that the Apache Cordova maintainers do not even have enough
> time resources to keep up with bugs and features on the current platform
> stack versions, I find it ridiculous that we should even consider
> maintaining support for old tool versions such as Node.js 8.
>
> For example, I think migration of packages such as cordova-android to
> fs-extra should only target Node.js 10(+)
> https://github.com/apache/cordova-android/issues/781
>
> On Thu, Apr 11, 2019 at 12:42 AM Jesse <pu...@gmail.com> wrote:
>
>> There is an issue with the language in the blog post.
>> Deprecation means that support will be removed in the future, we should
>> deprecate now, and remove support somewhere down the road. The sooner the
>> better for Node 6.x imho
>>
>>
>> On Wed, Apr 10, 2019 at 8:17 PM Gedas Gardauskas <
>> gedas.gardauskas@gmail.com>
>> wrote:
>>
>>> +1
>>>
>>> I believe it is a good idea to hold out until December. Keeping in fact
>>> that there is little time to take action right now (except informing the
>>> user) and that we have released Cordova 9.0 not so long ago. Plus, the
>> fact
>>> that the Android and iOS new versions are coming later this year. As
>> Bryan
>>> said, I think, everything would line up nicely for the Cordova 10 release
>>> in December.
>>>
>>>
>>>
>>> On April 10, 2019 at 16:42:45, Bryan Ellis (erisu@apache.org) wrote:
>>>
>>> I would like to start the discussion around Cordova's planning for
>>> deprecating Node 6.x and Node 8.x as well as starting to support Node
>> 12.x.
>>> Since Node 6.x is being deprecated by the end of this month, I am not
>>> expecting drastic action.
>>>
>>> Additionally, Node 8.x is expected to be deprecated by December.
>>>
>>> IMO, we could hold out till December to deprecate both versions and just
>>> warn users about our recommendation to upgrade in the meantime. These
>>> notices and warnings can be added in April and September as a patch or
>>> minor release.
>>>
>>> As a side note, I suspect Android Q's release (August?) and possible iOS
>>> (Sept?) to be out before December. For a major release for these new
>>> platforms, adding Node will fall in nicely.
>>>
>>> Blog Post PR: https://github.com/apache/cordova-docs/pull/965
>>> GH Issue Ticket: https://github.com/apache/cordova/issues/79
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org