In order to avoid 1.7 drawing out past the end of the year, I think
it's time to start talking about tidying things up.
For my part, I'm going to be doing one or two final passes over
invokedynamic support in the compiler. I heard today that OpenJDK 7u2
likely has all the optimizations that it will get, and current work
will be held until OpenJDK 7u4. That's not a bad thing...u2 includes
the most important fixes and improvements, leading to really excellent
JRuby performance. There's just a few wilder uses of invokedynamic I
will have to disable until u4 comes around.
The current set of enabled invokedynamic features in JRuby passes all
tests and specs, so at least from that perspective it's ready for
prime time. There's a couple I still need to fix and turn on, and more
invocation paths that need indy love (like Ruby to Java dispatch, for
sure), but things are looking pretty solid and stable. Once I'm back
from conference travel I'll look at rounding a few cases out and then
closing the door on anything new and crazy.
Other areas we need to discuss for JRuby 1.7:
* Re-stabilizing master. We've drifted a bit and have had a few too
many red builds. We need to clean it up and get it soldily green on
all tests and specs.
* IR work. Where do we stand? Is it possible we might turn it on for
1.7, or is that too ambitious right now?
* Ruby 1.9 compatibility. We've been rolling almost all 1.9 fixes into
the JRuby 1.6 branch, but there are some more ambitious changes (like
the partial rewrite of Enumerable) we need to confirm.
Other areas? Related libraries that need to be brought up-to-date and
released around the same timeframe?
I believe we're still targeting end-of-year or shortly after,
hopefully to coincide roughly with the OpenJDK 7u2 release.
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
