[chef] Re: Chef cookbooks versions and chef versions.

[Matt Ray < >]

Cookbook releases are independent of Chef releases. I'm pretty sure
cookbooks do not get touched on the cookbooks site when a new Chef
release is made. The GitHub repo is versioned so when 0.10 is released
the cookbooks there will all support 0.10 properly (and if you need
0.9.x support you can use the older versions).

That said, I haven't seen any documentation about requiring a specific
Chef version in the metadata.rb, so I opened
http://tickets.opscode.com/browse/CHEF-2251

Thanks,
Matt Ray
Technical Evangelist | Opscode, Inc
E: 

 
 T: (512) 731-2218
Twitter, Github: mattray



On Thu, Apr 21, 2011 at 2:49 AM, Hedge Hog 
<
 >
 wrote:
> Hi,
> I'd appreciate it opscode can confirm that in their cookbooks repo,
> they bump any of the major or minor or patch version numbers of any
> affected cookbook when they release a Chef version?
>
> The reason: in the cookbooks account I'm tagging each cookbook repo
> with the version in the metadata.json (creating/updating the
> metadata.json as required).
> I'm wondering if there is some assurance that, for example, v0.6.2 of
> zenoss will always point to the cookbook as it was when Chef was at
> v0.9.12.
> Or, in other words, is it possible that when the changes in the
> Cookbooks 0.10.rc.0 branch get merged into master, that an affected
> cookbook metadata version number does not get bumped?
>
> TIA
>
> --
> πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
> [The fox knows many things, but the hedgehog knows one big thing.]
>   Archilochus, Greek poet (c. 680 BC – c. 645 BC)
> http://wiki.hedgehogshiatus.com
>