You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 12, 2022. It is now read-only.
There is a tag on github named "0.1.0" that should designate the version hacienda is at. It is not in sync with the version used in gemspec.
I propose to used semantic versioning and the following scheme: major.minor.patch+build.x.sha . The "major.minor.patch" would read from the last tag we have on git while "x" would be the number of commits since that tag and "sha" the current sha. More info here: http://semver.org/spec/v2.0.0-rc.1.html point 12. This would mean that releasing a new version would mean adding a new tag on git.
Say that the last tag is 0.3.2 and there are 40 commits since then, the version would be 0.3.2+build.40.23ef98.
Any comments?
The text was updated successfully, but these errors were encountered:
There is a tag on github named "0.1.0" that should designate the version hacienda is at. It is not in sync with the version used in gemspec.
I propose to used semantic versioning and the following scheme: major.minor.patch+build.x.sha . The "major.minor.patch" would read from the last tag we have on git while "x" would be the number of commits since that tag and "sha" the current sha. More info here: http://semver.org/spec/v2.0.0-rc.1.html point 12. This would mean that releasing a new version would mean adding a new tag on git.
Say that the last tag is 0.3.2 and there are 40 commits since then, the version would be 0.3.2+build.40.23ef98.
Any comments?
The text was updated successfully, but these errors were encountered: