Hi,
It is time again. If you have any questions regarding the release, please ping this thread.
SUNDAY 2023-09-03: API adoption freeze starts.
V8 will branch on TUESDAY for the upcoming Beta phase for Chrome 118. On the 2023-09-04 one of the latest Canaries will be selected to be the branch backup candidate in case of any issues on the branch day.
In order to make this synchronization as painless as possible for V8 and Blink, please don't make API changes which make the revert more difficult and don't adopt API changes. When in doubt, ask machenbach@.
MONDAY 2023-09-04: Select backup candidate for branching
Decide if the latest Canary can be taken as a backup candidate for branching. If this is not the case the Canary needs to be stabilized ASAP.
TUESDAY 2023-09-05: Create 11.8 branch
based on one of the latest V8 versions. The auto-roller is closed. Keep in mind that this means we are not integrating with Chromium (much less test coverage). If you happen to work on an important fix, please make sure that the fix is on 11.8 too! See information on merging & patching for the details.
Latest THURSDAY 2023-09-07: Back to normal and API adoption freeze is lifted
Auto-roller is running again and we are back to normal business.
Hi,
We have officially branched to be prepared for the upcoming Chrome version 118. The base of the branch is currently rolled into Chromium. It is based on the latest V8 version.
Integration into Chromium is stopped until Chromium has branched too.
V8 branch: refs/branch-heads/11.8
V8 Version: 11.8.172
Ref to be used in Chromium: https://chromium.googlesource.com/v8/v8/+/refs/heads/11.8-lkgr
If your CL is not included in 11.8.172you might consider merging it into the branch refs/branch-heads/11.8. In that case please apply the label Merge-Request-11.8 to the bug the CL is fixing. See https://v8.dev/docs/merge-patch for more information on merging.
Thanks,
Michael
Michael Achenbach | | Software Engineer, V8 | | Google Germany GmbH | | Erika-Mann-Str. 33, 80636 München |