Re: release tagging ... to v or not to v

Julz Friedman

+1 to Eric's view also. I like being able to (sort of) filter version tags.


On Thu, 1 Mar 2018 at 15:55 Marco Voelz <marco.voelz@...> wrote:

We also tag out bosh-openstack-cpi and bosh with a 'v' prefix. Here's what the github "draft a new release page" has to say about this

> Tagging suggestions

> It’s common practice to prefix your version names with the letter v. Some good tag names might be v1.0 or v2.3.4.

> If the tag isn’t meant for production use, add a pre-release version after the version name. Some good pre-release  versions might be v0.2-alpha or v5.9-beta.3.


I agree with Eric's view that this helps to distinguish git tags which are meant to be final releases from the ones that are just "tags that mean something else".


Warm regards





From: <cf-dev@...> on behalf of Ruben Koster <superruup@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Thursday, 1. March 2018 at 09:50
To: "cf-dev@..." <cf-dev@...>
Subject: Re: [cf-dev] release tagging ... to v or not to v


The v prefix works nicely with concourse git-resource tag_filter. 

Join to automatically receive all group messages.