Re: [Ironruby-core] MRI 1.8.7 compatibility

I honestly don’t think that shipping a 1.0 will delay any future release by much. I also don’t think that a Rails 3 release would hurt the progress towards 1.9. Unless something major changes, I believe all of the 1.8.7 features we are currently lacking for Rails 3 are also 1.9 features. JD F

Re: [Ironruby-core] MRI 1.8.7 compatibility

Overreact? I *never* do that ;-) If you guys are close to shipping 1.0, then I don't have a problem with a newer patch level release, like 1.0.1 or 1.0.2, providing just enough 1.8.7 compat to support Rails 3. On the other hand, if you think that 1.9 support is attainable this year, I'd rather see

Re: [Ironruby-core] MRI 1.8.7 compatibility

JRuby, Rubinius and MacRuby will support Rails 3, but all three of them are either working on a version to support 1.9 (Jruby), or only targeting 1.9 (the other 2). We’ve said a few times in the halls that if we had noticed the timing a year ago, 1.9 would probably have been a better 1.0 target

Re: [Ironruby-core] MRI 1.8.7 compatibility

1) What's the story on the other implementations for Rails 3? In other words, will JRuby, Rubinius, et. al. run Rails 3 out of the gate? If so, are they doing it on a 1.9 compat version or 1.8.7? If they are pursuing the former, no one will be able to fault IronRuby for not supporting Rails. If the

Re: [Ironruby-core] MRI 1.8.7 compatibility

Good point, but slight overreaction =) Running Rails 3 and being 1.8.7 compatible can be completely different goals, as Rails 3 doesn't use all of the 1.8.7 features. =) We can implement the features needed for Rails 3 for the releases after 1.0, so we may turn out to be compatible-enough with

Re: [Ironruby-core] MRI 1.8.7 compatibility

DISCLAIMER: We haven't discussed this yet, I'm just tossing it out to get thoughts. One option may be to put Rails 3 compat as the focus for 1.1, so that we do 1.0 in a few months on our current timeline, then put the focus into implementing the needed things for Rails 3. After that we can con

Re: [Ironruby-core] MRI 1.8.7 compatibility

> IronRuby 1.0.x releases: ONLY ruby-1.8.6 compatible > IronRuby 1.x releases: ONLY ruby-1.9 compatible > My fear is that releasing 1.0 so close to release of Rails 3 without the > ability to run it will do little for IronRuby's image in the wider Ruby > community (who, from my admittedly limited

Re: [Ironruby-core] MRI 1.8.7 compatibility

How much effort is it to get 1.8.7 compatible? How much to get 1.9 compatible? What is driving the push to release 1.0? My fear is that releasing 1.0 so close to release of Rails 3 without the ability to run it will do little for IronRuby's image in the wider Ruby community (who, from my admitted

Re: [Ironruby-core] MRI 1.8.7 compatibility

Here's the current compatibility plan, let me know if this concerns anyone: > IronRuby 1.0.x releases: ONLY ruby-1.8.6 compatible > === > IronRuby has created a 1.0-servicing branch (not on GitHub yet, > but shortly); all ruby-1.8.6 compatible rele

Re: [Ironruby-core] MRI 1.8.7 compatibility

Here's the current compatibility plan, let me know if this concerns anyone: > IronRuby 1.0.x releases: ONLY ruby-1.8.6 compatible > === > IronRuby has created a 1.0-servicing branch (not on GitHub yet, but > shortly); all ruby-1.8.6 compatible rel

Re: [Ironruby-core] New 2.3.2 Version (NO DBI)

FYI. ironruby-sqlserver (described at http://ironruby.net/Documentation/Real_Ruby_Applications/Rails) will have to lock down on 2.3.1 of the activerecord-sqlserver-adapter gem for now. From: rails-sqlserver-adap...@googlegroups.com [rails-sqlserver-adap

Re: [Ironruby-core] [ANN] IronRuby Unleashed

Nice work!! I'll try and grab a copy when it's out on Amazon UK! Still saying 28 Mar 2010. Ben On Mon, Feb 15, 2010 at 9:46 AM, Shay Friedman wrote: > Hi all! > I'm very excited to announce that the book IronRuby Unleashed has been > released! > The book was written by me and was reviewed by Jus

[Ironruby-core] [ANN] IronRuby Unleashed

Hi all! I'm very excited to announce that the book IronRuby Unleashed has been released! The book was written by me and was reviewed by Justin Etheredge ( codethinked.com). It is already available on the InformIT web site