Some thoughts from Ryan on node.js tracking future v8 releases

node.js v8 roadmap chats

[20:09] felixge: ryah_: is there any reason node is not on v8 3.2.x yet?
[20:11] ryah_: felixge: v0.4 is sticking with the 3.1 branch
[20:11] felixge: is that just to be cautious ?
[20:12] ryah_: felixge: just want to stay stable
[20:12] ryah_: we're going to start pegging node to v8 releases
[20:12] felixge: ryah_: ok. To put my own v8 into node.js, do I just copy it in there? Or do I need some patch?
[20:12] ryah_: and consequently chrome releases
[20:13] ryah_: v8 3.1 = chrome 11 = node 0.4
[20:13] ryah_: v8 3.2 = chrome 12 = node 0.6
[20:13] ryah_: you can just copy it in
[20:13] felixge: I'm wondering how that will work out if release cycles don't match up 
[20:13] felixge: (between node / chrome / v8 that is)
[20:14] felixge: I guess we would skip versions?
[20:14] ryah_: yeah
[20:14] ryah_: probably will too - i can't do a 6 week cycle