Is it 'safe' to upgrade to ruby 2.0 by now?

Ruby
1

Hello,

I’d like to know if do you consider safe upgrading all our programs to
ruby 2.0. By now it’s considered ‘stable’ and I’d like to keep up with
‘current development’ in order to avoid
issues that may arise from lagging too much behind. But do you or know
if there are gem issues with ruby 2.0? Some gems might need to get
upgraded, some are active other not…

What’s your opinion on this and which version do you use for
production/test development?

Best Regards,

Panagiotis (atmosx) Atmatzidis

email: [email protected]
URL: http://www.convalesco.org
GnuPG ID: 0x1A7BFEC5
gpg --keyserver pgp.mit.edu --recv-keys 1A7BFEC5

2

I think there’s still an issue with 64-bit 2.0 and Nokogiri, if that
makes a difference to you.

Are you able to provide a list of the gems you’re using? Obviously we
can’t account for ALL gems.

3

hm my nokogiri does not make issues with 64bit … oO, maybe it was
fixed later

@Panagiotis in 2.0 some stuff that was deprecated, was removed like
“iconv”

so its may be safe when you come from 1.9.* but you get more problems
when you come from 1.8 because of some stuff that was added in 1.9.3

4

Hans M. wrote in post #1109174:

hm my nokogiri does not make issues with 64bit … oO, maybe it was
fixed later

I forgot to mention that this was a windows-specific issue. I don’t see
any mention that it’s fixed yet.

5

Hello,

I use nokogiri in one of my scripts, but I don’t run windows so, thanks
for the heads up. Since there are no known major issues I think I can
move my (rvm) default to 2.0 and keep 1.9.3 around just in case.

Thanks

Panagiotis (atmosx) Atmatzidis

email: [email protected]
URL: http://www.convalesco.org
GnuPG ID: 0x1A7BFEC5
gpg --keyserver pgp.mit.edu --recv-keys 1A7BFEC5

6

Per-erik Martin wrote in post #1109258:

I’ve been running ruby 2.0 (p0 first, and now the new patch release) on
linux (intel laptop and raspberry pi) and Mac OS X, without any
problems.

Barring a few incompatibilities with 1.9 (UTF-8 as default encoding
probably the biggest one), it shouldn’t be a problem. (See
Ruby 2.0.0-p0 is released
about this.)

… and of course, you have to check any gems or other external
libraries you’re dependent of, to make sure that they have been updated
for 2.0 (if necessary).

7

I’ve been running ruby 2.0 (p0 first, and now the new patch release) on
linux (intel laptop and raspberry pi) and Mac OS X, without any
problems.

Barring a few incompatibilities with 1.9 (UTF-8 as default encoding
probably the biggest one), it shouldn’t be a problem. (See
http://www.ruby-lang.org/en/news/2013/02/24/ruby-2-0-0-p0-is-released/
about this.)

8

On Thu, May 16, 2013 at 1:57 AM, Panagiotis A.
[email protected] wrote:

I’d like to know if do you consider safe upgrading all our programs to ruby 2.0.

Do your apps’ tests pass under 2.0?

But do you or know if there are gem issues with ruby 2.0? Some gems might need
to get upgraded, some are active other not…

Do the tests of the gems you use pass under 2.0?

That’s where I would start, at least. Nobody but you knows all the
dependencies of your codebase.

9

Panagiotis A. wrote in post #1109170:

Hello,

On windows:
Gosu not ready
Gtk2/3 works

10

Hello,

On 17 Μαϊ 2013, at 16:49 , Hassan S. [email protected]
wrote:

That’s where I would start, at least. Nobody but you knows all the
dependencies of your codebase.

–
Hassan S. ------------------------ [email protected]
Hassan Schroeder | about.me
twitter: @hassan

Yes everything seems to work perfectly well :slight_smile:

Panagiotis (atmosx) Atmatzidis

email: [email protected]
URL: http://www.convalesco.org
GnuPG ID: 0x1A7BFEC5
gpg --keyserver pgp.mit.edu --recv-keys 1A7BFEC5

11

We’ve been running 2.0 in production on Heroku now since it came out. No
issues related to ruby.

On Fri, May 17, 2013 at 6:03 PM, Panagiotis A.