Best Practices

@matteodepalo or you would use git blame and deduce the fact from the commit message.
My sole itch with this rule as it stated currently, is that it makes it appear as frequent gem updates were a good thing. We review each change made to the system yet accept new code injected via a gem update on face value. 

Few gems follow the semantic versioning in the ruby world.  Even if they say the do often they are not. For example consider how most rails security releases have the tendency of introducing unrelated changes. By lambasting on any possible versions description that may be present in a Gemfile I feel we are encouraging upgrade whenever I want whatever I want kind of behaviour. 

I do not expect every gem to be locked to a particular version. Rather that we should not criticise whatever version strings are added or present. If it makes the upgrade process harder, so be it.