You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason will be displayed to describe this comment to others. Learn more.
No specific reason, just slowly moving everything up. I want to do a new release in a few weeks so we are going to get 0.9.5 up and I'm going to port all of node.js test suite over to this so we can make sure we are completely compliant.
The reason will be displayed to describe this comment to others. Learn more.
I've been tracking v0.9.6pre and using it in production without any noticeable problems, apart from the connect event not firing on the client when using namespaces, as described in #9
9cc50a0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any particular reason why v0.9.1 was imported, when the latest tagged version is v0.9.5 ?
9cc50a0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No specific reason, just slowly moving everything up. I want to do a new release in a few weeks so we are going to get 0.9.5 up and I'm going to port all of node.js test suite over to this so we can make sure we are completely compliant.
9cc50a0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've been tracking v0.9.6pre and using it in production without any noticeable problems, apart from the connect event not firing on the client when using namespaces, as described in #9