As many of you in the Community have seen by now, I recently joined Chef as a Vice President (more on what in particular I will be up to in a minute).

Continuous Delivery Pioneer to Play Leadership Role at Chef as Enterprise DevOps Adoption Surges SEATTLE – August 20, 2014 – Chef, the leader in web-scale IT automation, today announced Jez Humble has joined the company as vice president of development velocity.

Ohai chefs, Today we have released Chef Client 10.34.0 and Ohai 6.24.0. These releases contain important bug fixes and improvements that has been blockers to the Chef users who are on Chef 10. The MVP of this release is again **Phil Dibowitz**. Thanks Phil for your continuous support to us while maintaining Chef 10.

Here at Chef we have the privilege to share all kinds of innovation, community news and compelling events with you via the blog. I’m particularly happy to invite you to a webinar we’re hosting this week with Scholastic.

Ohai Chefs, Today we have released a patch release, 11.14.6, for Chef Client with some regression fixes and enhancements. We needed to skip 11.14.4 since we’ve realized that a couple of fixes slipped through the cracks and wasn’t included in 11.14.4 after tagging.

Hello Chefs, We are happy to announce that the 11.1.4 release of the open source Chef Server is now available. This is primarily a bug fix release. This release includes a bump in OpenSSL from 1.0.1h to 1.0.1i, as we announced in a previous post.

On Tuesday, August 12th at 15:10 UTC, the cookbook dependency API provided by Supermarket became unusable. We are very sorry for this outage and interruption to workflow. In this post, I will explain what happened and the mitigation steps we are taking to prevent this from happening in the future.

Continuing our series of updates on the new Chefs joining our engineering corps., we have another group of three delightful folks who have come on board.

Earlier this morning, a Supermarket code deployment caused the dependency API at /universe to start returning errors. Redis became unreachable, resulting in Berkshelf v3.x clients failing to resolve dependencies. At Chef, we conduct postmortem meetings for outages and issues with the site and services.