I wrote a post back in January about trying to get an app running on 1.9.1 [1] and wrote another one over this weekend [2]. Ruby 1.9.1 has come a long way since January! Take for example the mysql gem which needed editing, now doesn't. I got my app running on 1.9.1 with only the patch to Ruby + Passenger for the Rails post issue highlighted in Sam's stackoverflow answer.
Yeah, there's going to be gems that break but if we can get together as a community and patch them to use 1.9 then we'll all be better off for it. What are the gems that don't work for you? [1]: http://frozenplague.net/2009/01/ruby-191-rubygems-rails/ [2]: http://frozenplague.net/2009/12/ruby-1-9-1-friends-11-months-on/ 2009/12/7 Chris Herring <[email protected]> > I think we need to try. If we don't then the gems will need patching > forever. It's a bit of a chicken and the egg thing, without patching the > gems I guess it's not prod ready, but if we don't try to make our own apps > 1.9 ready and share the gem patches then we'll never make it. > > If you can get your app to 1.9, I say go for it! > > > On Mon, Dec 7, 2009 at 7:19 AM, Xavier Shay <[email protected]> wrote: > >> On 6/12/09 10:53 PM, sambo99 wrote: >> > I just spent a day upgrading my code to be a bit more 1.9.1 friendly, >> > surprisingly few code changes work required on my side. >> > >> > But it did feel like a bit of a minefield getting the periphery going >> > see: >> http://stackoverflow.com/questions/1666094/has-anyone-successfully-deployed-a-rails-project-with-ruby-1-9-1/1855167#1855167 >> > >> > Is it just me, or is 1.9.1 still a bit early for production use? >> We're not running in prod on 1.9, but I got our code base working with >> it, including all the bits and pieces. Needed to patch a few gems, but >> that's good for your soul :) >> >> > >> > -- >> > >> > You received this message because you are subscribed to the Google >> Groups "Ruby or Rails Oceania" group. >> > To post to this group, send email to [email protected]. >> > To unsubscribe from this group, send email to >> [email protected]<rails-oceania%[email protected]> >> . >> > For more options, visit this group at >> http://groups.google.com/group/rails-oceania?hl=en. >> > >> > >> >> -- >> >> You received this message because you are subscribed to the Google Groups >> "Ruby or Rails Oceania" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<rails-oceania%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/rails-oceania?hl=en. >> >> >> > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<rails-oceania%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. > -- Ryan Bigg -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
