Well, it is good to have exactly one valid format. With two options like "vN.M.L" and "N.M.L" confusion starts to spread and why not allow a capital "V" too and a "ú" too for "útgáfa" and "r" for "release" should be allowed too. If you start with two options you open up a flood of endless discussions about why just these two and not that other too.
So the whole question is "why v.N.M.M and not N.M.L ?" This might be a question of taste and thus unanswerable. I personally think the v prefix makes it clear it is a version tag. Even Semver 1.0.0 suggested to prefix the version number with v in the VCS. And the v prefix is pretty common: Docker, Kubernetes, CoreOS. And retagging a "3.1.4" as "v3.1.4" is dead simple. In summary. There is one format and that one is v<Semver>; it is a standard and standards are to be implemented. V. On Monday, 4 February 2019 07:52:09 UTC+1, Maxim S wrote: > > Now go mod requires to have prefix "v" for it's tag in VCS and it's > mandatory so you can't use tags in form of "A.B.C" in your workflow. > But this limitation has little to zero reason to exist so why is it strict > requirement? Why not to allow use both "vA.B.C" and "A.B.C" tags? Who are > using "A.B.C" tags for anything but version? > It can be done without modifying current .mod files by just ignoring "v" > prefix during repository search. > > Many teams use prefix-less tags for versions (both for Go before modules > and non-Go projects). Not to mention that it's not a valid semver > <https://github.com/semver/semver/blob/master/semver.md#is-v123-a-semantic-version> > (but > very common though) and thus requirement even less understandable. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
