anomaly / anomaly/lab-python-server
Outline and document guidelines around formats for version number in version control tags and package repositories
- Dominant language
- Python
- Stars
- 16
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
Not quite, but it's around consistency of how we label things. For examples I noticed that we have been using `v` prefixed labels when we tagged projects on Github but not prefixed when we published packages on the container registry.
**Describe the solution you'd like**
Our projects use SemVer, and everyone is closely aligned with how that works. We should write out a guide that outlines our policy of prefixing tags on:
- Container registry
- Version control systems (e.g Github)
**Describe alternatives you've considered**
NA
**Additional context**
I published a package on a repository with a prefix and the charts don't reference the prefix and hence had installation issues on EKS.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.