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.gardaus...@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 (er...@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 >
