This bug requires manual review: Reverts referenced in bugdroid comments after merge request.
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), ketakid @(ChromeOS), govind@(Desktop)
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Before we approve merge to M61, could you please answer followings?
* Is this M61 regression?
* Is this critical to have it in M61 or can wait until M62? Please note M61 is already branched on July 20th and we're only taking critical merges in.
* There are multiple large cls are listed here, all need to be merged to M61? If yes, all changes are well baked/verified in Canary, having enough automation tests coverage and safe to merge?
* Is this M61 regression?
- Yes.
* Is this critical to have it in M61 or can wait until M62? Please note M61 is already branched on July 20th and we're only taking critical merges in.
- It affects web.whatsapp.com in a very obvious way so I think its bad enough to fix asap.
* There are multiple large cls are listed here, all need to be merged to M61? If yes, all changes are well baked/verified in Canary, having enough automation tests coverage and safe to merge?
- Only one CL needs to be landed - the other two are a revert and a reland. The revert was due to an unintentional change to TestExpectations. Since no-one is banging down the door to get it fixed we could let it bake until someone does!
Comment 1 by bugdroid1@chromium.org
, Jul 28 2017