documentation: publish a LTS recommendation for package.json engines semver

[mderazon]

Hi,

I am deploying Node on a PAAS that installs node runtime according to the engines field in package.json.

I was wondering what would be a good engines semver configuration for node & npm versions to make sure I get all the important updates while still staying on the LTS branch.

I think adding this to the documentation would be good.

For example, I can do something like

"engines" : {
    "node" : "4.x.x"
  },

Would that be right ?

10x

[bnoordhuis]

I'd narrow it to "4.2.x". 4.2 is the LTS branch.

[rvagg]

not really .. we're going to hit 4.3 soon thanks to the V8 backport

[jasnell]

Specifically, any v4.x greater than v4.2.0 is part of the "Argon" LTS.