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 On Wednesday, July 28, 2021 at 2:00:07 AM UTC+2 [email protected] wrote: > Hey everyone, > > I am trying to understand the release process and versioning of V8 and had > a question. > > I came across Release Process <https://v8.dev/docs/release-process> & V8’s > version numbering scheme > <https://v8.dev/docs/version-numbers#which-v8-version-should-i-use%3F> > 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 > <https://chromium-review.googlesource.com/c/v8/v8/+/3056359>) (which will > later become the revision in Chromium.src DEPS); whereas Chromium.src > performs it on main (Link to CL > <https://chromium-review.googlesource.com/c/chromium/src/+/3052678>). > > 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 > -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-dev/7373b330-9f58-434e-99fe-da2c65a868een%40googlegroups.com.
