node version support #8
Description
node's versioning scheme is even number of v0.xx are stable releases and odd are unstable or development tags
https://github.com/joyent/node/wiki/FAQ
So v0.8, v0.10, v0.12 series are stable
A v0.11.x is not necessarily compatible with v0.11.y
Along about v0.11.14 there was a state of flux as the v8 engine and API went through massive changes where methods changed completely without a deprecation period as in still available but planned to be removed. It was the harmony [good] changes; the changes that altered the callback style of node and brought along features such as generators and promises and ES6 javascript. Any code written toward any node version from then on had the choice of being incompatible with older versions or as many did, used a macro system to deal with the differences as accomplished in nan https://github.com/nodejs/nan. Or dependent native projects make a branch and maintain only what was functioning at the time for legacy node versions
While building prebuilts with nodejs v0.12.7 they get labeled v14 in S3; not sure why.
Using nan does hold the code to a common denominator; a legacy branch written for v0.10 would be maintainable and free the v0.12 compatible trunk and beyond to explore the full power of the harmony features in v8(ES6)