Add release notes for .NET Provider 8.0.0 stable release #975
Conversation
| ## 8.0.0 - October 3rd, 2024 | ||
| ### Breaking Changes | ||
| * Increased the default maximum retry count when resolving Key Vault references and increased the minimum refresh interval to 1 minute. This helps prevent throttled requests to Key Vault and will reduce the chance of failing to resolve a secret due to momentary failures. [#589](https://github.com/Azure/AppConfiguration-DotnetProvider/issues/589) | ||
|
|
There was a problem hiding this comment.
Can we repeat all the breaking changes here since the last stable release? Most users don't follow all the preview releases and track all the breaking changes.
releaseNotes/MicrosoftExtensionsConfigurationAzureAppConfiguration.md
Outdated
Show resolved
Hide resolved
releaseNotes/MicrosoftExtensionsConfigurationAzureAppConfiguration.md
Outdated
Show resolved
Hide resolved
releaseNotes/MicrosoftExtensionsConfigurationAzureAppConfiguration.md
Outdated
Show resolved
Hide resolved
releaseNotes/MicrosoftExtensionsConfigurationAzureAppConfiguration.md
Outdated
Show resolved
Hide resolved
| * The APIs `AzureAppConfigurationRefreshOptions.SetCacheExpiration` and `FeatureFlagOptions.CacheExpirationInterval` have been deprecated and will be removed in a future release. They are replaced with `AzureAppConfigurationRefreshOptions.SetRefreshInterval` and `FeatureFlagOptions.SetRefreshInterval`, respectively. This change does not affect functionality but aims to eliminate confusion regarding cache expiration implied by the previous API names. [#350](https://github.com/Azure/AppConfiguration-DotnetProvider/issues/350) | ||
|
|
||
| ### Enhancements | ||
| * **Variant Feature Flags and Telemetry**: This is the first stable release with support for the `variants`, `allocation`, and `telemetry` properties for feature flags added by version 4.0.0 of the [Microsoft.FeatureManagement.*](https://github.com/microsoft/FeatureManagement-Dotnet) libraries. While variant feature flags can still be toggled on or off, they also allow 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 (like A/B testing, for example). |
There was a problem hiding this comment.
A/B testing and experimentation are the same thing, not an example of the other.
There was a problem hiding this comment.
Our experimentation docs didn't make it seem that way https://learn.microsoft.com/en-us/azure/azure-app-configuration/concept-experimentation#scenarios-for-using-experimentation
It makes it sound like A/B testing is one way to use experimentation, not that they're equivalent. Is our stance that it's the same thing?
There was a problem hiding this comment.
That document can definitely use some improvement. The same technology that is used for experimentation can be used for other scenarios like feature rollout, but will you call your feature rollout an experiment? I won't.
No description provided.