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

Guidance for API deprecation #9

Open
tomkirbygreen opened this issue Jan 5, 2022 · 0 comments
Open

Guidance for API deprecation #9

tomkirbygreen opened this issue Jan 5, 2022 · 0 comments
Labels
SDK Relates to the Ably SDK Team and our ways of working in open source.

Comments

@tomkirbygreen
Copy link
Contributor

tomkirbygreen commented Jan 5, 2022 •
edited by ably-sync-bot
Loading

I would like to see some guidance and ideally some cross-SDK standardisation around deprecating APIs.

What is the protocol for communicating the intention to remove or change an existing API?
Do we need to communicate this to Support and Documentation? In other words which groups / people outside of the SDK team need a heads-up about the proposed change?
How long after flagging (by some means) an API as subject to removal or change do we need to wait? Is this measured in 'releases' (somewhat woolly given our variable release cadence) or calendar months?
@tomkirbygreen tomkirbygreen added the SDK Relates to the Ably SDK Team and our ways of working in open source. label Jan 5, 2022
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
1 participant
@tomkirbygreen