Add automatic versioning #312
Conversation
| @@ -1,5 +1,13 @@ | |||
| [bumpversion] | |||
| current_version = 0.0.1 | |||
There was a problem hiding this comment.
Should Viper start from 0.1 or 0.0.1?
There was a problem hiding this comment.
0.1.0 would be when features are solidified and ready for the first beta IMO.
I would start at 0.0.1 for now.
There was a problem hiding this comment.
Viper is ready to use right now, not in production environment but if in test environment. So, VIper has solid features :) At least compile a whole contract.
But it's ok start from 0.0.1 👍
There was a problem hiding this comment.
Sure agreed, but there are unimplemented features that I would argue need to be there for a complete first draft to alpha/beta with. Perhaps that is more conservative than necessary, but that's my opinion.
I'm not in any position to be dictating what the first version is here anyways since that still needs to be set up initially after this PR is merged, and that's not up to me haha. I just used 0.0.1 because that is what it was.
There was a problem hiding this comment.
Hahaha, agree .. Well, maybe @vbuterin could tell you what is the right version for now.
But the PR is OK. : +1:
After this pull request is accepted, create a new tag with
bumpversion