ADR Feature flag #34
Closed
ADR Feature flag #34
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bigkevmcd
reviewed
Sep 8, 2021
|
|
||
| ## Context | ||
|
|
||
| As our organization grows, we will have more developers and more work in flight. Commonly, this results in long-lived branches, complicated testing environments, and slower release cycles. Using feature falgs allows us to develop closer to the trunk and separate releasing from delivering software. In addition, feature flags can be used for beta testing new features without special builds, operational controls, for example, kill switches, progressive and ring-based deployments, and in some cases, features available by product tiers. |
There was a problem hiding this comment.
Suggested change
| As our organization grows, we will have more developers and more work in flight. Commonly, this results in long-lived branches, complicated testing environments, and slower release cycles. Using feature falgs allows us to develop closer to the trunk and separate releasing from delivering software. In addition, feature flags can be used for beta testing new features without special builds, operational controls, for example, kill switches, progressive and ring-based deployments, and in some cases, features available by product tiers. | |
| As our organization grows, we will have more developers and more work in flight. Commonly, this results in long-lived branches, complicated testing environments, and slower release cycles. Using feature flags allows us to develop closer to the trunk and separate releasing from delivering software. In addition, feature flags can be used for beta testing new features without special builds, operational controls, for example, kill switches, progressive and ring-based deployments, and in some cases, features available by product tiers. |
| As our organization grows, we will have more developers and more work in flight. Commonly, this results in long-lived branches, complicated testing environments, and slower release cycles. Using feature falgs allows us to develop closer to the trunk and separate releasing from delivering software. In addition, feature flags can be used for beta testing new features without special builds, operational controls, for example, kill switches, progressive and ring-based deployments, and in some cases, features available by product tiers. | ||
|
|
||
| Feature flags can be simple environment variables passed into a program, or a SaaS service used to define, serve, and check flags at runtime. | ||
|
|
There was a problem hiding this comment.
This really needs a problem statement with some practical examples of the sorts of features we'd ship with this
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #17