eg http://twitter.com/#!/search/nodejs%20unstable
Though I know about the even/odd thing, it seems rather damaging to the platform to be announcing 'unstable' seemingly 'major' releases, don't you think? Why not Alpha? or Beta? or some other common convention? Ugh.
Many server systems use this convention as a way of embedding an extra bit of info (stable/unstable) for sys admins.
Many people are using Node to push boundaries in various ways, so they are using the unstable versions. I did this with 0.3, but 0.4 is good enough for the moment.
0.4 branch is and should be stable, meaning we can build on it and they'll try not to make big changes that could break what you built.
0.5 branch is unstable in the sense anything could change, even features added in 0.4 or older although they'll need compelling reasons to do that.
- add os.getNetworkInterfaces()
- add remoteAddress and remotePort for client TCP connections
I've been waiting for them to push these features out. (yes, I know you already have the address & port if you are a client).
https://github.com/felixge/node-nix
However, you need to know what you are doing, otherwise you'll have multiple processes draining the same file descriptors which will give you some nice surprises : )
