Proposal: Please start using Semantic Versioning
KateGo520 opened this issue · 2 comments
I found that this project already supports Go modules. But sadly, the tags doesn't follow Semantic Versioning, which means that all tags of this project will be ignored by Go modules and replaced by pseudo-versions, go get acts weirdly when tags are not in that form. It would be great to have the tagged release be named in the format vX.X.X format so that go mod can read it.
$go get github.com/mathetake/gann@0.2.0
go: downloading github.com/mathetake/gann v0.0.0-20190419042645-f40fe07254d2
go: github.com/mathetake/gann 0.2.0 => v0.0.0-20190419042645-f40fe07254d2
Else the mod file shows something like github.com/mathetake/gann v0.0.0-20190419042645-f40fe07254d2 which is not very readable and difficult to upgrade. It’s hard to verify which version is in use. This is not conducive to version control.
So, I propose this project to follow Semantic Versioning in future versions. For example, v1.0.1, v2.0.0, v3.1.0-alpha, v3.1.0-beta.2etc, so that other project can use tag in go.mod.
@mathetake Could you help me review this issue? Thx :p
closing since I'm archiving this repo.