Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Semantic Versioning #126

Open
nrdxp opened this issue Jan 28, 2022 · 1 comment
Open

Semantic Versioning #126

nrdxp opened this issue Jan 28, 2022 · 1 comment
Assignees
@disassembler @blaggacao
Labels
enhancement New feature or request

Comments

@nrdxp
Copy link
Contributor

nrdxp commented Jan 28, 2022 •
edited
Loading

Originally, I wanted to start the same versioning scheme here I had initiated for bitte cli, which was the semver semantic. At the time, it was argued that calendar version may be more appropriate, and that's what was initiated.

However, now that we are maintaining release branches for patches and hot-fixes, it really seems that semantic versioning would be more appropriate. Adding additional commits to a date versioning release kind of destroys the meaning of the version, and the patch release number x.x.[0-9] seems more appropriate for that kind of thing.
@jonringer
Copy link
Contributor

Agreed. CalVer is more oriented around "packages with a static interface, but changing content". Bitte is under heavy development right now, and the API is changing greatly.

@blaggacao blaggacao added the enhancement New feature or request label Jun 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@disassembler disassembler

@blaggacao blaggacao

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@disassembler @blaggacao @jonringer @nrdxp