TBD Versioning Scheme - Githubissues

TBD54566975 / open-source-playbook

TBD's Ethos and Practices behind our Open Source Business

Apache License 2.0

1 stars 2 forks source link

TBD Versioning Scheme #4

Open ALRubinger opened 1 year ago

ALRubinger commented 1 year ago

Provide guidelines to projects for versioning guidelines:

Branching and pre-release for acceptance testing
Tagging
Repositories (Go, JS/TS, etc)
Do we need/want a repo manager (ie. JFrog)?
Naming conventions
- ie. 0.x.y can be not back-compat
- After 1.x.y, back-compat
- x, minor number, includes API additions
- y, patch number, includes bug fixes
- Major number breaks back-compat
- How does wire compatibility fit in?
How much of Semantic Versioning guidelines would we like to adopt?