There are many tasks we need to iron out before getting the release out the door. I propose the following list...add or subtract as you see fit:
- Finalize integration of JvYAML into JRuby. We'll include it with the release and make it the default YAML parser.
- Confirm Rake and Rails gems are installing correctly *and are working*. Our demo for JavaOne used gem-installed Rails, but it was the copied version from a C Ruby distribution. We'll want to confirm we can take a bare JRuby install, install Rails and dependencies, and expect it to work (with all our additional non-gem-related hacks and contortions)
- Tom and I need to wrap up current performance work and decide what should be in the release. We've committed some and held others back, and we identify new performance opportunities every day. Things are looking good for improved performance before we even start worrying about compilation. We want to get as much in the release as possible, but need to draw the line.
- Those of you using JRuby on live projects will want to re-run your test suites. There shouldn't be nearly as much breakage in this release as there was in 0.8.3; that release represented six months of vicious refactoring, while this round has been purely about fixing bugs.
- We need to iron out how to include Ruby's .rb libraries and trim out those that we don't want to include (like yaml or any others that use native code). We will include a full complement of Ruby libraries in this release (potentially a bare archive without and a "complete" archive with). We must confirm all expected apps (like IRB) work out of the box.
- We should consider including RubyGems pre-installed. Ruby does it, and it might be nice for us to do it too.
- We'll need a "JRuby manifest" that includes information on external projects and libraries included, such as the .rb libraries, JvYAML, RubyGems, and so on.
Up in the air:
- Where to keep Rails-related stuff, like Nick's ActiveRecord-JDBC connector, and whether that even goes with JRuby as part of a general release
- Where to keep JSR223/Mustang-related stuff like we created for JavaOne
--
Charles Oliver Nutter @ headius.blogspot.com
JRuby Developer @ jruby.sourceforge.net
Application Architect @ www.ventera.com
_______________________________________________ Jruby-devel mailing list Jruby-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jruby-devel
