Auto-roll is active again. Back to normal.

On Thu, Aug 31, 2017 at 1:15 PM Michael Hablich <[email protected]>
wrote:

> Hi,
>
> we have officially branched to be prepared for the upcoming Chrome version
> 62. The base of the branch is currently rolled into Chromium
> <https://chromium-review.googlesource.com/c/chromium/src/+/645548>. It is
> based on one of the latest Chrome Canaries.
>
> V8 branch: branch-heads/6.2
> Original Canary: 62.0.3200.0
> Ref to be used in Chromium:
> https://chromium.googlesource.com/v8/v8/+log/6.2-lkgr
>
> If your CL is not included in 62.0.3200.0 you might consider merging it
> into the branch 6.2. In that case please apply the label
> 'Merge-Requested-6.2' the the bug the CL is fixing.
> See https://github.com/v8/v8/wiki/Merging%20&%20Patching for more
> information on merging.
>
> Thanks,
> Michael
>
> On Thu, Aug 24, 2017 at 9:21 AM Michael Hablich <[email protected]>
> wrote:
>
>> Hi,
>>
>> it is time again. If you have any questions regarding the release, please
>> ping this thread.
>>
>> THURSDAY 2017-08-24: API adoption freeze starting
>> V8 will branch in one week for the upcoming Beta phase for Chrome 61. On
>> the 2017-08-31 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@ or hablich@.
>>
>> MONDAY 2017-08-27: 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-08-31: Create 6.2 branch
>> Create the 6.2 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 an an important fix, please make sure that the fix is on
>> 6.2 too! See information on merging & patching for the details. Merge
>> approver for this release is hablich@.
>>
>> Latest MONDAY 2017-09-04: Back to normal and API adoption freeze is lifted
>> Auto-roller is running again and we are back to normal business.
>>
>> Cheers,
>> Michael
>>
>

-- 
-- 
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].
For more options, visit https://groups.google.com/d/optout.

Reply via email to