> we made a decision to delay moving to Rails 2.2 for as long as we > could.
OK looks like a Rails 2.2 upgrade can be a bit more work than I'd realised. I've upgraded several apps very easily though. The only problems I've hit (so far!) were in Hobo itself, and those are fixed now. Unfortunately this kind of thing is just part of the challenge of using a big project like Hobo before 1.0. At one point we insisted on edge Rails - that really annoyed a few people :) Using lots of other plugins will also exaggerate these issues. One thing you could do is fork Hobo and keep a Rails 2.1 branch, cherry-picking in any fixes you need that come later. Tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hobo Users" 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/hobousers?hl=en -~----------~----~----~----~------~----~------~--~---
