Your flag: enable-async-dns is expiring in M107

[sriniv...@google.com]

Hi,

Your flag: enable-async-dns expired in M106

In M107 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 M105 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 M107, or because you are a PM who might need visibility into this process.In M107, we will hide flags that expired as of M107 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 M107 (before the branch date Sept 15 2022):

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

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

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

Flags expiring in M107 as of r1035672

Thanks,

Srinivas Sista