Branches with `v` prefix

[dagood]

Right now, the repo has a v0.1 branch, and v0.1.0 + v0.1.1 tags.

In my experience, I've only seen v prefixes before tags, and it's sometimes been a useful way to differentiate tags from branches. It's certainly valid to have v0.1 as a branch, just not something I've seen before.

In .NET land, the norm is e.g. release/6.0 and v6.0.1. I've also seen a bare version: 0.1 with v0.1.1 tag.

I'm curious if this naming style has history behind it, maybe in the Go ecosystem in particular?

(Figured we might as well discuss this on a GitHub issue for posterity. 😄)

@qmuntal @microsoft/golang-compiler

[qmuntal]

There are some well-known Go projects prefixing branch names with v, but I wouldn't say is a general pattern, but an inertia inherited from tags naming convention.

I did not have any strong opinion on this topic until now, but I buy your arguments and I think we should name branches differently to avoid confusion.