Add policies to force enable/disable Network Service |
||||||
Issue descriptionSpeaking with the enterprise team, they mentioned that we should start the launch without deploying to any enterprise users first. This makes our experiment cleaner. We can try to stabilize non-enterprise population first and then attempt to launch to both non-enterprise and enterprise users. We can condition our finch flag along with checking if !base::win::IsEnterpriseManaged() first.
,
Sep 18
FTR I don't think we should add additional roadblocks. I'll discuss with the team.
,
Sep 18
how about a finch flag to turn off enterprise users in case if we get bugs in enterprise?
,
Sep 26
Per discussion with Daniel, Robert and George, we will add an enterprise policy to disable network service. This is to cover the case of network process not working in enterprise environments which would block disabling the finch experiment from reaching the users.
,
Sep 27
Issue 887816 has been merged into this issue.
,
Sep 27
re Comment #4, can we also have a policy to turn on network service. this will help our trusted testers a lot for testing network service on beta.
,
Sep 28
,
Sep 28
I'm still not convinced we need this: i.e. this is only for the case that the network process won't start/wok in enterprise-only environments. Removing stable blocker for now.
,
Oct 11
won't fix per discussoin |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by dougt@chromium.org
, Sep 13