As it was already said there are no reasons not to use prefixed tags. The point was not to restrict prefixless tags and not an opinion *against* prefixed tags. These are fine and quite common and good.
Problem is that literally all of my projects and projects of my team use plain semver tag and used them (for Go code too, yes) for a long time before modules. Probably that's the case for some other developers who might have struggle too but not very active. Basically it leads to dropping all the version tags for all Go projects while having other naming convention for other projects. And Go team decided for some reason that standard and valid semver naming is invalid and should not be used because it is not widely used among them. While chosen naming scheme itself is viable exclusion to semver and not like "A.B.C" semver. There's no any argument against using prefixless tags in addition to current naming conventions. Literally zero issues without any compromise to backward compatibility and so. On Tuesday, February 5, 2019 at 1:45:51 AM UTC+3, kortschak wrote: > > The text of for that answer is not saying that a person cannot use > "vM.m.p", but that "vM.m.p" means semver M.m.p. They even use `git tag > v1.2.3 -m "Release version 1.2.3"` as an example. > > In the case of Go, the v is a marker that the following is a semver > version. > -- 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.
