-
Notifications
You must be signed in to change notification settings - Fork 577
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
Track backport of v8_inspector #109
Comments
The inspector seems awfully large for a backport, are we sure we want to be doing this? What will our messaging look like? This is a very sizable feature. Doesn't feel very lts-y at all. |
v6.x is not LTS yet. I don't think this issue is necessary at this point. We should track inspector support like everything else we merge into Current. EDIT: typo. |
Well I don't think we're going to need to do any backporting other than master -> v6.x but having a list of commits might be helpful if we end up having to back it out prior to v6 LTS for whatever reason. |
everything has been backported |
This issue is to track all commits that will be needed to track the backport of nodejs/node#6792
Other PR's that will need to be backported too
nodejs/node#7070
nodejs/node#7078
nodejs/node#7118
nodejs/node#7212
nodejs/node#7228
nodejs/node#7232
nodejs/node#7248
nodejs/node#7258
Should we make a temporary label to track these issues?
/cc @ofrobots
The text was updated successfully, but these errors were encountered: