because we all share ...

undefined clue 'adversity' for nil:nil (NameError)

Why You Should Never Change API on a Minor Release

In this case, my pain is Chef; as 0.7.0 came out we were rocking with metadata.rb, as I wasn’t paying attention and reading release documentation properly suddenly that doesn’t do squat, and everything is in metadata.json. I’m sure there was something in one of the release notes that I omitted, however it brings up a valid point that Opscode has broken many times (I am only mentioning these 2) in the .7 release cycle

They have repeatedly broken the basic idea of not making major changes in a minor release, such as this, or when they re-wrote the bootstrap system; and then neutered the old system so you had to use the old bootstrap tarball (which is the only reason I am not up in arms).

… However, if you want to do things like this, you should release a new major version and allow people to get used to the major changes. There are always growing pains with anything new, different, … however the past has taught us that you should not make stupid major changes to a structure without a major release.

Opscode has made this much smoother since the original post of this message and they have delivered a much better product then this post originally ranted about.

Comments