News for hackers. Stuff that matters.
Re:Rails 3.0: Release candidate by davidw on Tuesday July 27, 2010 @02:52AM (#1550471)
I haven't had a look at 3.0 yet. What's the effort like to upgrade? I have this suspicion that it's basically going to be a major rewrite for most of my projects with all the new apis and deprecation. It's almost as if it were a completely separate project that offered some degree of Rails compatibility to help people transition. However, that's the impression I get from reading things - how is it in practice for those who have updated significant code bases?
Re:Rails 3.0: Release candidate by ekidd on Tuesday July 27, 2010 @06:14AM (#1550775)
The core Rails APIs are mostly the same, though you'll have to basically rewrite a couple of files in config/. I'm currently porting a moderately large application from 2.3, and few of the remaining unit test failures have anything to do with the Rails core.

Your biggest problem will be that a number of third-party gems have been heavily updated for ActiveSupport 3.0, including RSpec, Devise and Mongoid, and these may cause more headaches than Rails itself. Figure a few days of updating stuff and staring at unit test failures if you rely heavily on these gems.

Of course, all bets are off if you use a lot of dodgy, unmaintained gems that heavily monkey-patch Rails. We have a pretty strict policy against using dubious minor gems that stick their fingers deep inside Rails, after some bad experiences over the past couple of years.

Re:Rails 3.0: Release candidate by hitonagashi on Tuesday July 27, 2010 @06:52AM (#1550832)
You've got to be careful with Ruby versions.

Rails 3 runs on 1.8.7 and 1.9.2.

My machine before was running on 1.8.6 and 1.9.1 (okay, I'm lazy!), but luckily RVM simplified the upgrade for me.

If you are still running on 1.8.6, it's something to bear in mind :).