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.

Sign up for GitHub

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

Jump to bottom

Define 'breaking change' for Ably SDKs #46

Open
QuintinWillison opened this issue Nov 16, 2022 · 1 comment
Open

Define 'breaking change' for Ably SDKs #46

QuintinWillison opened this issue Nov 16, 2022 · 1 comment
Labels
SDK Relates to the Ably SDK Team and our ways of working in open source.

Comments

@QuintinWillison
Copy link
Contributor

QuintinWillison commented Nov 16, 2022 •
edited by ably-sync-bot
Loading

In #45 we're starting to flesh out what a 'version bump' means for an Ably SDK, including what should trigger different grades of bump (major vs minor, etc..).

There are scenarios where we may need to present a 'breaking change' where there is no change to user-facing SDK APIs. We should produce some guidance around what Ably considers a breaking SDK change in relation to less obvious edge cases (e.g. dropping support for a platform/runtime version).

As pointed out and illustrated in more detail by @owenpearson in this comment,
@QuintinWillison QuintinWillison added the SDK Relates to the Ably SDK Team and our ways of working in open source. label Nov 16, 2022
@QuintinWillison QuintinWillison mentioned this issue Nov 16, 2022
Merged
@ably-sync-bot
Copy link

➤ Automation for Jira commented:

The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-2942

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
SDK Relates to the Ably SDK Team and our ways of working in open source.
Milestone
No milestone
Development

No branches or pull requests
2 participants
@QuintinWillison @ably-sync-bot