-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Documentation with breaking changes between version 6 to version 8 #14225
Comments
I think @Fishrock123 has handled these in the past. This seems like something for @nodejs/documentation |
Although there shouldn't be anymore breaking changes on the node side of things from now until v8.x goes LTS in October, I am not sure if we should wait until we see what version of V8 will be used in the first LTS release. While node core will be ABI compatible with the various V8 versions (5.9, 6.0, and possibly 6.1 now), I'm not sure if we traditionally document any V8 changes that may break userland (despite |
Yeah, previous discussion was to do this when Node 8 goes LTS. I can't remember which issue it was though. |
Now that Node 8 became the new LTS is there any update on that? |
Does Semver-Major section suffice? |
@vsemozhetbyt Thx, this is nice! I'm still seeing value to have a migration guide at least between LTS versions. |
@vsemozhetbyt if you're moving from Node 6 to Node 8, you actually need the list of semver-majors in v7.0.0 and v8.0.0: https://nodejs.org/en/blog/release/v7.0.0/#commits I agree we should publish a separate guide though. |
There is this document now, this seems sufficient. |
@arboreal84 looks like it's good for you, so I'll close this. |
Has the wiki moved? The link doesn't appear to work anymore |
@ColinWhitmarsh It is archived in https://github.com/nodejs/wiki-archive |
As a user of node I would like to see a document detailing breaking changes between node 6 and node 8, or, node 7 to node 8, such as this one (just for different versions).
The text was updated successfully, but these errors were encountered: