Your flag: back-forward-cache is expiring in M96

[sriniv...@google.com]

Hi,

Your flag: back-forward-cache expired in M95

In M96 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 M94 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 has expired before or in M96, or because you are a PM who might need visibility into this process.In M96, we will hide flags that expired as of M96 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 M96 (before the branch date Oct 7, 2021):

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

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

The current list of expiring flags (as of r924407) 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 M96 branch you're all set; if you do it after the M96 branch you'll need to merge that CL to the M96 branch as well.

Flags expiring in M96 as of r924407

Thanks,

Srinivas