Issue 1489861 in chromium: Flag expired : enable-async-dns is expired in M120

[chrome-branch-day via monorail]

Comment #1 on issue 1489861 by chrome-b...@chops-service-accounts.iam.gserviceaccount.com: Flag expired : enable-async-dns is expired in M120
https://bugs.chromium.org/p/chromium/issues/detail?id=1489861#c1

This flag has been marked as expiring in M120 or earlier. This bug has been opened for the Eng teams to clean up the references for the flag in the //chrome/browser/flag-metadata.json as well as references to that flag.

This is a friendly reminder to help get this clean up completed.

If you think this flag needs to be extended beyond this milestone, please follow these steps:
- 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 M120 branch you're all set; if you do it after the M120 branch you'll need to merge that CL to the M120 branch as well.

You can check the branch date for this milestone at https://chromiumdash.appspot.com/schedule

--
You received this message because:
1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment or make updates.

[ricea via monorail]

Updates:
Components: Internals>Network>DNS

Comment #2 on issue 1489861 by ri...@chromium.org: Flag expired : enable-async-dns is expired in M120
https://bugs.chromium.org/p/chromium/issues/detail?id=1489861#c2

(No comment was entered for this change.)

[chrome-branch-day via monorail]

Comment #3 on issue 1489861 by chrome-b...@chops-service-accounts.iam.gserviceaccount.com: Flag expired : enable-async-dns is expired in M120
https://bugs.chromium.org/p/chromium/issues/detail?id=1489861#c3

This flag has been marked as expiring in M121 or earlier. This bug has been opened for the Eng teams to clean up the references for the flag in the //chrome/browser/flag-metadata.json as well as references to that flag.

This is a friendly reminder to help get this clean up completed.

If you think this flag needs to be extended beyond this milestone, please follow these steps:
- 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 M121 branch you're all set; if you do it after the M121 branch you'll need to merge that CL to the M121 branch as well.

You can check the branch date for this milestone at https://chromiumdash.appspot.com/schedule

[chrome-branch-day via monorail]

Comment #4 on issue 1489861 by chrome-b...@chops-service-accounts.iam.gserviceaccount.com: Flag expired : enable-async-dns is expired in M120
https://bugs.chromium.org/p/chromium/issues/detail?id=1489861#c4

This flag has been marked as expiring in M122 or earlier. This bug has been opened for the Eng teams to clean up the references for the flag in the //chrome/browser/flag-metadata.json as well as references to that flag.

This is a friendly reminder to help get this clean up completed.

If you think this flag needs to be extended beyond this milestone, please follow these steps:
- 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 M122 branch you're all set; if you do it after the M122 branch you'll need to merge that CL to the M122 branch as well.

[chrome-branch-day via monorail]

Comment #5 on issue 1489861 by chrome-b...@chops-service-accounts.iam.gserviceaccount.com: Flag expired : enable-async-dns is expired in M120
https://bugs.chromium.org/p/chromium/issues/detail?id=1489861#c5

This flag has been marked as expiring in M123 or earlier. This bug has been opened for the Eng teams to clean up the references for the flag in the //chrome/browser/flag-metadata.json as well as references to that flag.

This is a friendly reminder to help get this clean up completed.

If you think this flag needs to be extended beyond this milestone, please follow these steps:
- 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 M123 branch you're all set; if you do it after the M123 branch you'll need to merge that CL to the M123 branch as well.