On Mon, Mar 8, 2010 at 5:38 PM, Hirotsugu Asari <asari.r...@gmail.com>wrote:
> > On Mar 8, 2010, at 10:26 AM, Nick Sieger wrote: > > > On Sun, Mar 7, 2010 at 2:50 PM, Charles Oliver Nutter > > <head...@headius.com> wrote: > >> Ok, we want to go to RC real soon now. Here's a few things I think are > >> still left unresolved that we need to deal with: > >> > >> * Bugs marked for 1.5 (44 of them). Obviously we're not going to get > >> them all in, so we need to start whittling that list away, starting > >> with the most-critical items. > >> * jruby --java needs test cases, examples, and we need to figure out > >> how it should handle loading associated code (or whether that's the > >> user's responsibility) > > As clarified on IRC, this is about 'jrubyc'. :-) > > >> * Mac OS X installer? > > I don't know if David's on the list, but I do not think that it is close to > releasable yet. > > Sorry, I'm quite busy these days. Actually, the main problem with the osx installer is to decide how to structure the package. Some days ago I was thinking on create what osx calls a "Framework", like the ruby package bundled with the os, that allowed us to maintain several versions easily. I need to take a look at how python bundles its package: http://svn.python.org/projects/python/trunk/Mac/ Anyway, Hiro has credentials to write in the repo, feel free to use it or fork it. If anyone more want access just tell me. > >> * Native launcher...is it ready to go? > > > > Ready to go. We're continuing to make tweaks, but those can be picked > > up separately via gem install. We should also move the launcher to > > 1.0. > > > >> * ant/rake integration...anything left to be done? > > > > Nothing major on my list. There are still some weird bugs -- for > > example when converting JRuby's build.xml to .rb and trying to run a > > compile, I get a SEGV. Even though there's a converter class there, we > > probably shouldn't advertise using pure-Ruby Ant projects until some > > of that stuff is ironed out. > > > >> * Quick pass over recently-updated and recently-added bugs to see if > >> there's any easy ones we can drop in > >> * Rails 3 support: I know it's working, because some folks are playing > >> with it...but are there things we should fix? Where do we stand on > >> test cases? > > > > I'll be working on Rails 3 stuff this week and you'll hear from me if > > there's anything serious. > > > > /Nick > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- David Calavera http://www.thinkincode.net
