We would like to clarify that all labels will continue to be available in
Chrome 126 after June 30th. We will provide further updates prior to Chrome
127 Stable release in July.
On Thursday, June 6, 2024 at 3:34:28 AM UTC-4 Daniel Bratell wrote:
> I agree. One lgtm is enough for this, but
I agree. One lgtm is enough for this, but thanks to John for raising it.
/Daniel
On 2024-06-06 07:59, Mike Taylor wrote:
I will claim that it doesn't, since it's just for 1 more milestone.
(if other API OWNERS disagree, now is a great time to chime in!)
On 6/6/24 2:30 PM, John Delaney
I will claim that it doesn't, since it's just for 1 more milestone.
(if other API OWNERS disagree, now is a great time to chime in!)
On 6/6/24 2:30 PM, John Delaney wrote:
Thanks Mike. I should have included this in the original email, but
the initial I2E for this feature needed 3 LGTMs as it
Thanks Mike. I should have included this in the original email, but the
initial I2E for this feature needed 3 LGTMs as it was a non-standard
experiment. Does this extension also require 3?
Thanks again!
On Thu, Jun 6, 2024 at 1:00 AM Mike Taylor wrote:
> LGTM to extend one more milestone
LGTM to extend one more milestone (M126).
On 6/5/24 11:57 PM, John Delaney wrote:
We would like to extend the Cookie Deprecation Label experimental
feature being used for Chrome Facilitated Testing. This feature
previously received approval to run through the end of M125 (ending
roughly
We would like to extend the Cookie Deprecation Label experimental feature
being used for Chrome Facilitated Testing. This feature previously
received approval to run through the end of M125 (ending roughly June 10,
2024). The Facilitated Testing period, however, is scheduled to run
through
