[chef-dev] Re: Re: Re: Re: chef-server versioning

[Noah Kantrowitz < >]

In the future, this kind of thing really needs to go in release announcements 
and change logs, and is itself potentially a breaking change.

--Noah

On Mar 19, 2014, at 8:27 AM, Daniel DeLeo 
<
 >
 wrote:

> The server team decided to abandon “dev-odd” versioning. When 
> Chef/then-Opscode originally adopted dev-odd, Chef was a ruby-only project, 
> distributed as a rubygem, and rubygems did not yet support prerelease 
> versions. Those things have changed and our tooling (omnibus) produces 
> packages with extra version fields to indicate non-release builds.  
> 
> --  
> Daniel DeLeo
> 
> 
> On Wednesday, March 19, 2014 at 4:28 AM, Barthélemy Vessemont wrote:
> 
>> even versions are release version.
>> odd versions are dev version, and never should be released.
>> 
>> That's why cookbook's version jump 2 by 2.
>> 
>> 
>> On Wed, Mar 19, 2014 at 2:09 AM, JJ Asghar 
>> <
 
>>  
>> (mailto:
 )>
>>  wrote:
>>> 
>>> Seth Vergo rolls a d20-1 and says hey that works?
>>> </joke>
>>> 
>>> -
>>> - JJ Asghar
>>> 
>>>> On Mar 18, 2014, at 19:43, "Noah Kantrowitz" 
>>>> <
 
>>>>  
>>>> (mailto:
 )>
>>>>  wrote:
>>>> 
>>>> Is there a reason the versions for chef-server go 11.0.0, 11.0.2, 
>>>> 11.0.4, 11.0.6, 11.0.8, 11.0.10, 11.0.11?
>>>> 
>>>> --Noah
>> 
>> 
>> 
>> --  
>> Barthélemy Vessemont - 
>> 
 
>>  
>> (mailto:
 )
>> Ingénieur en informatique diplômé de l'UTC (Compiègne)
> 
> 
>

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail