Python Feature Management Release Notes #976
Conversation
|
|
||
| ## 1.0.0 - July 01, 2024 | ||
|
|
||
| GA Release of the feature management support for Python. |
There was a problem hiding this comment.
Please list what has been released during previews here for a stable release. Most users don't use preview or track the changes.
There was a problem hiding this comment.
There was only one preview release, and the GA's only change was the version number.
There was a problem hiding this comment.
I know, but users won't know if there are more or less been included in the stable version unless you list them, right? This is a practice we should do for all stable releases.
There was a problem hiding this comment.
So, I should copy the 4 lines right below this into this part too?
|
|
||
| ### Enhancement | ||
|
|
||
| * Added support for variant feature flags defined using [Microsoft Feature Management schema](https://github.com/microsoft/FeatureManagement/blob/main/Schema/FeatureManagement.v2.0.0.schema.json). Variants and telemetry can be declared using [Microsoft Feature Flag schema v2](https://github.com/microsoft/FeatureManagement/blob/main/Schema/FeatureFlag.v2.0.0.schema.json). The Microsoft Feature Management schema is designed to be language agnostic, which enables you to apply a consistent feature management configuration across Microsoft feature management libraries of different programming languages. |
There was a problem hiding this comment.
I didn't expect this. Unlike .NET, v2 schema is not new to Python FM. I was expecting we talk about variant feature flags. I copied the following from the .NET release notes.
Added support for variant feature flags. A variant feature flag is an enhanced feature flag that supports multiple states or variations. While it can still be toggled on or off, it also allows for different configurations, ranging from simple primitives to complex JSON objects. Variant feature flags are particularly useful for feature rollouts, configuration rollouts, and feature experimentation (also known as A/B testing).
There was a problem hiding this comment.
I put it like this as variants are part of the schema, and technically before this we only supported the non-variant part of the schema.
Updating to your version.
| * Added support for variant feature flags defined using [Microsoft Feature Management schema](https://github.com/microsoft/FeatureManagement/blob/main/Schema/FeatureManagement.v2.0.0.schema.json). Variants and telemetry can be declared using [Microsoft Feature Flag schema v2](https://github.com/microsoft/FeatureManagement/blob/main/Schema/FeatureFlag.v2.0.0.schema.json). The Microsoft Feature Management schema is designed to be language agnostic, which enables you to apply a consistent feature management configuration across Microsoft feature management libraries of different programming languages. | ||
|
|
||
| See our [documentation](https://learn.microsoft.com/azure/azure-app-configuration/feature-management-python-reference#variants) for more information. | ||
|
|
There was a problem hiding this comment.
We should add a separate bullet for telemetry.
|
|
||
| ### Enhancement | ||
|
|
||
| Added support for variant feature flags. A variant feature flag is an enhanced feature flag that supports multiple states or variations. While it can still be toggled on or off, it also allows for different configurations, ranging from simple primitives to complex JSON objects. Variant feature flags are particularly useful for feature rollouts, configuration rollouts, and feature experimentation (also known as A/B testing). |
There was a problem hiding this comment.
Please add a bullet point.
|
|
||
| For more information, see the [feature reference document](https://learn.microsoft.com/azure/azure-app-configuration/feature-management-python-reference#variants). | ||
|
|
||
| Added support for telemetry in feature flags. Telemetry is a powerful feature that allows you to track how your feature flags are being used. It provides insights into the effectiveness of your feature flags and helps you make data-driven decisions. Telemetry is particularly useful for feature experimentation (also known as A/B testing) and feature rollouts. |
There was a problem hiding this comment.
Please add a bullet point.
No description provided.