-
Notifications
You must be signed in to change notification settings - Fork 665
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
release tag format, compatibility with the Go versioning proposal #985
Comments
We can definitely do that, let me see if we can edit older tags and avoid using |
As far as I can see it's not necessary to change older tags, adding the ones with the I'm not sure what you mean with "avoiding using |
New releases should absolutely have the |
I am not sure why vgo choose "v" prefix are you saying it doesn't work without |
As far as I understood the implementation and the proposal, version tags are required to start with I don't know why this was chosen, maybe it was even arbitrarily, but that's the way it is. :) |
This change is needed to follow `vgo` guidelines put forth by Go community. https://github.com/golang/vgo/blob/master/vendor/cmd/go/internal/semver/semver.go#L6 > // semantic version strings must begin with a leading "v" Supported format style https://github.com/golang/vgo/blob/master/vendor/cmd/go/internal/semver/semver.go#L11 > // vMAJOR[.MINOR[.PATCH[-PRERELEASE][+BUILD]]] Fixes minio#985
This change is needed to follow `vgo` guidelines put forth by Go community. https://github.com/golang/vgo/blob/master/vendor/cmd/go/internal/semver/semver.go#L6 > // semantic version strings must begin with a leading "v" Supported format style https://github.com/golang/vgo/blob/master/vendor/cmd/go/internal/semver/semver.go#L11 > // vMAJOR[.MINOR[.PATCH[-PRERELEASE][+BUILD]]] Fixes #985
Cool, thanks! |
Hey,
when testing if restic compiles with
vgo
, the prototype implementation for adding versioning to the Go toolchain, I noticed that some time ago you switched from release tags in the formv1.2.3
(as required byvgo
) to1.2.3
, so thev
prefix was dropped.This leads to
vgo
selecting thev1.0.0
release tag, which is ancient:Would you mind adding a second tag
v6.0.1
which points to the same commit the tag6.0.1
does, and tagging future releases with thev
prefix? That'd be awesome :)Thanks!
The text was updated successfully, but these errors were encountered: