Develop schema version bump policy
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 16
Description
Develop a proper strategy how schema version bump should work
- Gates for new features?
- When does it require a version bump --> SemVer
- Version control in the API.. etc
probably best as an rfc
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
No files or tests are named. Start by locating the schema definitions and API version-handling entry points, then review existing release and SemVer practices. Done means an RFC that defines feature gates, version-bump criteria, and how schema versions are represented in the API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, release
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100