chromium/src
0
Fork 0
Code Activity

Update add_new_policy with the warning about changing defaults

Browse Source 
BUG=b:266377723

Change-Id: Ia90cafc09e67c373281000c48575fff70e6fe2b0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4199025
Commit-Queue: Roman Sorokin <rsorokin@google.com>
Auto-Submit: Roman Sorokin <rsorokin@google.com>
Reviewed-by: Roland Bock <rbock@google.com>
Cr-Commit-Position: refs/heads/main@{#1098490}
This commit is contained in:
Roman Sorokin
2023-01-30 09:19:17 +00:00
committed by Chromium LUCI CQ
parent 86ba634ef1
commit d9adffca0f
1 changed files with 9 additions and 4 deletions

13
docs/enterprise/add_new_policy.md

@ -306,10 +306,15 @@ the code that handles existing policy settings, in particular:
- Make sure the policy metadata is up-to-date, in particular `supported_on`, and
the feature flags.
- In general, don't change policy semantics in a way that is incompatible
(as determined by user/admin-visible behavior) with previous semantics. **In
particular, consider that existing policy deployments may affect both old and
new browser versions, and both should behave according to the admin's
intentions**.
(as determined by user/admin-visible behavior) with previous semantics.
- **In particular, consider that existing policy deployments may affect**
**both old and new browser versions, and both should behave according to**
**the admin's intentions.**
- **Do not modify the behavior when the policy is not set**. To be more
specific: values `default`, `default_for_enterprise_users` and
`default_policy_level` must (likely) never change after the launch. Contact
cros-policy-muc-eng@google.com for guidance if you need to make such
changes.
- **An important pitfall is that adding an additional allowed
value to an enum policy may cause compatibility issues.** Specifically, an
administrator may use the new policy value, which makes older Chrome versions