Version Bumps of V8 v/s Chromium

[Suraj Sharma]

Hey everyone,

I am trying to understand the release process and versioning of V8 and had a question.

I came across Release Process & V8’s version numbering scheme docs, that explains how it is tightly connected to Chrome’s.

Although, I did notice that for the v8 repo, automated version bumps changing the BUILD_NUMBER are performed on a branch off main (Link to CL) (which will later become the revision in Chromium.src DEPS); whereas Chromium.src performs it on main (Link to CL).

I was curious to know, if there’s a reason why we follow this model, contrary to performing these version bumps on main?

Thanks

Suraj

[Michael Hablich]

Hi Suraj,

we are not regularly updating the (minor) version number on main, as it would require to either:

• Update the version number with each commit => Point of failure for CL authors and potential for race conditions
• Have a bot running that updates the version number in a separate CL like we do on the branches with the help of our tag bot => That would spam our main with logistic CLs.

Happy to give more insight on how this works, may I ask why this topic is interesting to you?

Cheers,

Michael

[Suraj Sharma]

Hello Michael

Thanks for the response.

Sure, I'm working on improving the release process for Edge; was interested to know how chromium is able to do it so efficiently. Then I came across this peculiar tagging model for V8 and got curious to know the reasoning behind it :D

Thanks

Suraj