A note about Chef 12.0.0.alpha.0


#1

Hi Chefs,

I just pushed Chef 12.0.0.alpha.0 to rubygems. Since lots of you follow our activity on github and rubygems (and will notice this release), I’d like to give you an explanation of what’s in this release and our motivation for shipping it now.

First of all, very few of the changes we’ve agreed upon in the RFC process (https://github.com/opscode/chef-rfc/pull/22) have been implemented. If you’re interested in what has changed since we started merging code for 12.0, see the release notes (in progress) here: https://github.com/opscode/chef/blob/bfe0ac206c5723637772d8b9b3a48a4d94f5c21f/RELEASE_NOTES.md

Since there’s still so much left to do, we normally wouldn’t have made an official release of any sort at this point. However, we’ve recently added some library code to the chef-dk application which relies on changes that were in master of chef. Due to some quirks of our build tooling and bundler, ChefDK (the package) doesn’t build correctly when using bundler to fetch dependencies from git. So in order to keep our Ci pipeline happy, we’ve released the 12.0.0.alpha.0 gem to work around these limitations. Note that this will only affect the version of chef that chef-dk (the app) uses as a library, and this change will only show up in nightly builds for now. The knife, chef-client, and other binaries that come with ChefDK will continue to be built from the stable branch.

Let me know if you have any questions,


Daniel DeLeo


#2

Btw: what about Chef 11.14.0?

I have seen the tag on the git repo but its not pushed to rubygems yet.

Just curious… :slight_smile:
Am 31.07.2014 01:44 schrieb “Daniel DeLeo” dan@kallistec.com:

Hi Chefs,

I just pushed Chef 12.0.0.alpha.0 to rubygems. Since lots of you follow
our activity on github and rubygems (and will notice this release), I’d
like to give you an explanation of what’s in this release and our
motivation for shipping it now.

First of all, very few of the changes we’ve agreed upon in the RFC process
(https://github.com/opscode/chef-rfc/pull/22) have been implemented. If
you’re interested in what has changed since we started merging code for
12.0, see the release notes (in progress) here:
https://github.com/opscode/chef/blob/bfe0ac206c5723637772d8b9b3a48a4d94f5c21f/RELEASE_NOTES.md

Since there’s still so much left to do, we normally wouldn’t have made an
official release of any sort at this point. However, we’ve recently added
some library code to the chef-dk application which relies on changes that
were in master of chef. Due to some quirks of our build tooling and
bundler, ChefDK (the package) doesn’t build correctly when using bundler to
fetch dependencies from git. So in order to keep our Ci pipeline happy,
we’ve released the 12.0.0.alpha.0 gem to work around these limitations.
Note that this will only affect the version of chef that chef-dk (the app)
uses as a library, and this change will only show up in nightly builds for
now. The knife, chef-client, and other binaries that come with ChefDK
will continue to be built from the stable branch.

Let me know if you have any questions,


Daniel DeLeo


#3

On Wednesday, July 30, 2014 at 10:34 PM, Torben Knerr wrote:

Btw: what about Chef 11.14.0?
I have seen the tag on the git repo but its not pushed to rubygems yet.
Just curious… :slight_smile:

After pushing the 11.14.0 tag, we ran some more integration tests against the package that would have been 11.14.0 and discovered a bug that only occurs in some rare circumstances. We might end up releasing skipping 11.14.0 and going right to 11.14.2 with the fix.


Daniel DeLeo


#4

On Wed Jul 30 23:07:14 2014, Daniel DeLeo wrote:

On Wednesday, July 30, 2014 at 10:34 PM, Torben Knerr wrote:

Btw: what about Chef 11.14.0?
I have seen the tag on the git repo but its not pushed to rubygems yet.
Just curious… :slight_smile:

After pushing the 11.14.0 tag, we ran some more integration tests against the package that would have been 11.14.0 and discovered a bug that only occurs in some rare circumstances. We might end up releasing skipping 11.14.0 and going right to 11.14.2 with the fix.

Since I cheated and pushed a non-annotated tag, I deleted the old tag
and added an annotated 11.14.0, which should be the final version we go
with. Unless there’s another show stopper somewhere that’ll be the
final version we push, and if there’s a show stopper we’d have to retag
as 11.14.2.