release a node 0.8 with an updated npm

[timoxley]

Maybe io.js is in a position to finally cut a simple bugfix release of node 0.8 that includes a functional version of npm. The version of npm bundled on 0.8 is incompatible with the current npm registry. nodejs/node-v0.x-archive#7797

Not sure how many people this would benefit as anyone affected has probably figured out a solution, and you don't want to encourage people to linger around on old versions, but perhaps it's something to consider as it could help io.js gain the trust of people who don't like to take risks.

Just a thought.

[cjihrig]

I'm -1 on this. My personal opinion is that 0.8 is joyent/node's baggage at this point.

[reqshark]

actually that would be really nice but a tad node backwardish.

[osslate]

My opinion: it's up to Joyent to release a version of 0.8 with a newer version of npm, io.js should stick to moving Node forward instead of lingering on older versions. It could be a separate project though?

[rvagg]

Technically I suspect this wouldn't be hard to pull off given an appropriate PR from the npm folk to shoehorn newer npm into the v0.8 branch. I just don't see the merit of it. If you are stuck on 0.8, how likely are you to accept a upgrade from a non-official source? My guess is that you're either super conservative or are using a stale node that comes with your distro, neither of these audiences are likely to download an upgrade from iojs.org.

[dougwilson]

I would like this, but it won't help the situation, i.m.o.. @rvagg puts it best:

If you are stuck on 0.8, how likely are you to accept a upgrade from a non-official source? My guess is that you're either super conservative or are using a stale node that comes with your distro, neither of these audiences are likely to download an upgrade from iojs.org.

If you were to release a new 0.8, maybe I could get systems updated, but with it not from Joyent, that pretty much goes to a "not happening".

Internally, we simply use [email protected] on 0.8 systems and it works just fine for us.

[kkoopa]

As we're past the 0.10 series, 0.8 should be retired. Releasing patches only prolongs the suffering.

[mgol]

Also, note that the io.js project couldn't release "Node.js 0.8.29" but only "io.js 0.8.29" or Joyent could go after the project. How many people would "upgrade" to a version of a differently named project? What would happen when Node.js 0.8.29 comes out later? This would most likely only increase confusion instead of resolving the problem.

[cjihrig]

It doesn't sound like this is likely to happen. If something changes, this can be reopened.