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

Meaningful versioning #529

Closed
docktermj opened this issue Sep 8, 2021 · 2 comments
Closed

Meaningful versioning #529

docktermj opened this issue Sep 8, 2021 · 2 comments

Comments

@docktermj
Copy link

I appreciate that you are versioning according to year-month-day (YYYY-MM-DD), However it doesn't tell me anything important about importing a version of the s3fs into a python program. For instance 0.4.2 worked, but 2021.08.01 broke do to dependency conflicts. (Ref: #528)

The question is: When did the backward breaking change occur?

Many folks use Semantic Versioning (https://semver.org/) to communicate breakage, new features, and patches.

I hope you'll consider Semantic Versioning in the future.

@martindurant
Copy link
Member

We decided, along with other dask projects, that we could not faithfully maintain semantic versioning - given the large API and backends supported, there would, generally, always be some part of the code-base that could be considered not backward compatible on every release. fsspec is strange as a package, being both an end-user library (with a fairly stable API) and many internal details which other packages depend on in detail.

@docktermj
Copy link
Author

@martindurant I do thank you for considering Semantic Versioning.

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

2 participants