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.

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

service - support custom strategies #11

Closed
gardleopard opened this issue Oct 15, 2014 · 2 comments
Closed

service - support custom strategies #11

gardleopard opened this issue Oct 15, 2014 · 2 comments

Comments

@gardleopard
Copy link
Contributor

Support custom strategies. Should it be possible to share custom strategies between different features or should it be feature specific?

@gardleopard gardleopard added this to the MVP 1 milestone Oct 15, 2014
@jarib jarib added the server label Oct 21, 2014
@ivarconr
Copy link
Member

The whole idea behind an activation strategy is to share it between multiple toggles (or even change strategy for a toggle when it is time to release it).

One concrete example:

  • Develper Hans protects new feature with the AwsomeFeature feature toggle.
  • Hans enables the feature for his team and product owner in production to show the not completed feature to get som feeback.
  • Product owner gives feedback on some important improvements.
  • Hans implements improvements.
  • The team decides to test the new feature on some real users and changes activation strategy for AwsomeFeature to GradualRolloutStrategy.
  • The feature behaves good and they activates it for everyone.
  • Hans removes the feature toggle from the code and from unleash.

@ivarconr ivarconr modified the milestones: Later, MVP 1 Oct 23, 2014
@jarib
Copy link
Contributor

jarib commented Nov 25, 2014

Jeg ser på mulighet til å legge til nye strategier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants