-
Notifications
You must be signed in to change notification settings - Fork 568
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
npm update for 0.12 #143
Comments
We certainly could. Is that by itself enough to justify a new release of v0.10 tho? |
I'm not sure its worth it for 0.10.X. Its been the way it is for a long time and 0.10.x should only be in use for a few more weeks. |
That's 0.10 in the blue there not doing a very good job at dying, unlike 0.12. It's going to be used a lot longer than that, particularly given that it's included in some Linux distros that will live for a long time. I'd argue that getting a release out with a correct license is the responsible thing to do with a release line that folks are already having a hard time considering giving up on. |
I'd be up for putting together a 0.10 and 0.12 release including the npm On Sat, Oct 15, 2016, 12:47 AM Rod Vagg [email protected] wrote:
|
@thealphanerd I think we should still stick to our process of not bundling non-trivial and non-build things with security releases so this would actually mean two releases, one for c-ares and one for npm |
It was decided on today's call that @Fishrock123 would backport to v0.12 and that we would have a no-op for 0.10 this issue should be closed when the PR is opened, I am going to edit the title to reflect the current state of things |
Sorry I couldn't be there this time. Can you explain what no-op for 0.10 means? |
0.10 is EOL so we are not going to another release in any official capacity. (with or without updated npm) |
@ErisDS yeah, sorry for the poor choice of wording there. We will not be doing another 0.10 release is what I meant to say |
Closing, moving to the PR: nodejs/node#9619 |
Refs: nodejs/Release#143 PR-URL: nodejs#9619 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rod Vagg <[email protected]>
Refs: nodejs/Release#143 PR-URL: nodejs/node#9619 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rod Vagg <[email protected]>
As per nodejs/node#8928, thanks to @ChALkeR for the ping. The LICENSE is finally updated in npm@2, it might be appropriate for us to ship this in both 0.10 and 0.12 since we're still shipping the old, problematic license. Thoughts @nodejs/lts?
The text was updated successfully, but these errors were encountered: