M60 branch is here! (branch 3112)

109 views
Skip to first unread message

Richard Bustamante

unread,
May 26, 2017, 5:42:21 PM5/26/17
to chromi...@chromium.org, blin...@chromium.org
Hello Everyone,


We have branched for M60. Please read through this entire email if you plan on making changes that you want in this release.


Branches

Branch number: 3112

Branched Chromium @ revision: 474934

V8 branch: 6.0

Skia branch: chrome/m60

WebRTC branch: 60



The Merge Process:

To get a change into Chrome 60, here’s what you need to do:


  1. Have unit test and/or integration test coverage included in the change.

  2. Have your change checked into the trunk/master, and passed through either a Canary build or Dev channel release at least 24 hours and verified before asking for merge approval.

  3. Tag your bug with the correct labels: Merge-Request-60. If you tag it wrong, we won't see it.

  4. Once approved, land your change using drover, cherry-pick, or by hand.

  5. Wait for your merge to be approved.  This will trigger an email or IM notification that your bug has been approved to land.

  6. Land your change using drover, cherry-pick, or by hand. 


Regards,

Richard & Di
Reply all
Reply to author
Forward
0 new messages