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

Document versioning policy #34

Closed
robin-nitrokey opened this issue Feb 7, 2022 · 2 comments
Closed

Document versioning policy #34

robin-nitrokey opened this issue Feb 7, 2022 · 2 comments

Comments

@robin-nitrokey
Copy link

The v1.6.0 release broke compatibility with the previous releases because the spsdk.sbfile.images module was removed. To avoid such changes affecting other projects, it would be helpful to know your versioning policy. Which library versions can be assumed to be compatible?

@mstarecek
Copy link
Contributor

The SPSDK project is still far from being a stable product (in PyPI it's marked as alpha).
I know the 1. in version is very misleading, but this is a corporate "can of worms" I don't want to open :)
Considering the version being major.minor.patch we can't promise everything will be compatible with a "minor" release (1.5->1.6). What we want to maintain is backward compatibility in "patch" releases.
We'll add this kind of disclaimer either directly in README or in generated docs.

robin-nitrokey added a commit to Nitrokey/pynitrokey that referenced this issue Feb 14, 2022
As discussed in <nxp-mcuxpresso/spsdk#34>, spsdk only aims to be compatible between patch releases so we add a corresponding maximum version to the dependency specification.
@marekvi95
Copy link
Contributor

I am closing this issue, the versioning policy was already described by @mstarecek.

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

3 participants