Update V8 in next to 4.3.61.27

[domenic]

Currently at 4.3.61.21. This will allow us to stop floating 70716fd.

[Fishrock123]

cc @bnoordhuis / @chrisdickinson

[silverwind]

This also includes the fix for #1398, so we can stop doing the workaround.

[ronkorving]

What's the policy on which V8 versions to follow? V8 4.5.x has been shipped with a whole bunch of ES6 features people have been waiting for (arrow functions, just to name my favorite addition).

[bnoordhuis]

@ronkorving We try to follow stable release branches (for now, TBD for LTS.) 4.5 isn't stable yet but see #2091 for an integration branch.

[ronkorving]

Thanks for the clarification. I get a bit lost sometimes when I try to find this kind of information. What defines stable for V8? Which branches of io.js are meant for what? etc..

[bnoordhuis]

A working definition for 'stable' is when the V8 team creates the release branch for that version, i.e., 4.3 and 4.4 have release branches, but 4.5 doesn't yet.

At the moment, master is the branch that v2.x releases are cut from, and next is the basis for the upcoming v3.0.0 release.

[ronkorving]

Thanks again 👍

[lancedikson]

@ronkorving @bnoordhuis V8 4.5 stable released

[domenic]

That is exactly the opposite of what that blog post says. V8 4.5 beta was first cut today. Stable will be released in six weeks.

[targos]

Closing this issue as we now have v8 4.4 in next branch and 4.5 in next+1.