-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
2018-10-30 Version 10.13.0 'Dubnium' (LTS) #23831
Conversation
@nodejs/release please lmk if you think we should include any changes in this release... we currently have a fairly decent backlog on staging, which I think includes semver-minor changes. While we could include them in this release it would arguably be against our LTS policy (as changes will not have been in a release for 2 weeks). We do not, afaik, have explicit policy around the initial LTS release... but have discussed in the past releasing only the bit flip to LTS rather than accompanying it with other changes |
I'm +1 on a release with minimal changes. We should include #23801 when it lands |
Test is failing because it needs to be aware of the new release // it's expected that future LTS release lines will have additional
// branches in here
if (versionParts[0] === '4' && versionParts[1] >= 2) {
assert.strictEqual(process.release.lts, 'Argon');
} else if (versionParts[0] === '6' && versionParts[1] >= 9) {
assert.strictEqual(process.release.lts, 'Boron');
} else if (versionParts[0] === '8' && versionParts[1] >= 9) {
assert.strictEqual(process.release.lts, 'Carbon');
} else {
assert.strictEqual(process.release.lts, undefined);
} Missing the else if for 10 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM once test is updated.
src/node_version.h
Outdated
#define NODE_VERSION_IS_LTS 0 | ||
#define NODE_VERSION_LTS_CODENAME "" | ||
#define NODE_VERSION_IS_LTS 1 | ||
#define NODE_VERSION_LTS_CODENAME "dubnium" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This codename is uppercased in Boron
and Carbon
. Is there a reason for a change to this naming pattern?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
3ef9e25
to
fe93064
Compare
@MylesBorins did you intend to rebase to |
fe93064
to
f336836
Compare
@cxreg I didn't, thanks for the due diligence |
Another change that should be included IMO: #23795 |
edit no notable changes… OK, this can be next time.maybe some ICU <3 ? in decreasing order of importance
Easily skip this one if ICU 63.1 lands:
|
Thank you for your work on this @MylesBorins ❤️ I also very much appreciate the precedent of "no changes" outside of a SemVer minor patch. Feels much tidier and provides a simple way to explain the change to people. |
@targos I've landed #23801 and am waiting to see what happens in #23795 @srl295 I'm going to push back on landing any of the changes you've outlined here. As we are keeping this release targeting to minimal changes. I'd like to see the changes above live in an 11.x release before landing them in LTS |
PR-URL: #23801 Fixes: #23796 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Matheus Marchini <[email protected]>
c97612a
to
80cd8f3
Compare
🎉 Thanks Node contributors and maintainers! 🎉 |
All the sub targets have internal parallelism, so no performance loss. Also `make` doesn't to a good enough job of combining the output streams, or eliminate races. PR-URL: #23733 Fixes: #22006 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Joyee Cheung <[email protected]> Reviewed-By: Matheus Marchini <[email protected]>
80cd8f3
to
dc2708a
Compare
updated with two more commits to fix known regressions. Kicking off one last round of CI CI: https://ci.nodejs.org/job/node-test-pull-request/18216/ |
Rebuilding OSX: https://ci.nodejs.org/job/node-test-commit-osx/22254/ |
This release marks the transition of Node.js 10.x into Long Term Support (LTS) with the codename 'Dubnium'. The 10.x release line now moves in to "Active LTS" and will remain so until April 2020. After that time it will move in to "Maintenance" until end of life in April 2021. Notable Changes: This release only includes minimal changes necessary to fix known regressions prior to LTS. PR-URL: #23831
dc2708a
to
ab4af08
Compare
This release marks the transition of Node.js 10.x into Long Term Support (LTS) with the codename 'Dubnium'. The 10.x release line now moves in to "Active LTS" and will remain so until April 2020. After that time it will move in to "Maintenance" until end of life in April 2021. Notable Changes: This release only includes minimal changes necessary to fix known regressions prior to LTS. PR-URL: nodejs#23831
🎉 🎉 🎉 |
Thanks @MylesBorins! I think you still need to add a |
Opened nodejs/nodejs-latest-linker#2 against the linker tool. |
I manually created https://nodejs.org/download/release/latest-dubnium/ but we still need to update the automation script |
latest-linker updated and deployed, thanks @richardlau for the code and @joshgav for the ping |
2018-10-30, Version 10.13.0 'Dubnium' (LTS), @MylesBorins
This release marks the transition of Node.js 10.x into Long Term
Support (LTS) with the codename 'Dubnium'. The 10.x release line
now moves in to "Active LTS" and will remain so until April 2020.
After that time it will move in to "Maintenance" until end of
life in April 2021.
Notable Changes
This release only includes minimal changes necessary to fix known regressions prior to LTS.
Commits
2ba6010082
] - buffer: fix crash for invalid index types (Anna Henningsen)2cd68be69d
] - build: spawnmake test-ci
with-j1
(Refael Ackermann) #237331003f4c975
] - deps: fix wrong default for v8 handle zapping (Refael Ackermann) #23801