Versioning and Releases
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 366
- Forks
- 96
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
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?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the issue discussion and reviewing the project's current release process. This needs an agreed versioning scheme and release schedule, with the decision documented and applied consistently to future releases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100