- From: Hedge Hog <
>
- To:
- Subject: [chef] Chef cookbooks versions and chef versions.
- Date: Thu, 21 Apr 2011 17:49:55 +1000
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=iPmqZjneTP4LfHoSRU3NUU+fB0Oq821w5sHHdgOcjTIoNFJHiu8QWdE/L37tk2OkTj S78hp5ExPX5HEzCuClRDez5KqIySGd880JI5q582O9dfGP3Y4s5J/5qomBmo73UjFJyB G9sYH9hy/g+Rlf07e1iV4i4I5rcp6WoOwJBbo=
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
- [chef] Chef cookbooks versions and chef versions., Hedge Hog, 04/21/2011
Archive powered by MHonArc 2.6.16.