Skip to content
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

Upgrade to V8 v4.9 #5926

Closed
lewispham opened this issue Mar 27, 2016 · 5 comments
Closed

Upgrade to V8 v4.9 #5926

lewispham opened this issue Mar 27, 2016 · 5 comments
Labels
question Issues that look for answers. v8 engine Issues and PRs related to the V8 dependency.

Comments

@lewispham
Copy link

I'm not sure about the reasons behind this delay. It's been a long time since version v4.6. Please give me some information about the next upgrade of V8. I'll appreciate that.

@bnoordhuis
Copy link
Member

We expect to ship node.js v6 with V8 5.0. The V8 version in the current stable and LTS branches won't be upgraded because of API/ABI backwards compatibility issues.

@bnoordhuis bnoordhuis added question Issues that look for answers. v8 engine Issues and PRs related to the V8 dependency. labels Mar 27, 2016
@lewispham
Copy link
Author

What about the delay? It's just about this upgrade or the strategy has changed? Why doesn't Nodejs upgrade V8 as soons as possible, just like what it used to do?

@bnoordhuis
Copy link
Member

We don't upgrade (only bug-fix) in release lines when it would break the API or the ABI, because that forces everyone to recompile (ABI) or rewrite (API) their native add-ons. With V8, that almost always means you're stuck with a particular version because it changes quite a bit between releases.

Why doesn't Nodejs upgrade V8 as soons as possible, just like what it used to do?

Perhaps you mean io.js? Node.js from before the merger was rather infamous for shipping outdated versions from day zero, never mind upgrades.

Take v0.10: it's still using V8 3.14, last update over three years ago. When v0.10.0 was released, that version of V8 had already been abandoned by upstream for a few months.

@lewispham
Copy link
Author

Perhaps you mean io.js?

No. I meant the converged version (Nodejs v4+). You can see the change log for more details. It says:

It can be clearly seen that there is no V8 upgrade since 2015-11-17. You can do the math then compare it with the others. That's why I filed this issue and asked for a reason.

If you have no idea about the causes of the delay, please reopen this issue.

@cjihrig
Copy link
Contributor

cjihrig commented Mar 27, 2016

There are a number of V8 related backports after 2015-11-17, but no version updates because, as @bnoordhuis pointed out, they would be breaking changes. We are still updating V8 (for example see #5494), but it won't be in a release until v6 comes out in April. This is part of the LTS schedule.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Issues that look for answers. v8 engine Issues and PRs related to the V8 dependency.
Projects
None yet
Development

No branches or pull requests

3 participants