Azure / Azure/azure-sdk-tools

The service/feature team must explicitly agree no breaking change to GAed libraries

Open
#6,452 14 comments 0 reactions 2 assignees Claimed by @jrferry101 View on GitHub
Breaking Changes Engagement Experience
Dominant language
C#
Stars
135
Forks
260
Avg merge
3d 1h
Merged PRs (30d)
144

Description

The following request is initiated from management-plane, but I think this can be applied to data plane SDK release too.

The service/feature team must explicitly agree no breaking change to GAed libraries. “Explicitly” means if we can keep a recording of their commitment when they approaching first GA? And we shall let the team know the consequence – If you introduce any breaking change to GAed libraries, you may have to work on the breaking changes in the future SDK releases manually. We truly hope this can reduce breaking change number and frequency, which bothers us a lot, refer to the breaking change analysis attached below

![image](https://github.com/Azure/azure-sdk-tools/assets/18413981/59b9a8b8-64b0-4c28-ba3a-380aa2765a1a)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.