As from a week ago, Fog officially dropped support for Ruby 1.9.3 (commit
on Fog
<https://github.com/fog/fog/commit/8a413ef54a82e902c59e1e277a38ffe91a466968>
).
IMHO, that means Foreman has to decide either we pin down to a specific
version of Fog, or we begin moving our project toward support for Ruby 2.0+.
Not doing either of those options will lead to a dependency mess (and
eventually a broken code).
Comments? Ideas?
Shim.
Sure, could do. Refactor #8884: Drop Ruby 1.9.3 support - Foreman tracks it,
we'd need a plan for each listed OS.
···
On 06/10/15 09:57, sshtein@redhat.com wrote:
> As from a week ago, Fog officially dropped support for Ruby 1.9.3 (commit
> on Fog
>
> ).
>
> IMHO, that means Foreman has to decide either we pin down to a specific
> version of Fog, or we begin moving our project toward support for Ruby 2.0+.
–
Dominic Cleal
dominic@cleal.org
> As from a week ago, Fog officially dropped support for Ruby 1.9.3 (commit
> on Fog
> <https://github.com/fog/fog/commit/8a413ef54a82e902c59e1e277a38ffe91a466968>
> ).
>
> IMHO, that means Foreman has to decide either we pin down to a specific
> version of Fog, or we begin moving our project toward support for Ruby 2.0+.
> Not doing either of those options will lead to a dependency mess (and
> eventually a broken code).
>
> Comments? Ideas?
>
> My assumption is that rails 4.x upgrade also include a new version of ruby
2.x?
Ohad
···
On Tue, Oct 6, 2015 at 11:57 AM, wrote:
Shim.
–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Would we want to use the existing Rails 4 SCL? If so we need ruby 2.2.
https://www.softwarecollections.org/en/scls/rhscl/rh-ror41/
David
···
On Tue, Oct 6, 2015 at 5:02 AM, Ohad Levy wrote:
On Tue, Oct 6, 2015 at 11:57 AM, sshtein@redhat.com wrote:
As from a week ago, Fog officially dropped support for Ruby 1.9.3 (commit
on Fog
https://github.com/fog/fog/commit/8a413ef54a82e902c59e1e277a38ffe91a466968
).
IMHO, that means Foreman has to decide either we pin down to a specific
version of Fog, or we begin moving our project toward support for Ruby 2.0+.
Not doing either of those options will lead to a dependency mess (and
eventually a broken code).
Comments? Ideas?
My assumption is that rails 4.x upgrade also include a new version of
ruby 2.x?
Ohad
Shim.
–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.