Locking Rubby Gems versions for use in a variety of environments.

[carlosdelfino]

What/why?

In my development environment I have several projects each one works with a different version of gems which sometimes leaves me in doubt if it is the version that is causing a certain bug, to avoid this, I fixed the versions of the gems where I identified that it would be important In rich versions environments.

How was it tested?

bundle update
bundle exec jekyll s

[ilg-ul]

I am successfully using jekyll 3.3.0? why do you need to lock it at 3.2?

[carlosdelfino]

I renamed the branch and the pull-request closed.

[carlosdelfino]

To solve the pluign error that informs the use of depreciated function.

[ilg-ul]

as environment, I have a different approach, I do not have ruby/jekyll/etc installed in the system, but I have a separate homebrew instance for jekyll, which I use to generate all my sites, so I have no problems with different applications requiring different gems.

[ilg-ul]

To solve the pluign error that informs the use of depreciated function.

you mean the warning? this is harmless.

[carlosdelfino]

you mean the warning? this is harmless.

yes, not have a problems about this. Only for eliminate the mensage and run clean.

[carlosdelfino]

I make a new pull-request #26 because github close this automatically where I rename the branch.