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.

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

please be rigorous with version IDs #95

Open
onthebreeze opened this issue Feb 18, 2020 · 0 comments
Open

please be rigorous with version IDs #95

onthebreeze opened this issue Feb 18, 2020 · 0 comments
Assignees

Comments

@onthebreeze
Copy link
Contributor

I have version 0.2.8 installed from a week ago.
I saw there is a new commit 4 days ago - which I installed
It is still tagged 0.2.8 - so the version ID is no longer a reliable indicator of version.

Please make sure that the version ID is always updated when making a new commit ot master branch. the conventions is

major.minor.patch where

  • major = breaking change or major release.
  • minor = new feature that is not breaking
  • patch = bug fix or other change that does not introduce a new feature/function.

So I'd suggest we move to 0.3.0 now and then start incrementing the patch number every commit unless there is some new feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants