JRuby 1.0.x end-of-life

I think it’s come time for us to consider the 1.0 line finished. With
all the work that’s gone into JRuby 1.1, and the massive performance and
compatibility differential, I can’t see us ever putting time into
another 1.0.x release. We strongly recommend everyone use JRuby 1.1+,
and no work has been done on the 1.0 line in many months.

The only worry we have is the fact that JRuby 1.1 depends on Java 1.5,
but we simply don’t have resources to maintain 1.0 into the future.

This email is notification that we’re very likely to end-of-life the 1.0
line and mark all remaining open bugs for 1.0.x as “never to be fixed”
since in all cases they’ve been fixed for a long time in 1.1+. If you
have specific issues that prevent you from upgrading to JRuby 1.1+,
please let us know and we’ll try to work with you.

  • Charlie

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

I haven’t hit any problems with 1.0, but haven’t upgraded to 1.1,
either. I’ve been thinking about doing so, but if it requires Java 1.5,
then I will not be able to. I’ve been writing JMX utilities for Weblogic
8.1 which requires me to run with a 1.4 JVM. I could write my Weblogic
9.2 scripts with JRuby 1.1, but part of the reason I’m using JRuby
instead of WLST is to minimize differences between the two platforms as
I can when writing my scripts. Using different versions of JRuby won’t
help much in that regard. :-\

Given that I haven’t been experiencing problems, I’m not concerned if
you stop supporting 1.0. I did see some really weird problems with Java
integration when I was using JRuby threads, but I found that threads
didn’t speed my application up, so I just stopped using them and have
been happy since.

–Patrick

We’re certainly willing to turn over the maintenance reins to someone
else…but the move to EOL 1.0 largely reflects how much work we have to
do with 1.1.x and future versions, which are much more widely used now.

If you find issues you’d like to get into 1.0 at some point, we may
migrate the 1.0 maintenance line to a contrib branch and allow access
for anyone to keep it going. Or you might want to try running the
retroweaved JRuby, which exists but does not receive any testing.

  • Charlie

[email protected] wrote:

To: jruby-user
but we simply don’t have resources to maintain 1.0 into the future.
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs