Chef 0.7.14 / Ohai 0.3.6: Monday Release


#1

Hi all,

Just a note to say that we’ve closed the final tickets for Chef 0.7.14
and Ohai 0.3.6 and will be looking to release Monday next week.

Current release notes:
Bug

[CHEF-454] - Centos4 yum provider failure
[CHEF-565] - dpkg provider fails at packages with a dash in it,
causing packages to be re-installed on every chef run
[CHEF-570] - Portage package provider uses wrong regexp in
load_current_resource
[CHEF-577] - provider.rb doesn’t give @definitions a default value of
Hash.new, causing epic fail in resource DSL
[CHEF-588] - RC is missing debugging info in find_preferred_file
[CHEF-591] - if service doesn’t have a status command, process table
inspection fails in simple service provider
[CHEF-593] - deploy resource is not idempotent
[CHEF-602] - in deploy provider, callback-defined resources are
executed in all subsequent callbacks
[CHEF-603] - deploy: gems.yml support
[CHEF-604] - deploy: sudo / run command handler support
[CHEF-614] - LWRP undefined local variable or method `new_resource’
[CHEF-619] - Mixlib-* gems installed from gemcutter.org have too
restrictive permissions
[CHEF-621] - LWRP dynamic attribute methods are Ruby 1.9 incompatible
and cause warnings in 1.8
[CHEF-628] - Deploy resource removes newest release instead of oldest
Improvement

[CHEF-620] - LWRP components should be shown in Web UI
[CHEF-622] - Gem Package resource/provider shouldn’t silently ignore
the options attribute

Please actively test gems built from opscode/master [1] or contact me
off-list if you need gems hosted.

[1] http://github.com/opscode/chef/tree/master


Arjuna Christensen, Software Development Engineer
Opscode, Inc.
E: aj@opscode.com


#2

How close does this get us to 0.8?

On Wed, Oct 21, 2009 at 1:15 PM, Arjuna Christensen aj@opscode.com wrote:

Hi all,
Just a note to say that we’ve closed the final tickets for Chef 0.7.14 and
Ohai 0.3.6 and will be looking to release Monday next week.
Current release notes:

Bug

[CHEF-454] - Centos4 yum provider failure
[CHEF-565] - dpkg provider fails at packages with a dash in it, causing
packages to be re-installed on every chef run
[CHEF-570] - Portage package provider uses wrong regexp in
load_current_resource
[CHEF-577] - provider.rb doesn’t give @definitions a default value of
Hash.new, causing epic fail in resource DSL
[CHEF-588] - RC is missing debugging info in find_preferred_file
[CHEF-591] - if service doesn’t have a status command, process table
inspection fails in simple service provider
[CHEF-593] - deploy resource is not idempotent
[CHEF-602] - in deploy provider, callback-defined resources are executed in
all subsequent callbacks
[CHEF-603] - deploy: gems.yml support
[CHEF-604] - deploy: sudo / run command handler support
[CHEF-614] - LWRP undefined local variable or method `new_resource’
[CHEF-619] - Mixlib-* gems installed from gemcutter.org have too restrictive
permissions
[CHEF-621] - LWRP dynamic attribute methods are Ruby 1.9 incompatible and
cause warnings in 1.8
[CHEF-628] - Deploy resource removes newest release instead of oldest

Improvement

[CHEF-620] - LWRP components should be shown in Web UI
[CHEF-622] - Gem Package resource/provider shouldn’t silently ignore the
options attribute

Please actively test gems built from opscode/master [1] or contact me
off-list if you need gems hosted.
[1] http://github.com/opscode/chef/tree/master

Arjuna Christensen, Software Development Engineer
Opscode, Inc.
E: aj@opscode.com


#3

On Wed, Oct 21, 2009 at 10:34 AM, Bryan Liles bryan@osesm.com wrote:

How close does this get us to 0.8?

Once we ship 0.7.14, we’ll have the current 0.8 branch become the
master. Assuming there are no critical big fixes that require an
0.7.16, the next release will be 0.8.0.

The current status of 0.8.0 is that the API is working, the Web UI is
still in flux, and it hasn’t had much documentation written about new
features yet. Our goal is to get it out ASAP, but we want to make
sure it’s a solid release.

Adam


Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: adam@opscode.com


#4

On Wed, Oct 21, 2009 at 9:40 PM, Adam Jacob adam@opscode.com wrote:

On Wed, Oct 21, 2009 at 10:34 AM, Bryan Liles bryan@osesm.com wrote:

How close does this get us to 0.8?

Once we ship 0.7.14, we’ll have the current 0.8 branch become the
master. Assuming there are no critical big fixes that require an
0.7.16, the next release will be 0.8.0.

The current status of 0.8.0 is that the API is working, the Web UI is
still in flux, and it hasn’t had much documentation written about new
features yet. Our goal is to get it out ASAP, but we want to make
sure it’s a solid release.

Excellent!

Keep up the good work chaps!

Adam


Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: adam@opscode.com


$ echo “kpfmAdpoofdufevq/dp/vl” | perl -pe ‘s/(.)/chr(ord($1)-1)/ge’