Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add single team clause so feature gates align with enhancement guidance #1705

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add single team clause so feature gates align with enhancement guidance #1705

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion dev-guide/featuresets.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -391,7 +391,7 @@ The Kubernetes rebase is a good example of a large change that doesn’t really
The teams involved in landing these changes have worked with the TRT to create sufficient pre-merge signal to greatly
decrease the regression risk—effectively achieving the same goal as Feature Gates via another route.

Small features that take less than a sprint to fully develop, merge and test don’t really benefit from Feature Gates.
Small features involing a single team that take less than a sprint to fully develop, merge and test don’t really benefit from Feature Gates.
Those sorts of features haven’t been the biggest cause of our release risk.

## Should feature gates necessarily be tied to an API, i.e does it apply only when there are new APIs?
Expand Down