operatorai / operatorai/modelstore
Add support for calendar versioning
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 403
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
We decided to adopt a different versioning approach over UUID - CalVer with a short UUID for ensuring uniqueness:
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
Start by reviewing the linked Slack discussion, since the issue provides no files, tests, entry points, or acceptance criteria. Identify where model versions are generated and persisted, then clarify the CalVer format, short-UUID rules, compatibility expectations, and tests needed before implementation can be scoped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100