Check PageLifecycle flag |
|||||
Issue descriptionWe have enabled the PageLifecycle flag preemptively, however need to wait for API owners on I2S. If the LGTMs don't come through then we need to change the flag back to experimental (from stable).
,
Jun 4 2018
This issue is marked as a release blocker with no OS labels associated. Please add an appropriate OS label. All release blocking issues should have OS labels associated to it, so that the issue can tracked and promptly verified, once it gets fixed. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 4 2018
,
Jun 11 2018
Friendly ping to get an update on this issue. Thanks.!
,
Jun 11 2018
The flag is sticking (we got needed launch approvals), so closing the bug.
,
Jun 11 2018
[Auto-generated comment by a script] We noticed that this issue is targeted for M-68; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-68 label, otherwise remove Merge-TBD label. Thanks.
,
Jun 12 2018
Looks like no merge required to M68, but can you please confirm?
,
Jun 12 2018
Correct, no merge is required. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ojan@chromium.org
, May 31 2018