Branch cut V8 8.3
9 views
Skip to first unread message
Lutz Vahl
Mar 26, 2020, 6:13:12 AM3/26/20
to v8-...@googlegroups.com
Hi,
It is time again. If you have any questions regarding the release, please ping this thread.
THURSDAY 2020-03-26: API adoption freeze started.
V8 will branch in one week for the upcoming Beta phase for Chrome 83. On the 2020-04-02 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 hablich@ or vahl@.
WEDNESDAY 2020-04-01: 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 2020-04-02: Create 8.3 branch
Create the 8.3 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 8.3 too! See information on merging & patching for the details. Merge approvers for this release are vahl@ (backup hablich@)
Latest MONDAY 2020-04-06: Back to normal and API adoption freeze is lifted
Auto-roller is running again and we are back to normal business.
It is time again. If you have any questions regarding the release, please ping this thread.
THURSDAY 2020-03-26: API adoption freeze started.
V8 will branch in one week for the upcoming Beta phase for Chrome 83. On the 2020-04-02 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 hablich@ or vahl@.
WEDNESDAY 2020-04-01: 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 2020-04-02: Create 8.3 branch
Create the 8.3 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 8.3 too! See information on merging & patching for the details. Merge approvers for this release are vahl@ (backup hablich@)
Latest MONDAY 2020-04-06: Back to normal and API adoption freeze is lifted
Auto-roller is running again and we are back to normal business.
Cheers,
Lutz
Lutz Vahl
Apr 2, 2020, 11:33:03 AM4/2/20
to v8-...@googlegroups.com
Hi,
we have officially branched to be prepared for the upcoming Chrome version 83. 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/8.3
Original Canary: 83.0.4101.0
Ref to be used in Chromium: https://chromium.googlesource.com/v8/v8/+/refs/heads/8.3-lkgr
If your CL is not included in 83.0.4101.0 you might consider merging it into the branch branch-heads/8.3. In that case please apply the label Merge-Request-8.3 to the bug the CL is fixing. See https://v8.dev/docs/merge-patch for more information on merging.
Thanks,
Cheers,
Lutz
Reply all
Reply to author
Forward
0 new messages