Shulou(Shulou.com)06/02 Report--

This article will explain in detail how the JavaScript V8 engine version release process is, the quality of the article content is high, so Xiaobian shares it for everyone to make a reference, I hope you have a certain understanding of relevant knowledge after reading this article.

0. introduced

The V8 release process is closely tied to Chrome's release process. The V8 team also uses all four Chrome distribution channels to push new versions to users.

If you want to see the V8 version in Chrome, you can check it out in OmahaProxy. For each Chrome version, separate branches are created in the V8 codebase to make tracking easier, such as Chrome 45.0.2413.0.

1. Canary releases Canary releases

Through Chrome's Canary channel, new Canary versions are pushed to users every day. Normally, this version comes from the latest, stable enough version of the master branch.

Canary branches usually look like this:

remotes/origin/4.5.352. Dev releases development version

Through Chrome's Dev channel, a new development version is pushed to users every week. Normally, this release includes the latest stable V8 release on the Canary channel.

Dev branches usually look something like this.

remotes/origin/4.5.353. Beta releases Beta releases

A new major branch is created approximately every 6 weeks, such as Chrome 44. This happens in sync with the creation of Chrome's Beta channel. Chrome Beta is pinned to V8's branch-heads. About 6 weeks later the branch was promoted to Stable.

All changes are cherry-picked only to the stable version.

Beta branches usually look like this

remotes/branch-heads/4.5

They are based on Canary branches.

4. Stable releases

A new major stable release is completed approximately every six weeks. Since the newest Beta branch simply upgrades to Stable, no special branch is created. This version is pushed to users via Chrome's Stable channel.

The branches of Stable usually look like this.

remotes/branch-heads/4.5

They are promoted (or reused) from Beta branches.

5. Which version should I embed in my app?

You should use the latest branch of Chrome's Stable channel.

We often re-merge important bug fixes into stable branches, so if you care about stability and security and correctness, you should include these updates-which is why we recommend "the tip of the branch" rather than the exact version.

As soon as a new branch is promoted to Stable, we stop maintaining the previous stable branch. This happens once every six weeks, so you should be prepared to update frequently.

For example, the current stable Chrome version is 44.0.2403.125, and the corresponding V8 version is 4.4.63.25. So you should embed branch heads/4.4. And when Chrome 45 enters the stable channel, you should update to branch branch-heads/4.5.

About JavaScript V8 engine version release process is how to share here, I hope the above content can be of some help to everyone, you can learn more knowledge. If you think the article is good, you can share it so that more people can see it.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.