[chef-dev] Re: CHEF-3788: More restrictive gem dependencies?

[Mike < >]

I'm a big fan of looking at each dependency and seeing if they
explicitly declare that:
a) they follow SemVer
b) they are past 1.0

In that case, using '~> 1.0' is great. Using anything under 1.0, i.e.
moneta, should probably be nailed to the working version, until it's a
problem and deserves revisiting.

-M

On Thu, Jan 24, 2013 at 5:46 PM, Bryan McLellan 
<
 >
 wrote:
> Grégory has suggested in CHEF-3788  that the gem dependencies be more 
> restrictive after the recent incident where Moneta 0.7.0 was released and 
> the API was not backward compatible (CHEF-3721).
>
> In the past we've been restrictive about gems that have had similar issues, 
> particularly with slow responses, like JSON, but overall we have been more 
> optimistic to get the benefits of new releases of libraries without having 
> to make a new release of Chef. In the case of JSON, we occasionally have 
> tickets where people want to bump the version because we're starting to 
> cause dependency resolution failures with other tools that use Chef as a 
> library.
>
> But maybe it would help if we were at least pessmistic about major version 
> changes, e.g. ~> x.y.  Anyone have other opinions to add?
>
> ---
> Bryan McLellan | opscode | technical program manager, open source
> (c) 206.607.7108 | (t) @btmspox | (b) http://blog.loftninjas.org
>
> http://tickets.opscode.com/browse/CHEF-3788
> http://tickets.opscode.com/browse/CHEF-3721
>
>