Hi, we have officially branched to be prepared for the upcoming Chrome version *77*. The base of the branch is currently rolled into Chromium. It is based on one of the latest Chrome Canaries.
Integration into Chromium is stopped until Chromium has branched too. V8 branch: *branch-heads/7.7* Original Canary: *77.0.3863.2* Ref to be used in Chromium: *https://chromium.googlesource.com/v8/v8/+/refs/heads/7.7-lkgr <https://chromium.googlesource.com/v8/v8/+/refs/heads/7.7-lkgr>* If your CL is not included in *77.0.3863.2* you might consider merging it into the branch *branch-heads/7.7*. In that case please apply the label *Merge-Requested-7.7* to the bug the CL is fixing. The corresponding V8 commit is 9e90797ecece9193e0cdb612fd1639e02d0fc4fa <https://chromium.googlesource.com/v8/v8/+/9e90797ecece9193e0cdb612fd1639e02d0fc4fa>. See https://v8.dev/docs/merge-patch for more information on merging. Thanks, Maya Lekova & Sigurd Schneider On Thu, Jul 18, 2019 at 11:29 AM Maya Lekova <[email protected]> wrote: > Hi, > > it is time again. If you have any questions regarding the release, please > ping this thread. > > *THURSDAY 2017-07-18: API adoption freeze starting* > V8 will branch in one week for the upcoming Beta phase for Chrome 77. On > the 2017-07-25 one of the latest Canaries will be selected to be the branch > point. This means we will roll this version into Chromium in order to give > them and Blink time to synchronize with the roll. Essentially this will be > a revert to an older version! > 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 yangguo@. > > MONDAY 2017-07-22: 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. > > THURSDAY 2017-07-25: Create 7.7 branch > Create the branch based on one of the latest/most stable Canaries. The > auto-roller is closed (maybe over the weekend). 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 > 7.7 too! See information on merging & patching for the details. Merge > approvers for this release are Chrome Release Managers. > > Latest MONDAY 2017-07-29: Back to normal and API adoption freeze is lifted > Auto-roller is running again and we are back to normal business. > > Cheers, > Maya > > -- -- 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/CAFszerUSPfnq%2B2YX5gOAT_MTVkfAF-A7QdbAnkbJ7E9_fxNZzw%40mail.gmail.com.
