Earlier today, we made Supermarket the official community site and the source of http://api.berkshelf.com. About 30 minutes after the transition to the new site was complete we started to get a few reports of issues with Berkshelf v2.x reporting errors.

Continuing our series of posts on new engineering (or engineering-related) additions to the Chef team, today we’re highlighting a number of folks who joined over the past week.

The second entry from our upcoming collection of editorials entitled The Quiet Revolutionaries comes from our friend Kate Matsudaira, founder of popforms. Kate takes a look at the various degrees of speed and scale at play in IT today, and gives her guidance on delivering quality software quickly, beginning with the minimum viable product.

Ohai Chefs! Due to popular demand, Chef Software is moving its COOK project issue management away from JIRA and onto GitHub issues. This will help us streamline our contribution process, making it easier for the community to submit contributions to Chef maintained cookbooks. Chef maintained cookbooks have always been hosted on GitHub.

We are excited to announce the Grand Opening of Supermarket – the new Chef community site! On July 7th, 2014 at 12:00 PM PDT (2014–07–07 19:00 UTC) we will close the old community site and redirect all traffic to https://supermarket.getchef.com. At that time, Supermarket will be the official community site.

Hi! This is a long blog post, but it has a few important action items at its conclusion. If you care about the evolution of the Chef Community, or are considering going to the Community Summit, you should totally read it.

Today we launched the refreshed Learn Chef website. Based on your feedback, we wanted to: Provide a safe learning environment that’s easy to experiment in. Introduce the concepts gradually & provide hands-on experience along the way. Provide a streamlined experience that’s tailored to the server environment you care about most.

At 17:11 UTC, the Rails security team publicized CVE-2014-3482 and CVE-2014-3483. In short, this vulnerability is related to the PostgreSQL adapater in ActiveRecord. A bug in the SQL quoting code could allow an attacker to carefully craft a request and execute a SQL injection.

We had a ton of fun at Velocity last week! Thank you to all those who stopped by our booth, our hack, our sessions, or stopped us in the hallway for a chat. And thank you to the whole O’Reilly team for putting on another delightful conference.