-
Notifications
You must be signed in to change notification settings - Fork 104
Release #158
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
Comments
It really doesn't matter to me - I have no strong motivation to change, but no objection. |
Cool. Let’s just stay with the old system for now then.
… On Dec 18, 2020, at 2:49 PM, Martin Durant ***@***.***> wrote:
It really doesn't matter to me - I have no strong motivation to change, but no objection.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#158 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKAOIRWOA24FR5YKBRJDMTSVO57FANCNFSM4VBVCP5A>.
|
@TomAugspurger -- No issues. Please go ahead. Regarding the switch to Calver, I wasn't aware of the change, and don't have strong opinions. Over a longer term, I would lean toward following the conventions used by dask and dask-foo. |
0.5.9 is up on PyPI now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'd like to make a release with the recent performance improvements. Is that OK @hayesgb? I seem to have push access to PyPI, so I can take care of it.
Dask has recently switched to Calver. I believe the various dask-foo projects will migrate to calver too. @martindurant do you have versioning plans for s3fs, gcsfs, and perhaps fsspec? Do you think they should use calver too?
The text was updated successfully, but these errors were encountered: