kerchunk icon indicating copy to clipboard operation
kerchunk copied to clipboard

Versioning and Releases

Open lsterzinger opened this issue 3 years ago • 3 comments

I'm wondering with the increase in development activity recently if we want to revisit the release strategy/schedule. On one hand, I think Kerchunk would benefit from a YYYY.MM.Version system (such as dask) for monthly/submonthly releases.

On the other hand, there's plenty of opportunity for the API to change, so semantic versioning might still be preferable to distinguish pre-release 0.0.x versions from future more-stable version.

Thoughts?

lsterzinger avatar Aug 22 '22 15:08 lsterzinger

I personally don't have a strong feeling. I do get annoyed when people quibble over whether a change is breaking or not and which part of the version to change, but as you say, there will be plenty of changes here. Perhaps it's reasonable to go for calendar numbers once we have something roughly stable?

martindurant avatar Aug 22 '22 15:08 martindurant

Excited to use some of the new changes. Is a release going to happen soon? If not I can point to a git sha for now, but my ops team grumbles when I do that.

emfdavid avatar Sep 09 '22 15:09 emfdavid

0.0.8 is now on pypi

martindurant avatar Sep 09 '22 15:09 martindurant