Repository navigation
Node.js 8.0.0 Tracking Issue #10117
Description
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.
Reacted by Sergey Rubanov, Sveinung Tord Røsaker, Gibson Fahnestock, Benjamin Lupton, Robert Rossmann, Bazyli Brzóska (Zendesk), therealkenc, Mathieu M-Gosselin, coderaiser, Lukas Kollmer and 14 more
Activity
targos commentedon Dec 5, 2016
We could also try to use a Github project?
jasnell commentedon Dec 5, 2016
Trott commentedon Dec 5, 2016
Probably need to add an issue for deprecating the current CLI debugger.
jasnell commentedon Dec 5, 2016
Ooh... Yeah, good idea. We will need the new stuff to come out of experimental at the same time the old debugger deprecates.
targos commentedon Dec 5, 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: #9789
Fishrock123 commentedon Dec 5, 2016
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.
Trott commentedon Dec 5, 2016
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 commentedon Dec 5, 2016
By the way, the debugger thing is on the CTC agenda this week, at least indirectly, as nodejs/CTC#40.
klimashkin commentedon Dec 5, 2016
@targos Is there a date when
8.0.0is going to be released?V5 5.7 will be around the beginning of March, 5.8 - middle of April
chicoxyzzy commentedon Dec 5, 2016
klimashkin commentedon Dec 5, 2016
So there is hope that nodejs release will wait for V8 5.8, as 7.0.0 did with 5.4
Fishrock123 commentedon Dec 5, 2016
Only if V8 5.8 comes out in April.
15 remaining items
jasnell commentedon Mar 27, 2017
ping @nodejs/build @nodejs/release ... see https://ci-release.nodejs.org/job/iojs+release/1593/nodes=vs2015-x86/console (/cc @jbergstroem)
jasnell commentedon Mar 27, 2017
Test build #2: https://nodejs.org/download/test/v8.0.0-test20170327db9805885fb817c5b36e5b2bb53b82c0765e438f/
joaocgreis commentedon Mar 28, 2017
@jasnell that looks like nodejs/v8#4, did that run with all the commits from #11752? I see 9c9e2d7 in
v8.x-stagingnow, if it was not when you run the job then that is expected.jasnell commentedon Mar 28, 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.
joaocgreis commentedon Mar 30, 2017
@jasnell there's a real issue here, tracking in nodejs/build#669 and nodejs/v8#4.
gordysc commentedon Apr 26, 2017
Both tickets in the above comment have been closed. Is there still outstanding issues?
iyobo commentedon Apr 27, 2017
@gordysc None! Release the Kraken! :D
skcc75 commentedon Apr 27, 2017
@gordysc @iyobo #12220 (comment)
vjeux commentedon May 9, 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
klimashkin commentedon May 9, 2017
@vjeux Yes, it was shipped in v8
5.8ConAntonakos commentedon May 16, 2017
https://v8project.blogspot.com/2017/05/launching-ignition-and-turbofan.html
bnoordhuis commentedon May 25, 2017
One for the release notes:
new Date(...)date parsing follows ES2015 behavior now:Refs #13210 and others.
jasnell commentedon May 30, 2017
Landed. Thank you all.