-
Notifications
You must be signed in to change notification settings - Fork 570
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
[Tracking] Node.js 11.0.0 Release #328
Comments
+1 |
+1. Chromium 70 is scheduled for Oct 16th so timing is perfect |
@targos ... what V8 version will that be? V8 7? |
EsModule 🎉 |
@jasnell Yes. That will be V8 7.0 |
@targos I thought we were at V8 release v6.6... |
Right now in 10.0.0 we are. This thread is discussing Node.js 11.0.0, however. We'll be at V87 by October. |
And this release will require OpenSSL 1.1.1 with TLS1.3 right? Given that it is out. |
Current state of OpenSSL 1.1.1 integration with Node.js is in nodejs/node#18770. It sounds like there are issues on the Node.js side supporting TLS1.3. |
Might as well get this kicked off as early as possible given that 10.0.0 is going out the door tomorrow.
I will do the 11.0.0 release in October.
I'm proposing Tuesday, October 23rd as the target release date, with October 1st as a target soft semver-major cut off date, and October 15th as a target hard semver-major cut off date ("soft" == this is what folks should be targeting for, "hard" == absolutely no semver-major's unless they're critical for the release).
This gives us one week to slip the release if absolutely necessary.
The text was updated successfully, but these errors were encountered: