Yeah, I was able to take a small project of mine and update it to Rails 3 on Ruby 1.8.7 with very little trouble. I did have to fork and modify the twitter-auth and backgroundrb plugins for the new plugin API, but once I understood the new requirements it was very easy. I am definitely targeting Rails 3 for any new projects at this point.
-Nic On Mar 17, 2010, at 10:14 AM, John Lynch wrote: > Like Matt says, if the plugins you are planning on using are updated, then > Rails3 is a good choice. However, I recently started a project using > Rails3/Ruby1.9/Ubuntu9.10, and I spent a lot of time shaving yaks, mainly > with issues related to Ruby1.9. Backing down to Ruby1.8.7 seemed to go a lot > smoother. > > > > Regards, > > John Lynch, CTO > Rigel Group, LLC > [email protected] > > > > On Wed, Mar 17, 2010 at 10:05 AM, Matt Aimonetti <[email protected]> > wrote: > Plugins might be an issue if they hack into Rails' internals, otherwise, > Rails3 beta is ok when starting new projects. A new beta should hit the > interwebs shortly if everything goes according to plan. > > Matt plugins/gems were you planning on using? > > Also, make sure to switch to Rub 1.8.7 or even better Ruby 1.9, 1.9.2 final > should be released in August according to the release schedule. > > - Matt > > > On Wed, Mar 17, 2010 at 12:58 PM, Kevin Baker <[email protected]> wrote: > We have a couple Rails app coming up that I'd like to jump into Rails 3 with. > > What is the consensus on Rails3 production readiness? They are pretty > standard CRUD apps with some pretty standard plugins? > > > > ---- > Kevin Baker > Sr Software Engineer > Sorenson Media > > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby > > > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby > > > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
