I like this 😄

A thought: Is perhaps process.release a bit redundant with process.config? I'm thinking it would be simpler if we just re-used that mechanism, since whatever's in config.gypi will be on that object during runtime (would make the changes in node.gyp and src/node.cc unnecessary).

We would just need to move the 3 URL props to the root-level of the config.gypi file, and add config.name = 'iojs' in the configure phase, so that it ends up in the config.gypi file as well.

@TooTallNate that's a good suggestion; I'm working my way through some node-gyp changes for this and that's the really difficult end so I'll loop back here when I have something working over there.

@rvagg is anything still holding this up?

Yes, I'm the holdup, we need to arrive on code that's acceptable to both node-gyp and io.js before we can land either.

The current state of code is @ https://github.com/rvagg/node-gyp/compare/iojs?expand=1 but it's pending proper Windows support, it's only part-way there. I'll try and get to it this week but if I keep finding that I just don't have time to finish it up I'll put out a call for someone else to take over.

Didn't I see windows gyp support land? Does that unblock this?

What is the status here? Anything you need help with @rvagg?

This is still blocking nodejs/node-gyp#564, which is in turn blocking npm from shipping a floating-patch free version of itself. Is there anything I can do to move this along, @rvagg?

@rvagg now that you're less busy, any chance of this landing soon? Seems like a few people depend on this.

..................................

@stevenvachon it'd be great if you avoided comments like these. Since a lot of people get pinged when new info arrives, we also assume that information will be beneficial to us. Thanks for understanding.

@jbergstroem and other comments merely asking for status updates shouldn't also be avoided?

@rvagg any progress here?

@rvagg wtfux?

@rvagg @TooTallNate @othiym23

I do dis ... it's becoming more and more urgent; I just have to squash a . few . more . things . from . my . TODO

Hmm, semver-minor.. no way to port this to 1.x then? It'd probably be worth it.

@Fishrock123 if the LTS working group wills it, I'm sure they can make it happen.

Looks good, when to merge?

Is this necessary anymore since http://www.infoq.com/news/2015/05/nodejs-iojs ?

Yes because 1) io.js still exists and is still releasing and has a patched version of node-gyp that you can't upgrade and more importantly 2) we need to support nightlies and rc builds with node-gyp and this metadata provides us with the flexibility to do so.

Succeeded by #2154