On Thu, Jan 13, 2022 at 11:32 PM Brandon Heenan <[email protected]> wrote:
> > This probably requires an Enterprise Policy, to reduce the risk for > managed installs. +bheenan@ for opinions on that front. > > I agree, this looks like a breaking change according to > go/chrome-enterprise-friendly and therefore needs a policy. Instructions > for implementing a policy are here: > https://source.chromium.org/chromium/chromium/src/+/main:docs/enterprise/add_new_policy.md > if you haven't done it before, and the enterprise team is happy to help if > anything seems confusing. Having this implemented as a "soft removal" with > a temporary policy escape hatch significantly reduces enterprise risk, > since even if we are surprised by a use case hiding behind many > enterprises' tendency to turn off metrics, those users can > break-fix themselves immediately while staying on the latest version. > I agree, and a policy is already in place <https://source.chromium.org/chromium/chromium/src/+/main:components/policy/resources/policy_templates.json;l=29155-29200;drc=f537981ecfb9fe7b4027ac902c71432f50f57bcd>. (I'll have to update it with the new milestones, though.) -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALG6KPNccT4qX8KEyjMkSg5hgytn_RaUMEAC%2B81Ffd9gYK-X0g%40mail.gmail.com.
