5 ms·

I really do not like the “semver-like” versioning string requirement. My packages are already tagged with valid semver releases and now I need to change them by

I really do not like the “semver-like” versioning string requirement. My packages are already tagged with valid semver releases and now I need to change them by adding a “v” prefix. If you don’t know what I’m talking about vgo requires the release to be tagged like “v1.0.3” which is not standard semver.

cesarb 8y ago
> vgo requires the release to be tagged like “v1.0.3” which is not standard semver Are you talking about git tags? Tagging a release with a "v" followed by the version number has been done since the very first git repository. I don't think semver has any official standard; the closest I can find is https://semver.org/spec/v1.0.0.html https://semver.org/spec/v1.0.0.html, which does say "When tagging releases in a version control system, the tag for a version MUST be “vX.Y.Z” e.g. “v3.1.0”."
- anonfunction 8y ago
  Yes I am talking about git tags. I purposely followed semver 2.0.0 which doesn't mention anything about a "v" prefix. Thanks for finding an old mention of version control tagging! At the end of the day it's not a big deal. I will just duplicate the tags so it won't break any dep configurations.
lobster_johnson 8y ago
Every Go project I've used uses git tags prefixed with "v", e.g. v1.0.3. https://github.com/gogo/protobuf https://github.com/gogo/protobuf https://github.com/olivere/elastic https://github.com/olivere/elastic https://github.com/golang/protobuf https://github.com/golang/protobuf https://github.com/sanity-io/litter https://github.com/sanity-io/litter
- anonfunction 8y ago
  I've seen a few that used 1.0.3 which is also common among python and other languages. One of the biggest new go projects, istio[1], uses the 1.0.3 style. I'll switch over in the future and keep existing tags for dep users. 1. https://github.com/istio/istio/tags https://github.com/istio/istio/tags

cesarb 8y ago

> vgo requires the release to be tagged like “v1.0.3” which is not standard semver Are you talking about git tags? Tagging a release with a "v" followed by the version number has been done since the very first git repository. I don't think semver has any official standard; the closest I can find is https://semver.org/spec/v1.0.0.html https://semver.org/spec/v1.0.0.html, which does say "When tagging releases in a version control system, the tag for a version MUST be “vX.Y.Z” e.g. “v3.1.0”."

anonfunction 8y ago
Yes I am talking about git tags. I purposely followed semver 2.0.0 which doesn't mention anything about a "v" prefix. Thanks for finding an old mention of version control tagging! At the end of the day it's not a big deal. I will just duplicate the tags so it won't break any dep configurations.

lobster_johnson 8y ago

Every Go project I've used uses git tags prefixed with "v", e.g. v1.0.3. https://github.com/gogo/protobuf https://github.com/gogo/protobuf https://github.com/olivere/elastic https://github.com/olivere/elastic https://github.com/golang/protobuf https://github.com/golang/protobuf https://github.com/sanity-io/litter https://github.com/sanity-io/litter

anonfunction 8y ago
I've seen a few that used 1.0.3 which is also common among python and other languages. One of the biggest new go projects, istio[1], uses the 1.0.3 style. I'll switch over in the future and keep existing tags for dep users. 1. https://github.com/istio/istio/tags https://github.com/istio/istio/tags