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


Zach Robinson
 

This was killing me the other day on cf-deployment.  I really prefer to exclude the 'v'.  It doesn't seem to add anything.
-Zach

On Wed, Feb 28, 2018 at 8:52 AM Jane Day <jday@...> wrote:
I share Andrew's peeve.
For the docs, we state that all version numbers should be prefaced with the lowercase "v". 


On Wed, Feb 28, 2018 at 2:21 AM, Andrew Edgar1 <aedgar1@...> wrote:
Hi All,
 
One pet peeve of mine is the inconsistency of version tagging in the community github repos.  I think by looking it's about 50/50 whether there is a "v" or no "v" in the tag for each new release version.
 
Would it be possible to settle on some sort of standard?  Can we all use a "v" or all not use a "v" (I have no preference).  But when trying to write scripts that pull information from the repos it would be much easier if I didn't need a big if statement on whether to add this "v" or not :)
 
Anybody else have strong opinions one way or another.
 
CAPI, all the buildpack releases, routing-release    -  No 'v'
loggregator, statsd-injector-release, uaa, diego, garden-runc-release - Yes 'v'
 
Thanks,
 
Andrew Edgar
 
---
Andrew Edgar
Senior Software Engineer
Dept. D293, IBM Research & Development Boeblingen 
-------------------------------------------------------------------------------------------------------------------------------------------
IBM Deutschland
Schoenaicher Str. 220
71032 Boeblingen
Phone: 49-7031-16-2868
E-Mail: aedgar1@...
-------------------------------------------------------------------------------------------------------------------------------------------


Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.