@jbudorick, @agrieve - Do we have plans for N bots upstream? And is the work to remove --strict-mode desirable from a build perspective?

If there are no plans for upstream N bots but there are plans for upstream O bots IIRC, then perhaps that effort is better spent fixing strict mode issues for O instead.

#3: We already have an upstream N bot (https://build.chromium.org/p/chromium.android.fyi/builders/Nougat%20Phone%20Tester), but won't be deploying more at scale. We are planning on a significant upstream O deployment next year.

Sounds good, then I'd like to focus on StrictMode issues in O and skip N. WDYT?

sgtm, though I don't really know how they differ and would be curious to hear about cases where something breaks N but not O.

This is more for aligning context, timing, and effort, so I don't fix a bunch of new StrictMode issues on N now and have a repeat when O is in our fleet. All effort can be concentrated for O at a later time, sometime in 2018.

Making this available until it's actually in our OKRs.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot