-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
doc: adding deprecations.md #11621
doc: adding deprecations.md #11621
Conversation
@italoacasas since this is a backport, you don't have to wait to merge into the v7.x-staging/proposal branches. |
Aside: I'm wondering if the intent above was to @-mention nodejs/collaborators rather than nodejs/collaboration. Is nodejs/collaboration active anymore? Might be good to remove (or else rename) to avoid this kind of confusion. I've certainly auto-completed to |
Yes, that was the intent, second time this happens to me xD... Landing this in 10m... |
PR-URL: nodejs#11621 Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Landed |
Marking as don't land on 4 and 6. |
Checklist
Affected core subsystem(s)
doc
This file doesn't exist in v7.x because every commit was a
semver-major
. Now we have an exception because the backport for thenode --debug
deprecation.The release for 7.7.0 is going to be delayed if we don't fast track this backport, since the build is failing because this other commit was included in staging already.
This backport is, in my opinion, the correct fix.
cc: @nodejs/collaboration