Make a 1.0 release and follow semantic versioning for breaking changes
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C++
- Stars
- 361
- Forks
- 60
- Avg merge
- 18h 41m
- Merged PRs (30d)
- 3
Description
ml_dtypes already has significant downstream users (JAX and TensorFlow), who we should not casually break. We should follow semver for managing API changes.
Contributor guide
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
The payload names no files, tests, or entry points. Begin by reviewing the repository's release process and public API surface, then define the 1.0 and semantic-versioning criteria; done means an agreed plan for releasing without casually breaking downstream users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100