- From: Mike <
>
- To: Chef Dev <
>, Kevin Christen <
>
- Subject: [chef-dev] ANNOUNCE: RFC: Cookbook Versioning Policy
- Date: Tue, 18 Dec 2012 09:58:57 -0500
Ohai Chefs!
First off, Happy Tuesday!
After the Chef Summit 2012, where the topic of Cookbook Versioning was
discussed by many, Kevin Christen reached out on the dev list with a
proposal to start by figuring out what each part of a cookbook's
version number should encompass.
We wrote back and forth a bit, and Kevin did most of the heavy lifting
(writing?), and we are now happy to announce that we're looking for
comments from both Opscode and the community.
For your review:
https://docs.google.com/document/pub?id=1DuZ0g98vFV7-I23c6_7prKBnWSgVb7s0cU0EgeIidc0
(should be world-viewable)
The goal is that by having a documented changes-to-revision policy, we
will be able to produce better predictability when it comes to
releases, and have a higher degree of predictability when using
someone else's code.
Please feel free to email Kevin & myself directly with your feedback,
or respond to this thread on the list, so others can chime in.
Looking forward to hearing your thoughts and opinions,
Mike Fiedler & Kevin Christen
- [chef-dev] ANNOUNCE: RFC: Cookbook Versioning Policy, Mike, 12/18/2012
Archive powered by MHonArc 2.6.16.