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.

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

sdk / extension version strategy #53

Open
ChuckHend opened this issue Aug 14, 2023 · 1 comment
Open

sdk / extension version strategy #53

ChuckHend opened this issue Aug 14, 2023 · 1 comment

Comments

@ChuckHend
Copy link
Contributor

Managing compatibility between the SDKs and the Extension is brittle. There is currently not a defined relationship between the SDKs version and the extension version. They should all follow semver, and we can use semver to define the compatibility between them. e.g. Python SDK 1.1.0 must be compatible with Extension version 1.0.0. Some things that should be implemented:

  • changes to the Extension trigger tests on the SDKs
  • any SDK changes should be run on the latest version of the Extension
  • SDKs should have some sort of compatibility check with the environment they execute against and give feedback to user. e.g. running python 0.0.1 against Extension 2.0.0 should raise something useful to the user.
@ChuckHend
Copy link
Contributor Author

when we reach 1.0 in the extension, all client will also release 1.0

then, we maintain a map of the required version of client to extension. clients will contain validation checks within their library.

@ChuckHend ChuckHend reopened this Oct 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant