[chef-dev] Re: Accepted RFCs for October 15th

[Aimelyne Mochiron < >]

+1 for the idea of having reports such as this one on RFCs being 
accepted/merged. Just like btm's Developer Office Hours reports, this is very 
useful/convenient to keep on top of things when one's bandwidth is limited, 
as you say. Thanks! :-)

am

On 16 Oct 2014, at 09:18, Noah Kantrowitz 
<
 >
 wrote:

> I think maybe it would be good for the editor team to notify this mailing 
> list when new RFCs are accepted and merged, for those that don't have the 
> bandwidth to keep up with the whole RFC process. Do people feel I should CC 
> the Chef ML too? 
> 
> This week five RFCs have been accepted, all planned for inclusion in Chef 
> 12:
> 
> ## RFC 22: Arbitrary Cookbook Identifiers
> 
> https://github.com/opscode/chef-rfc/blob/master/rfc022-arbitrary-cookbook-identifiers.md
> 
> This defines a new API to manage cookbooks with identifiers other the 
> current three-integer-semver structure in use now.
> 
> ## RFC 23: Chef 12 Attributes Changes
> 
> https://github.com/opscode/chef-rfc/blob/master/rfc023-chef-12-attributes-changes.md
> 
> This defines several new methods on Node to manipulate attributes. This 
> will restore some functionality that was lost during the Chef 11 attributes 
> rewrite, including safely deleting attributes and assigning over an 
> existing hash.
> 
> ## RFC 24: Local Mode Default
> 
> https://github.com/opscode/chef-rfc/blob/master/rfc024-local-mode-default.md
> 
> This outlines plans to change chef-client and knife to use local-mode by 
> default if no server URL is specified.
> 
> ## RFC 25: Multitenant Chef Client Support
> 
> https://github.com/opscode/chef-rfc/blob/master/rfc025-multitenant-chef-client-support.md
> 
> This adds additional configuration options to better support multi tenant 
> Chef Servers, such as Chef Server 12.
> 
> ## RFC 26: Remove HTTP Config Files
> 
> https://github.com/opscode/chef-rfc/blob/master/rfc026-remove-http-config-files.md
> 
> This deprecates a relatively unknown feature whereby chef-client can 
> download its configuration directly from an HTTP server. Given how little 
> this feature is believed to be used, an aggressive deprecation schedule 
> will be used such that the feature will throw a warning in future Chef 11 
> versions and be entirely removed in Chef 12.
> 
> Thats all for this week. If you have thoughts on this bulletin, please let 
> me know!
> 
> --Noah