Cookbook releases, runit upgrade prep edition


#1

Ohai Chefs,

Ticket CHEF-154 was moved to the cookbooks project and is now COOK-2254.
The COOK-2254 branch that had the runit_service changes I described
earlier this week is now merged into master. The version is "development"
version 0.16.3, and I’m planning on releasing 1.0.0 tomorrow. The
cookbooks releases below are mainly pinning the runit dependency to <=
0.16.2.


5ff16dfb6fe5cf9

It bears repeating that we do not recommend using the master branch of the
GitHub repositories, and instead use the released versions from the
community site. You should also update your own local cookbooks that use
runit_service to the runit cookbook version 0.16.2 (or to whatever
version you’re currently using) until you’re ready to modify them for the
changes in COOK-2254. The ticket to track Opscode’s cookbook changes for
this update is COOK-2253. It will have sub-task tickets reflecting the
work required on an individual cookbook ticket. For now, the affected
cookbooks pin the version.

Note that chef-client and nginx cookbooks do not depend on runit, because
it is not the default way these cookbooks set up the service. Instead they
use suggests and recommends, which aren’t actually implemented for
cookbook downloading, and are informational only.

application_ruby v1.0.10:

  • [COOK-2260] - pin runit version

chef-client v2.1.8:

  • [COOK-2192] - Add option to use cron_d resource for cron management
  • [COOK-2261] - pin runit dependency

djbdns v1.0.2:

  • [COOK-2262] - pin runit dependency

git v2.1.4:

  • [COOK-2110] - initial test-kitchen support (only available in GitHub
    repository).
  • [COOK-2253] - pin runit dependency

jira v0.9.2:

  • [COOK-2265] - pin runit dependency

memcached v1.2.0:

  • [COOK-1469] - include yum epel recipe on RHEL 5 (introduces yum
    cookbook dependency)
  • [COOK-2202] - Fix typo in previous ticket/commits
  • [COOK-2266] - pin runit dependency

nginx v1.2.0:

  • [COOK-1752] - Add headers more module to the nginx cookbook
  • [COOK-2209] - nginx source recipe should create web user before
    creating directories
  • [COOK-2221] - make nginx::source compatible with gentoo
  • [COOK-2267] - add version for runit recommends

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


#2

We’re going to hold on releasing 1.0 as we may have a solution to allow
better backwards compatibility, and not require modification of existing
cookbooks. We still recommend pinning the version until you’re ready to
upgrade and test in a non-production environment, though.

On 1/24/13 10:48 PM, “Joshua Timberman” joshua@opscode.com wrote:

Ohai Chefs,

Ticket CHEF-154 was moved to the cookbooks project and is now COOK-2254.
The COOK-2254 branch that had the runit_service changes I described
earlier this week is now merged into master. The version is "development"
version 0.16.3, and I’m planning on releasing 1.0.0 tomorrow. The
cookbooks releases below are mainly pinning the runit dependency to <=
0.16.2.

https://github.com/opscode-cookbooks/runit/commit/4b52f63711eb633accacb616
3
5ff16dfb6fe5cf9

It bears repeating that we do not recommend using the master branch of the
GitHub repositories, and instead use the released versions from the
community site. You should also update your own local cookbooks that use
runit_service to the runit cookbook version 0.16.2 (or to whatever
version you’re currently using) until you’re ready to modify them for the
changes in COOK-2254. The ticket to track Opscode’s cookbook changes for
this update is COOK-2253. It will have sub-task tickets reflecting the
work required on an individual cookbook ticket. For now, the affected
cookbooks pin the version.

Note that chef-client and nginx cookbooks do not depend on runit, because
it is not the default way these cookbooks set up the service. Instead they
use suggests and recommends, which aren’t actually implemented for
cookbook downloading, and are informational only.

application_ruby v1.0.10:

  • [COOK-2260] - pin runit version

chef-client v2.1.8:

  • [COOK-2192] - Add option to use cron_d resource for cron management
  • [COOK-2261] - pin runit dependency

djbdns v1.0.2:

  • [COOK-2262] - pin runit dependency

git v2.1.4:

  • [COOK-2110] - initial test-kitchen support (only available in GitHub
    repository).
  • [COOK-2253] - pin runit dependency

jira v0.9.2:

  • [COOK-2265] - pin runit dependency

memcached v1.2.0:

  • [COOK-1469] - include yum epel recipe on RHEL 5 (introduces yum
    cookbook dependency)
  • [COOK-2202] - Fix typo in previous ticket/commits
  • [COOK-2266] - pin runit dependency

nginx v1.2.0:

  • [COOK-1752] - Add headers more module to the nginx cookbook
  • [COOK-2209] - nginx source recipe should create web user before
    creating directories
  • [COOK-2221] - make nginx::source compatible with gentoo
  • [COOK-2267] - add version for runit recommends

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


#3

The master branch is updated with changes that allow notifications with a
"service" resource (instead of “runit_service”) for better backwards
compatibility. The other changes mentioned below are reflected in the
CHANGELOG.md.

We’re planning to release version 1.0.0 on Monday.

Cheers,
Joshua

On 1/25/13 10:56 AM, “Joshua Timberman” joshua@opscode.com wrote:

We’re going to hold on releasing 1.0 as we may have a solution to allow
better backwards compatibility, and not require modification of existing
cookbooks. We still recommend pinning the version until you’re ready to
upgrade and test in a non-production environment, though.

On 1/24/13 10:48 PM, “Joshua Timberman” joshua@opscode.com wrote:

Ohai Chefs,

Ticket CHEF-154 was moved to the cookbooks project and is now COOK-2254.
The COOK-2254 branch that had the runit_service changes I described
earlier this week is now merged into master. The version is "development"
version 0.16.3, and I’m planning on releasing 1.0.0 tomorrow. The
cookbooks releases below are mainly pinning the runit dependency to <=
0.16.2.

https://github.com/opscode-cookbooks/runit/commit/4b52f63711eb633accacb61
6
3
5ff16dfb6fe5cf9

It bears repeating that we do not recommend using the master branch of
the
GitHub repositories, and instead use the released versions from the
community site. You should also update your own local cookbooks that use
runit_service to the runit cookbook version 0.16.2 (or to whatever
version you’re currently using) until you’re ready to modify them for the
changes in COOK-2254. The ticket to track Opscode’s cookbook changes for
this update is COOK-2253. It will have sub-task tickets reflecting the
work required on an individual cookbook ticket. For now, the affected
cookbooks pin the version.

Note that chef-client and nginx cookbooks do not depend on runit, because
it is not the default way these cookbooks set up the service. Instead
they
use suggests and recommends, which aren’t actually implemented for
cookbook downloading, and are informational only.

application_ruby v1.0.10:

  • [COOK-2260] - pin runit version

chef-client v2.1.8:

  • [COOK-2192] - Add option to use cron_d resource for cron management
  • [COOK-2261] - pin runit dependency

djbdns v1.0.2:

  • [COOK-2262] - pin runit dependency

git v2.1.4:

  • [COOK-2110] - initial test-kitchen support (only available in GitHub
    repository).
  • [COOK-2253] - pin runit dependency

jira v0.9.2:

  • [COOK-2265] - pin runit dependency

memcached v1.2.0:

  • [COOK-1469] - include yum epel recipe on RHEL 5 (introduces yum
    cookbook dependency)
  • [COOK-2202] - Fix typo in previous ticket/commits
  • [COOK-2266] - pin runit dependency

nginx v1.2.0:

  • [COOK-1752] - Add headers more module to the nginx cookbook
  • [COOK-2209] - nginx source recipe should create web user before
    creating directories
  • [COOK-2221] - make nginx::source compatible with gentoo
  • [COOK-2267] - add version for runit recommends

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