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

[Bryan McLellan < >]

On Thu, Jan 24, 2013 at 6:19 PM, Julian C. Dunn 
<
 >
 wrote:
> My problem with being so restrictive about Gem versions is that few people
> actually go back periodically and see if such restrictions are still
> necessary.

Right. It's a bunch of work, which is why we've hesitated. Chef
releases, even if we're just including a couple commits, take a lot of
work and time to get everything tested and all the packages built.

> I was actually just working my way up to an e-mail about this, because I'm
> in the middle of packaging Chef for Fedora and they have far newer versions
> of Gems -- like JSON -- than Chef's gemspec would suggest work.
>
> I'm pretty sure the extremely pessimistic pinning on JSON can be removed,
> but how can I be sure? Is it just a matter of running Chef's unit tests and
> if they pass on the new Gem, I can submit a pull request to remove it?

Well, to increase the version it's just been a matter of opening a
ticket with a PR that says "I've tested a chef-client run with this
version and it seemed fine"

For example: http://tickets.opscode.com/browse/CHEF-1548
or for example: http://tickets.opscode.com/browse/CHEF-2031

Here is the most recent un-finished JSON dependency ticket:
http://tickets.opscode.com/browse/CHEF-3712
This is probably a dupe provided we get up to at least 1.6.5:
http://tickets.opscode.com/browse/CHEF-2960

Bryan