This morning we’ve released another release candidate for Chef Server 12
(12.0.0-rc3) to address a critical issue related to client permissions on
node objects when upgrading from Open Source Chef Server 11.
The RC can be obtained by visiting http://downloads.getchef.com/chef-server/
Thanks to IRC and GitHub user tbunnyman for reporting the issue and filing
it on the GitHub Issue Tracker .
If you’ve already upgraded from Open Source Chef Server 11 to RC2 (the
first public release from Monday), you can contact Chef Support  and we
can help get your node permissions repaired.
On Tue, Sep 9, 2014 at 10:17 AM, Joseph Smith email@example.com wrote:
As we’ve continued to test this RC, we’ve found a problem with OSC
upgrades - pre-existing nodes don’t have their permissions set correctly in
all cases, which is a pretty serious problem.
The problem is being fixed now, and we’re working on getting a build out
as soon as we can - hopefully today. In the interim, I would strongly
advise not using this RC to test OSC upgrades with.
Thanks for your patience,
QA @ Chef
On Mon, Sep 8, 2014 at 6:38 AM, Stephen Delano firstname.lastname@example.org
This morning I’m pleased to announce the first release candidate of Chef
Server 12. Please head on over to the Chef blog to check out the
announcement  as well as a post  by Adam Jacob that explains the open
source strategy around Chef Server 12. (Hint, it’s all open source)
 Open Source Strategy:
Engineering Lead - Chef Server
Software Development Engineer
1008 Western Avenue
Seattle, WA 98104