The document discusses versioning policies for Chef cookbooks. It introduces the Cookbook Versioning Policy (CVP) which provides guidelines for assigning version numbers to cookbooks based on the type and impact of changes. Major versions are for breaking changes, minor versions are for adding non-breaking features, and patch versions are for fixing bugs. The CVP aims to prevent breaking changes from surprising users and encourage transparent and consistent versioning practices.

1. What’s In This
Cookbook?
or, How do I know what I’m eating?
Wednesday, June 12, 13

2. Mike Fiedler
Operations
Datadog.com
Twitter: @mikefiedler
GitHub: @miketheman
Ops School
Chef-Community
Roller Derby Ref
Skydiver
©Alex Erde
Wednesday, June 12, 13

3. It starts with...
• good intentions
• roll your own code
• open source a solution
• desire to release goodness frequently
Wednesday, June 12, 13

4. a running list
Flickr: Ben Garney
Wednesday, June 12, 13

5. Crap.
What’s the diff?
Wednesday, June 12, 13

6. So many cookbooks!
Flickr: ex.libris
Wednesday, June 12, 13

7. Bring on
Versions!
RHEL 6.0 2010-11-09
RHEL 6.1 2011-05-19
RHEL 6.2 2011-12-06
RHEL 6.3 2012-06-20
RHEL 6.4 2013-02-21
Flickr: Alan Dayley
Wednesday, June 12, 13

8. Enter
SemVer.org
Wednesday, June 12, 13

9. X.Y.Zapache
2.2.0
2.2.23
2.4.3
postgresql
9.0.13
9.1
9.1.9
9.2.4
python
2.6.6
2.6.8
2.7.5
Wednesday, June 12, 13

10. But for cookbooks?
Flickr: toholio
Wednesday, June 12, 13

11. Enter CVP
Cookbook Versioning Policy:
Sane Versioning for Chef Cookbooks
http://chef-community.github.io/cvp/
Mad props to Kevin Christen!
Wednesday, June 12, 13

12. Public API
• External interfaces
• Names other recipes may be using
• Libraries, Providers & Resources
• Templates used via Providers
Wednesday, June 12, 13

13. Major Versions
• Breaking changes
• Removing previously
deprecated functionality
Wednesday, June 12, 13

14. Minor Versions
• Adding non-breaking features
• New recipe, resource, provider
• New attribute w/default value
• Relaxing constraints
Wednesday, June 12, 13

15. Patch Versions
• Fixing something broken
• Typos
Wednesday, June 12, 13

16. In conclusion...
Flickr: Geoffrey Gilmour-Taylor
Wednesday, June 12, 13

17. Mike’s Version Theory
• Don’t break stuff
• Don’t surprise others
• Breaking something? Be LOUD!
• Use similar practices for internal code
Wednesday, June 12, 13

18. KEEP IT HOT
http://foodfightshow.org/
Wednesday, June 12, 13

19. Speak to me
about:
Chef
DevOps
OpsSchool
Automation
Wine
Skydiving
Roller Derby
#HugOps
Wednesday, June 12, 13

20. Yes, we’re hiring.
http://jobs.datadoghq.com/
Wednesday, June 12, 13