-
Notifications
You must be signed in to change notification settings - Fork 10.1k
When did 2.0 happen? #2946
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Ah I searched and found the History as well, but I mean that some sort of public announcement would also be nice in either the homepage, documentation or Github's README |
Well, I'm open to suggestions! What has already been done:
|
Hi, is there anything that needs to happen in order to upgrade 1.x to 2.0? I haven't seen any notes on upgrading other than 0.9. Is it just drop/replace? |
@tagyoureit besides upgrading your nodejs if you are still running 0.10/0.12 versions, I don't see anything particular to do. |
@darrachequesne is uws in there by default meaning we don't have to track it or add it somewhere? And is it still recommended to add bufferutils + utf8-validate? And at which versions, 2.x.x, or latest? |
You want to:
When did 2.0 happen? Is it stable? I cannot see neither in the homepage nor in the repository information about breaking changes or transition paths. What broke that was warrant a major bump?
I am also invested on 1.0 as I'm preparing to release
server
which relies on socket.io so I'd love to know these changes in the same way that there was a transition guide from 0.9 to 1.x. If there are no breaking changes I think the homepage or repo would be a good place to say so for people who worry (like myself).PS, I really love socket.io, great work!
The text was updated successfully, but these errors were encountered: