Expand process around breaking permission changes
Problem to solve
Changing permissions that adds a restriction is often a breaking change, we should document the process to correctly communicate and release these changes.
Further details
Permission restrictions would require us to use a feature flag, mention it in the release post and alert GitLab support and account management.
When dealing with a security update, we need to have a way to alert the community of the breaking change without making the vulnerability known.
Proposal
- Add restricting permissions changes to the when to use a feature flag docs.
- Check and update the feature flag rollout template to ensure we have appropriate steps for communicating in a release post, alerting support and account management.
- Check and update the documentation around breaking changes to ensure we have appropriate steps for communicating in a release post, alerting support and account management.
Other links/references
Edited by Steve Abrams