Cookbook Releases just for you


#1

I tried to get this all completed in time for Valentine’s day, but as
you can see, there was a lot to do.

Total cookbooks released: 19.
Total tickets resolved: 47.
Average amount of love given to contributors: Immeasurable!

Thank you everyone who contributed to these releases. Andrea Campi,
Jamie Winsor, and Bryan Berry have put in a lot of hard work improving
some of our most popular cookbooks, apache2, mysql, nginx and java,
particularly. Thanks guys, you’re awesome.

With these releases done, we’re down to only 10 issues that have been
triaged and are awaiting a merge, and 7 issues that are resolved but
not triaged yet. This puts us in a pretty good place to start the
effort to move each of the cookbooks out of the monolithic cookbooks
repository into their own separate repository.

While we do send out these cookbook release announcements to the list
periodically, you can keep up with cookbook development on an
individual cookbook basis, as well. If you have an Opscode community
site user, you can follow specific cookbooks, and set up notification
settings. Simply click the big orange “Follow” button on a cookbook’s
page, and go to your profile to edit when you get email notifications.

And now, the releases:

apache2 v1.1.0

  • [COOK-861] - Add mod_perl and apreq2
  • [COOK-941] - fix mod_auth_openid on FreeBSD
  • [COOK-1021] - add a commented-out LoadModule directive to keep apxs happy
  • [COOK-1022] - consistency for icondir attribute
  • [COOK-1023] - fix platform test for attributes
  • [COOK-1024] - fix a2enmod script so it runs cleanly on !bash
  • [COOK-1026] - fix error_log location on FreeBSD

apt v1.3.0, v1.3.2

v1.3.2:

  • [COOK-1040] - actually run apt-get update w/ not_if

v1.3.0:

  • [COOK-533] - add support for deb and deb_src repos with
    apt_repository provider
  • [COOK-593] - switched from apt-cacher to apt-cacher-ng to better
    support multiple distributions.
  • [COOK-890] - Fix distribution for zenoss repo in apt README
  • [COOK-891] - Make add the default action for apt_repository
  • [COOK-947] - Add chef-solo support for recipe[apt::cacher-client].

bluepill v1.0.0

This cookbook has been relatively stable and is “feature complete” so
it is graduated to a 1.0.0 release.

  • [COOK-943] - add init script for freebsd

chef-client v1.1.0

  • [COOK-909] - trigger upstart on correct event
  • [COOK-795] - add windows support with winsw
  • [COOK-798] - added recipe to run chef-client as a cron job
  • [COOK-986] - don’t delete the validation.pem if chef-server recipe
    is detected

djbdns v0.99.2

  • [COOK-1042] - Corrected a syntax error in axfr.
  • [COOK-740] - use correct directory for tinydns root data

gecode v1.2.0

  • [COOK-663] - upgrade libgecode-dev package
  • [COOK-778] - update ld.so.conf

java v1.4.0

oracle, make openjdk default, add java_ark LWRP.

  • [COOK-520] - ArchLinux support
  • [COOK-858] - numerous updates: handle jdk6 and 7, switch from sun to
  • [COOK-942] - FreeBSD support

memcached v1.0.0

  • [COOK-706] - Additional info in README
  • [COOK-828] - Package for RHEL systems

munin v1.0.2

  • [COOK-920] - FreeBSD support

mysql v1.2.4

  • [COOK-992] - fix FATAL nameerror
  • [COOK-827] - mysql:server_ec2 recipe can’t mount data_dir
  • [COOK-945] - FreeBSD support

nginx

  • [COOK-818] - add “application/json” per RFC.
  • [COOK-870] - bluepill init style support
  • [COOK-957] - Compress application/javascript.
  • [COOK-981] - Add reload support to NGINX service

ntp v1.1.2

  • [COOK-952] - freebsd support
  • [COOK-949] - check for any virtual system not just vmware

php v1.0.2

  • [COOK-993] Add mhash-devel to centos php source libs
  • [COOK-989] - bump version of php to 5.3.10
  • Also download the .tar.gz instead of .tar.bz2 as bzip2 may not be in
    the base OS (e.g., CentOS 6 minimal)

powershell v1.0.4

  • [COOK-988] - powershell never exits

reprepro v0.2.4

  • [COOK-922] - add allow to data bag
  • Update the readme with data bag info

sudo v1.0.2

  • [COOK-903] - freebsd support

thrift v1.0.0

  • [COOK-904] - install version 0.8, requires Ubuntu 11.10

transmission

  • [COOK-729] - transmission_torrent_file doesn’t work for more than
    a single torrent
  • [COOK-732] - link to file in swarm not created if torrent already
    completely downloaded

windows v1.2.10

  • [COOK-939] - add type parameter to windows_registry to allow
    binary registry keys.
  • [COOK-940] - refactor logic so multiple values get created.


Opscode, Inc
Joshua Timberman, Technical Program Manager
IRC, Skype, Twitter, Github: jtimberman


#2

On Fri, Feb 17, 2012 at 01:14, Joshua Timberman joshua@opscode.com wrote:

While we do send out these cookbook release announcements to the list
periodically, you can keep up with cookbook development on an
individual cookbook basis, as well. If you have an Opscode community
site user, you can follow specific cookbooks, and set up notification
settings. Simply click the big orange “Follow” button on a cookbook’s
page, and go to your profile to edit when you get email notifications.

I think these automated notification emails would be much more useful
if they included some kind of changelog.

Regards,


Ronan Amicel

«« Twitter overload?
»» Get your daily summary at http://focus.io/


#3

I think these automated notification emails would be much more useful
if they included some kind of changelog.

Besides the closed tickets they list for each cookbook?

-J


#4

On Fri, Feb 17, 2012 at 02:28, Jason J. W. Williams <
jasonjwwilliams@gmail.com> wrote:

I think these automated notification emails would be much more useful
if they included some kind of changelog.

Besides the closed tickets they list for each cookbook?

Joshua’s emails are fine.

I’m talking about the automated notifications, which are pretty
content-free. Here is an example:

Hello Ronan Amicel,

A new version of the nginx cookbook has been uploaded to the Opscode
community site.
You can find the new version at
https://community.opscode.com/cookbooks/nginx.
Thanks,
The Opscode Team


Ronan Amicel

«« Twitter overload?
»» Get your daily summary at http://focus.io/


#5

@joshua,

As mentioned about the bluepill v1.0.0 as:
""" bluepill v1.0.0

This cookbook has been relatively stable and is “feature complete” so
it is graduated to a 1.0.0 release. “”""

I think its still buggy with the chef-server cookbook installation via rubygems.


I installed chef_server on ec2 ubuntu10.04 using rubygems n bluepill init style.

After installing the packages, bluepill blows up.
The following is the debugg-ed log.

https://gist.github.com/1847128

Google around and found one similar issue at bluepill’s issue at GH.
https://github.com/arya/bluepill/issues/132

Are these both problem is the same one?

Why its failing?


@millisami
~ Sachin Sagar Rai
Ruby on Rails Developer
http://tfm.com.np
http://nepalonrails.tumblr.com
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)

On Friday, February 17, 2012 at 7:20 AM, Ronan Amicel wrote:

On Fri, Feb 17, 2012 at 02:28, Jason J. W. Williams <jasonjwwilliams@gmail.com (mailto:jasonjwwilliams@gmail.com)> wrote:

I think these automated notification emails would be much more useful
if they included some kind of changelog.

Besides the closed tickets they list for each cookbook?

Joshua’s emails are fine.

I’m talking about the automated notifications, which are pretty content-free. Here is an example:

Hello Ronan Amicel,
A new version of the nginx cookbook has been uploaded to the Opscode community site.
You can find the new version at https://community.opscode.com/cookbooks/nginx.
Thanks,
The Opscode Team


Ronan Amicel

«« Twitter overload?
»» Get your daily summary at http://focus.io/


#6

On Thu, Feb 16, 2012 at 8:35 PM, Ronan Amicel ronan.amicel@gmail.com wrote:

I’m talking about the automated notifications, which are pretty
content-free. Here is an example:

Hello Ronan Amicel,
A new version of the nginx cookbook has been uploaded to the Opscode
community site.
You can find the new version at
https://community.opscode.com/cookbooks/nginx.

Ronan, I’ve opened an internal feature request to improve this, but I
had a hard time designing it. What content do you have in mind?

A diff either in the email or a link to a diff-tool built into the web
site sounds great in theory, but I can see many situations where it
isn’t going to be helpful because of major changes or confusing
changes when you don’t have the convenience of the history of SCM
commits.

A changelog would require a new metadata mechanism, such as a a
changelog.md file with a schema for entries so that the website could
parse it and add the changes to the email. Then you would have to get
authors to use the mechanism. This could be encouraged by adding a
"The cookbook author did not provide a changelog entry for this
release." message, but getting everyone to do it right might not
provide a lot of value for the cost. What first comes to mind for me
is the debian changelog, which provides all the features you want, but
requires a number of tools, syntax checking, and a community
requirement for its completion for it to be that useful.

Any other ideas?

Bryan


#7

On Fri, Feb 17, 2012 at 18:19, Bryan McLellan btm@loftninjas.org wrote:

On Thu, Feb 16, 2012 at 8:35 PM, Ronan Amicel ronan.amicel@gmail.com
wrote:

I’m talking about the automated notifications, which are pretty
content-free. Here is an example:

Hello Ronan Amicel,
A new version of the nginx cookbook has been uploaded to the Opscode
community site.
You can find the new version at
https://community.opscode.com/cookbooks/nginx.

Ronan, I’ve opened an internal feature request to improve this, but I
had a hard time designing it. What content do you have in mind?

At least, it should include the current and previous version numbers.

A diff either in the email or a link to a diff-tool built into the web

site sounds great in theory, but I can see many situations where it
isn’t going to be helpful because of major changes or confusing
changes when you don’t have the convenience of the history of SCM
commits.

A changelog would require a new metadata mechanism, such as a a
changelog.md file with a schema for entries so that the website could
parse it and add the changes to the email. Then you would have to get
authors to use the mechanism. This could be encouraged by adding a
"The cookbook author did not provide a changelog entry for this
release." message, but getting everyone to do it right might not
provide a lot of value for the cost. What first comes to mind for me
is the debian changelog, which provides all the features you want, but
requires a number of tools, syntax checking, and a community
requirement for its completion for it to be that useful.

Any other ideas?

Some packages already include a changelog section in their README file. Now
that it is displayed on the community site, I can quickly get a sense of
what’s new by following the link in the email and scanning the page. For
example: http://community.opscode.com/cookbooks/nginx That’s good enough
for me, without needing to add new metadata (although standardization and
guidelines may be useful).

However, other packages don’t do this, and I am left to wonder what’s new
in this version, and my best hope is to to the source on github and read
the commit messages and/or diff between tags (or wait for Joshua’s email on
this list). For example: http://community.opscode.com/cookbooks/apache


Ronan Amicel

«« Twitter overload?
»» Get your daily summary at http://focus.io/