This bug requires manual review: We are only 6 days from stable.
Please contact the milestone owner if you have questions.
Owners: amineer@(clank), cmasso@(bling), ketakid@(cros), govind@(desktop)
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Thank you meacer@. It would be great if this change can wait till M58 as it is too late for M57 although the change is very small. The reason I'm asking to wait for M58 is :
* b29954e8ac243142eaedbcc3c6e54d480373ee38 is not yet made to canary
* Bug 594215 exists since March, 2016
* We're very close to M57 Stable RC cut for Desktop (possibly today) and we're taking ONLY important merges in at this point.
I do think this is an important merge, since we have multiple external stakeholders expecting the deprecation in M58, and we need to warn devs before. Is there a refresh of M57 that we could possibly get this into?
re #3: ok, got it(just curious to know why the merge request came so late if this is an important merge). Thank you.
meacer@, please update the bug with canary result tomorrow. If it is looks good in Canary, I will approve the merge.
Note: Stable cut may get delayed due to ongoing investigation on bug 698681. So we might be able to pick up merge for current bug 699277 for initial stable roll out if not it will go to future M57 stable refresh (if any). Please let me know if there is any concern here. Thank you
> re #3: ok, got it(just curious to know why the merge request came so late if this is an important merge). Thank you.
Yes, sorry about that. I was able to only land the patch earlier today hence the late merge request.
> meacer@, please update the bug with canary result tomorrow. If it is looks good in Canary, I will approve the merge.
Thanks! I'll keep an eye on it and update tomorrow. I think merging this to a stable refresh is reasonable too. emilyschechter, wdyt?
Thank you meacer@.
+amineer@ as this is also applicable to Android (This is a late M57 merge request, small cl per original bug description, important merge per comment #3 and change looks good in Canary per comment #7).
Do we not translate console warnings? It looks like the string with the warning is hard coded as English. If this is normal practice I suppose it's fine, just curious.
I don't have objections to the merge, but I'm not holding up our Android release for this. I'd recommend escalating and reaching out to developers using other channels in addition to the warning. Have we looped in the web platform team to see if they have recommendations on how to do this? Do we have an entry on chromestatus.com that relates to this?
Comment 1 by sheriffbot@chromium.org
, Mar 7 2017