Ohai Chefs! Today, after a thorough RC testing phase that included a great amount of feedback and contribution from the Chef community, we’re pleased to announce the GA release of Chef Server 12. This release brings the previously premium features of Enterprise Chef, namely multi-tenancy and role-based access control, into Open Source Chef.

Chef reporting 1.2.1 is a bug-fix release to address compatability with Chef Server 12.

Ohai Chefs! On November 19th a Chef branch was accidentally force pushed to master on Github, causing existing pull requests to include unnecessary diffs. We discovered the issue, rolled the git tree back to the correct state, and applied the commits which were originally meant to be included.

Last week, Jane Ireton, daughter of Chef Community member Doug Ireton, became Chef’s youngest contributor (eight years old!) by making this commit to Chef provisioning: This is, of course, not only awesome and delightful, but exactly what the Chef Community is all about.

As I flew back to Seattle from AWS re:Invent in Las Vegas, I couldn’t help but think about how automation and the cloud have really become the new normal in IT.  And when I say “cloud,” I mean cloud as a proxy for spending fewer calories managing infrastructure and redirecting that energy towards driving innovation.

Thanks to everyone who attended my presentation on The Lean Enterprise today. If you didn’t have a chance to watch it live, you have two chances to see it again. First, by popular demand, we are doing an encore presentation on November 21st, 2014 at 10am GMT.

Hi Chefs, We have just release Chef 10.34.6. This release contains bash 3.1 updated to patch level 23, which provides security updates for Shellshock related vulnerabilities CVE-2014-6271, CVE-2014-6271, CVE-2014-6278, CVE-2014-7186, CVE-2014-7187. You can download this release for Windows using this link: Chef Client 10.34.

On Monday, November 10th, 2014, it was discovered that the contributors section of the Supermarket, including the Curry Bot functions, had been disabled. This resulted in Pull Requests not being properly labeled and made it impossible for users to sign ICLAs and CCLAs.

Company Delivers Industry’s First Policy-Based Orchestration for Automating the Creation and Management of Compute Resources in Data Centers and the Cloud Chef to Demonstrate New Provisioning Capability at AWS re:Invent SEATTLE & LAS VEGAS — November 12, 2014 — Today at AWS re:Invent, Chef, the leader in web-scale IT automation, introduced Chef provisioning, a powerful […]