It's still very early in the process, but this will be the issue that I use to track the issues and todo's around the Node.js 8.0.0 release that will land in April 2017. The current plan is to cut the v8.x branch off master in the first couple of weeks in March 2017 (just about 3 months from now). This issue will be updated periodically with the relevant todo's.
jasnell
All 40 comments
We could also try to use a Github project?
targos
on 5 Dec 2016
Perhaps. I'm not sure how that would be any different than the milestone,
however.
On Sun, Dec 4, 2016 at 9:29 PM Michaël Zasso notifications@github.com
wrote:
We could also try to use a Github project?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/nodejs/node/issues/10117#issuecomment-264771134, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAa2eSLEy7YB4K-hfxJuKkc93AWUMx_Tks5rE6EjgaJpZM4LDy9d
.
jasnell
on 5 Dec 2016
Probably need to add an issue for deprecating the current CLI debugger.
Trott
on 5 Dec 2016
Ooh... Yeah, good idea. We will need the new stuff to come out of experimental at the same time the old debugger deprecates.
jasnell
on 5 Dec 2016
Yeah this is very important because we will probably have V8 5.8 or 5.9 by the time of the release and the old debugging protocol is removed as of 5.7! See: https://github.com/nodejs/node/issues/9789
targos
on 5 Dec 2016
and the old debugging protocol is removed as of 5.7!
It would be nice if they could have, you know, given us a heads up specifically about that. Thanks V8 team. ðŸ˜
Guess we need to issue another semver-minor deprecation in node 7 and maybe 6 that everyone will hate.
Fishrock123
on 5 Dec 2016
It would be nice if they could have, you know, given us a heads up specifically about that. Thanks V8 team. ðŸ˜
The protocol has been deprecated in V8 for at least one year, and I think longer than that.
@ofrobots opened an issue in June to discuss getting off the deprecated protocol. I'm pretty sure he surfaced the issue before that too, but certainly at least since then.
Trott
on 5 Dec 2016
By the way, the debugger thing is on the CTC agenda this week, at least indirectly, as https://github.com/nodejs/CTC/issues/40.
Trott
on 5 Dec 2016
@targos Is there a date when 8.0.0 is going to be released?
V5 5.7 will be around the beginning of March, 5.8 - middle of April
klimashkin
on 5 Dec 2016
Node.js 8.0.0 release that will land in April 2017
chicoxyzzy
on 5 Dec 2016
So there is hope that nodejs release will wait for V8 5.8, as 7.0.0 did with 5.4
klimashkin
on 5 Dec 2016
Only if V8 5.8 comes out in April.
Fishrock123
on 5 Dec 2016
Extrapolating from the schedule, my non-official estimat is that V8 5.8 will go stable during the last week of April. My guesstimate is that Node 8.0.0 will ship on April 25. If we hold things, V8 5.8 may be possible in 8.0.0, but the schedule is too tight for comfort. I don't see a way to get V8 5.9 in though. @targos: perhaps you meant as a ABI compatible upgrade sometime after 8.0?
Re: the old debug protocol. This has been deprecated for at least 2 years – we just haven't done anything about it. I guess the fault is partially mine that I didn't make even more noise about the imminent deprecation. After chatting with the V8 team, they have agreed to delay the removal of the old debug protocol from V8 5.7 to V8 5.8. This should give us some deprecation breathing room if 8.0.0 ships with V8 5.7 instead of V8 5.8. Coming up with an API/ABI compatible patch to upgrade to 5.8/5.9 during the life of 8.x would be a lot more work though.
Regardless, as discussed in the collaborator summit, we will need to immediately start working on figuring out a path forward for the old debug protocol going away.
ofrobots
on 5 Dec 2016
The timing is going to depend largely on what kinds of breakage is expected in 5.8. Once the branch is cut in early March, the ability to land semver-major PRs will be cut significantly and will require CTC sign off (that's not an absolute rule, just the way that I'll be handling this release). If there are any breaking changes going into 5.8, they will be need to be reviewed carefully.
jasnell
on 5 Dec 2016
I don't see a way to get V8 5.9 in though. @targos: perhaps you meant as a ABI compatible upgrade sometime after 8.0?
No you're right. I just went too fast and looked at the Branch points schedule.
targos
on 5 Dec 2016
For the record: the legacy debugging JSON protocol has been deprecated for a very long time already. The reason it stayed functional until now is because there was no reasonable migration path away from it (aside from using the not-well-documented debug context). This has changed since v8-inspector finally landed in V8.
hashseed
on 21 Dec 2016
I'm trying to integrate V8 5.8 and it seems that vm.runInDebugContext is also compromised.
targos
on 6 Feb 2017
There is only 2 month left for Node 8.
Not sure that 5.5 for Node 7 still makes sense, anyway it's not LTS.
Maybe it's better to spend more effort on 5.8 and its new inspect api, community will happily wait for it : )
Imo
Anyway async in 5.5 is not so fast:
klimashkin
on 6 Feb 2017
@targos what do you mean by "compromised"? v8::Debug::GetDebugContext is deprecated but should still work.
hashseed
on 7 Feb 2017
@hashseed see https://github.com/nodejs/node/blob/master/src/node_contextify.cc#L262-L275. We are using v8::Debug::GetMirror.
I don't know if this is still needed or can be replaced by something else.
/cc @ofrobots @bnoordhuis
targos
on 7 Feb 2017
Hehehe... check out this: https://github.com/v8/node/commit/293fc84613293b350d35a04a84801661b8c29bd9
hashseed
on 7 Feb 2017
Three things that need to be worked out, at least two of which will likely come down to the CTC in my opinion:
- what's the CLI debugger story in v8.0.0 (I think Diagnostics has that worked out already)
- what to do about Buffer constructor and when (paging @ChALkeR)
- whether or not to go with the new error system as-is or if it needs modifications or what. My primary motivation at this time is realizing that all error messages are going to change and not being certain of the cost to the ecosystem vs. the benefit. See https://github.com/nodejs/node/pull/11220#issuecomment-279781389 and discussion that follows
Trott
on 14 Feb 2017
The v8.x and v8.x-staging branches have been cut.
I'm running the first test release build now (https://ci-release.nodejs.org/job/iojs+release/1575/). (Note: This test build does not have the release bit set... it is essentially a cut directly off master).
I will generate a new test build each week and will begin working on the release candidate process starting April 4th.
@nodejs/collaborators @nodejs/ctc ... please work on landing all semver-major commits that should go into Node.js 8.0.0 by April 4th.
jasnell
on 15 Mar 2017
New test build: https://ci-release.nodejs.org/job/iojs+release/1576
(the first run errored out because I'd forgotten that the REPLACEME tags needed to be replaced before running a release build (even for tests... that seems odd)
jasnell
on 16 Mar 2017
Test build #2: https://ci-release.nodejs.org/job/iojs+release/1593/
jasnell
on 27 Mar 2017
@jasnell this page is not public? I get "Access Denied".
targos
on 27 Mar 2017
It's on the release ci so only release team members have access.
jasnell
on 27 Mar 2017
ping @nodejs/build @nodejs/release ... see https://ci-release.nodejs.org/job/iojs+release/1593/nodes=vs2015-x86/console (/cc @jbergstroem)
jasnell
on 27 Mar 2017
Test build #2: https://nodejs.org/download/test/v8.0.0-test20170327db9805885fb817c5b36e5b2bb53b82c0765e438f/
jasnell
on 27 Mar 2017
@jasnell that looks like https://github.com/nodejs/v8/issues/4, did that run with all the commits from https://github.com/nodejs/node/pull/11752? I see https://github.com/nodejs/node/commit/9c9e2d7f4a576310eb652a620db090f00a320243 in v8.x-staging now, if it was not when you run the job then that is expected.
joaocgreis
on 28 Mar 2017
@joaocgreis ... ok. I'll be running another test build tomorrow and will be syncing v8.x-staging and v8.x with master before I run.
jasnell
on 28 Mar 2017
@jasnell there's a real issue here, tracking in https://github.com/nodejs/build/issues/669 and https://github.com/nodejs/v8/issues/4.
joaocgreis
on 31 Mar 2017
Both tickets in the above comment have been closed. Is there still outstanding issues?
gordysc
on 27 Apr 2017
@gordysc None! Release the Kraken! :D
iyobo
on 27 Apr 2017
@gordysc @iyobo https://github.com/nodejs/node/pull/12220#issuecomment-294511442
kyrylkov
on 27 Apr 2017
Sorry if this is the wrong place but is node 8 going to have support for trailing commas for function calls? Here's the commit on v8 that implements it: https://bugs.chromium.org/p/v8/issues/detail?id=5051
vjeux
on 10 May 2017
@vjeux Yes, it was shipped in v8 5.8
klimashkin
on 10 May 2017
ConAntonakos
on 17 May 2017
One for the release notes: new Date(...) date parsing follows ES2015 behavior now:
When the time zone offset is absent, date-only forms are interpreted as a UTC time and date-time forms are interpreted as a local time.
Refs #13210 and others.
bnoordhuis
on 25 May 2017
Landed. Thank you all.
jasnell
on 30 May 2017
Related issues
willnwhite
·
3Comments
cong88
·
3Comments
filipesilvaa
·
3Comments
Brekmister
·
3Comments
srl295
·
3Comments
Most helpful comment
Landed. Thank you all.