Dropping support for Node v0.10 and v0.12

[mbaj...@gmail.com]

Hello LoopBack users,

As most of you are probably already aware, the support for Node v0.10 will end at the end of this month (October 2016) and the support for Node v0.12 will be dropped at the end of this year.

As the date gets closer, more and more LoopBack dependencies are dropping support for Node v0.10, which makes it increasingly difficult for us to keep supporting this Node version.

We started to discuss when and how to drop support for Node v0.10 and v0.12 in LoopBack on GitHub, see

https://github.com/strongloop/loopback/issues/2807

The most important questions we don't have a good answer:

 - How many people are still using LoopBack on Node v0.10 and would be affected by this change? How about Node v0.12? 

 - Would anybody mind if we drop support for Node v0.10 from LoopBack 3.0, which is already in a release-candidate state and was published as "loop...@3.0.0" to npmjs.org? (This will effectively break semver rules.)

 - Can we drop support for Node v0.12 now too, even though this version will be supported for another two months?

Please join the discussion on GitHub and help us to find a solution that would work best for both LoopBack users and project maintainers.

Thank you.

Miroslav

LoopBack.io Tech Lead