You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The goal is to "show" the Feature Toggles in multiple Enums, based on any or all of the following:
Dynamism,
Longevity,
Ownership, &/
Type (Experiment, Releases Sunsetting, Permissioning, and the 3 DevOps sub-types).
e.g. since Experiment(s) are ultimately owned by Product, have high Dynamism, and hopefully short Longevity; they would be grouped together in an "Experiment" enum (note: the Ownership will actually move from the Devs, thru QA, to Product, and may move backwards a few times).
The text was updated successfully, but these errors were encountered:
litesoft
changed the title
Support multiple Enums "classes" to define the Feature Toggles
Show the two different ways to use multiple Enums "classes" to define the Feature Toggles
Feb 24, 2023
litesoft
changed the title
Show the two different ways to use multiple Enums "classes" to define the Feature Toggles
Show the two different ways to use multiple Enums to define the Feature Toggles
Feb 24, 2023
litesoft
changed the title
Show the two different ways to use multiple Enums to define the Feature Toggles
Show the two different ways to use multiple Enums to define the Feature Toggles in the documentation
Feb 24, 2023
The goal is to "show" the Feature Toggles in multiple Enums, based on any or all of the following:
e.g. since Experiment(s) are ultimately owned by Product, have high Dynamism, and hopefully short Longevity; they would be grouped together in an "Experiment" enum (note: the Ownership will actually move from the Devs, thru QA, to Product, and may move backwards a few times).
The text was updated successfully, but these errors were encountered: