[chef] Re: Re: Re: github release names and tags vs. cookbook version

[AJ Christensen < >]

Take a look at https://github.com/RiotGamesMinions/thor-scmversion - I also don't use 'v' so the tool can automatically manage bumping major/min/patch w/o having to strip the prefix during continuous integration cycles.

cheers,

--aj

On Thu, Jun 4, 2015 at 12:22 PM Charles Johnson < "> > wrote:

Noah,

Nobody's suggesting we all change. Mike only asked why the v is in the tag string, and what the general thoughts were on moving away from it. There's room in his question for those thoughts to be "nope." Personally I think it's unlikely we'll move away from having the v in the tag, but there's no harm in raising the discussion. It's healthy to question the way things have always been done when those things seem arbitrary.

As to the why versions in git tags are important: Stove automatically tags versions when publishing to Supermarket. Berkshelf supports tags in cookbook git sources, as does Policyfile. There's lots of valid reasons to write the semver to a git tag.

Thanks,

    --Charles

Charles Johnson — Product Engineer

(510) 545-9485 –  /" target="_blank"> " style="color:rgb(105,117,130)" target="_blank">  – my: Linkedin  Twitter

CHEF CHEF.IO

TM

chef.io   Blog   Facebook   Twitter   Youtube

On June 3, 2015 at 4:27:46 PM, Noah Kantrowitz ( " target="_blank"> ) wrote:

The v prefix is deeply embedded in both Chef and Ruby workflow tools. More to the point, why are you trying to read the version out of the git tag? A broader explanation of your problem might be more productive than asking why the whole community uses a single standard (semver) and suggesting we all change.

--Noah

On Jun 3, 2015, at 4:22 PM, Mike Thibodeau < " target="_blank"> > wrote:

> <Moving question to general Chef mailing list per suggestion from Nathen,>
>
> I’ve noticed that people are using the github example text and keeping redundant “v” prefix in the release tag.
> the metadata requires semver, “1.2.3”
> if the release name tag matches the version exactly we can do magical simple things by joining the [source_url] and [version]
> when there is extra text, like the “v”, we need special logic to try and figure out what that text is and how to handle it.
> the version is no longer “1.2.3” it is “v1.2.3”
>
> any thoughts on dropping the redundant “v” prefix?
> is there already an internal matching that handles the “v” ?
> how do *YOU* automate forking/branching/releasing and handle the release name?
>
>
> From: Nathen Harvey < " target="_blank"> >
> Reply-To: < " target="_blank"> >
> Date: Tuesday, June 2, 2015 at 3:27 PM
> To: Michael J Thibodeau < " target="_blank"> >
> Cc: < " target="_blank"> >
> Subject: Re: github release names and tags vs. cookbook version
>
> This is probably a good issue / question to raise in the stove project and/or on the Chef mailing list ( " target="_blank"> ).
>
> Internally at Chef, we typically use stove to publish cookbooks to the Supermarket.
>
> -Nathen
>