[chef-dev] Re: Re: Re: Supported versions

[Noah Kantrowitz < >]

On Jun 1, 2014, at 2:43 PM, Daniel DeLeo 
<
 >
 wrote:

> 
> 
> On Sunday, June 1, 2014 at 1:14 PM, Julian C. Dunn wrote:
> 
>> Can I also raise "what is our lifecycle policy for released versions
>> of Chef". i.e. when can we stop releasing and supporting Chef 10?
>> 
>> - Julian
> Historically, we’ve maintained N and N - 1.

Should probably have an explicit minimum time in addition to that, like 
"major versions will be supported for at least two years". That leaves room 
in case the chef-client team elects to release more often in the future.

>> 
>> On Sun, Jun 1, 2014 at 4:10 PM, Adam Jacob 
>> <
 
>>  
>> (mailto:
 )>
>>  wrote:
>>> With the Chef DK showing up, it looks like we need to chat about the list 
>>> of
>>> ways we as a community want to manage chef, ruby, and friends. A few 
>>> things
>>> we should answer:
>>> 
>>> 1. What versions of ruby is the chef gem supported on?
> 
> ChefDK requires ruby 2.0+. It would not be difficult to change the one or 
> two parts of the code that use Ruby 2.0 features. That said, 1.9.3 is in 
> maintenance mode, only getting security updates and is scheduled for EOL 
> next February. I would assume that people managing their own ruby 
> environments are using some sort of version management tooling 
> (rvm/rbenv/chruby) and all the tools I’m familiar with work on 2.0, so I 
> don’t see this as an onerous requirement. I’m willing to be convinced 
> otherwise if someone has a compelling story.
> 

Because omnibus-chef has been shipping with 1.9.3, I think that needs to be 
supported until those versions of Chef are EOL'd.

--Noah

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