# tag scheme

3 messages from 2014-11-25 to 2014-11-26. Participants: Carsten Mattner, Jeff King, Rick Umali.
Thread: https://gitlist.dev/t/38046

## Carsten Mattner, 2014-11-25 16:17

Subject: tag scheme
Message-ID: <CACY+HvouE0GBH=e4iu7hsFfBJmeZiPKgAC0870S5vPADSYXcJg@mail.gmail.com>
URL: https://gitlist.dev/e/CACY%2BHvouE0GBH%3De4iu7hsFfBJmeZiPKgAC0870S5vPADSYXcJg%40mail.gmail.com

```
I'm looking for advice on a tagging scheme, especially pros/cons
of using a 'v' prefix as in v2.1.0 like git does.

My impression is that using a common prefix for tags makes it
simple to distinguish from maintenance branches for past releases
but it seems that most repositories use tags without a prefix.
Before I settle on using vX.Y.Z (which I favor right now), I'd like to
understand why some projects do not prefix tags.

Any comments?

```

## Jeff King, 2014-11-25 17:09

Subject: Re: tag scheme
Message-ID: <20141125170941.GA23258@peff.net>
URL: https://gitlist.dev/e/20141125170941.GA23258%40peff.net
In-Reply-To: <CACY+HvouE0GBH=e4iu7hsFfBJmeZiPKgAC0870S5vPADSYXcJg@mail.gmail.com>

```
On Tue, Nov 25, 2014 at 05:17:52PM +0100, Carsten Mattner wrote:

> I'm looking for advice on a tagging scheme, especially pros/cons
> of using a 'v' prefix as in v2.1.0 like git does.
> 
> My impression is that using a common prefix for tags makes it
> simple to distinguish from maintenance branches for past releases
> but it seems that most repositories use tags without a prefix.
> Before I settle on using vX.Y.Z (which I favor right now), I'd like to
> understand why some projects do not prefix tags.

I cannot speak definitely for people who prefer no prefix, but I imagine
that they simply see it as useless noise.

Personally, I like the prefix because it lets me wildcard-match only the
releases (and not other random tags I might have):

  git tag -l 'v*'

Of course I quite often want to drop release-candidate tags from such a
list, too, and I have to resort to "grep -v -- -rc" to do so. :)

-Peff

```

## Rick Umali, 2014-11-26 21:13

Subject: Re: tag scheme
Message-ID: <20141126211356.GA15127@rick-t60>
URL: https://gitlist.dev/e/20141126211356.GA15127%40rick-t60
In-Reply-To: <20141125170941.GA23258@peff.net>

```
On Tue, Nov 25, 2014 at 12:09:42PM -0500, Jeff King wrote:
> On Tue, Nov 25, 2014 at 05:17:52PM +0100, Carsten Mattner wrote:
> > I'm looking for advice on a tagging scheme, especially pros/cons
> > of using a 'v' prefix as in v2.1.0 like git does.
> > 
> > My impression is that using a common prefix for tags makes it
> > simple to distinguish from maintenance branches for past releases
> > but it seems that most repositories use tags without a prefix.
> > Before I settle on using vX.Y.Z (which I favor right now), I'd like to
> > understand why some projects do not prefix tags.
> 
> I cannot speak definitely for people who prefer no prefix, but I imagine
> that they simply see it as useless noise.
> 
> Personally, I like the prefix because it lets me wildcard-match only the
> releases (and not other random tags I might have):
> 
>   git tag -l 'v*'
> 
> Of course I quite often want to drop release-candidate tags from such a
> list, too, and I have to resort to "grep -v -- -rc" to do so. :)

I wanted to second the prefix notation. I have a repository with 
three tag prefixes (namespaces?): SUBMIT, CODE and V. The prefix 
helps me stay organized. I've been adding -n to the git tag command
that Jeff mentioned:

git tag -l -n 'SUBMIT*'
-- 
Rick (www.manning.com/umali) Umali

```