Re: Your flag: site-isolation-trial-opt-out is expiring in M86

[Alex Moshchuk]

I put together a CL to extend the expiration for this.  I think it's still important to have an easily accessible site isolation opt-out switch on Android, since we will likely continue to experiment with expanding site isolation to additional devices or with new heuristics.

On Tue, Aug 11, 2020 at 2:43 PM <sriniv...@google.com> wrote:

Hi,

Your flag: site-isolation-trial-opt-out expired in M85

In M86 we will begin hiding from the Chrome UI (and eventually removing) flags that are marked as expired in flag-metadata.json

All flags expired until M83 have bugs opened for flag owners to clean up the code references. Please help get this cleaned up so your flag will be removed from this file and you dont get these emails. The bug report and dashboard here

This is in accordance with the process documented in //docs/flag_expiry.md . You are receiving this email because you are listed as the owner of a flag that will begin expiring in M86, or because you are a PM who might need visibility into this process.In M86, we will hide flags that expired as of M86 or earlier from chrome://flags. From this point onward, every subsequent release will hide flags that expired as of that release.

What you need to do for M86 (before the branch date Aug 20 2020):

1. Look at the list of flags marked as expiring in M86 or earlier. The authoritative source for this list is the list_flags.py tool

tools/flags/list_flags.py --expired-by 86

The current list of expiring flags (as of @r792688) is captured in this document

2. If you see a flag listed as expiring that you want to keep, create a CL updating //chrome/browser/flag-metadata.json with an appropriate new expiration milestone. If you do this before the M86 branch you're all set; if you do it after the M86 branch you'll need to merge that CL to the M86 branch as well.

Flags expiring in M86 as of @r792688

Thanks,

Srinivas