jatkinson1000 / jatkinson1000/archeryutils
Describe classification table versioning
- Dominant language
- Python
- Stars
- 20
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Once we decide in a versioning system this should be documented here.
A tag should be applied to specific commits match the tables.
Should we coalesce versioning or keep two separate schemes?
Is changing of the underpinning data thresholds considered a breaking change for semantic versioning?
API does not change but results do.
Contributor guide
No contributing guide indexed for this repository
Research direction
No file, test, or entry point is named. First resolve whether the classification tables share a versioning scheme and whether threshold changes are breaking changes; document the decision, including how tags identify matching commits and how result changes are treated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100