If you see a lot of improvements that you personal would use in 3.1 over 3.0.7, then you should think about switching. Another thing to consider is deadlines, as upgrading will push the moment you are ready to go to production further. You yourself raised a great question: will all the gems work with the new version? If you are using few of them, you should check that out before making the decision. Some projects use 50+ gems and then an incompatible gem can bring considerable slowdown to development. Are you willing to patch the gems/plugins yourself if they aren't compatible? My personal opinion would be continue with development, and upgrade when the project is on production, because then you'll be able to focus on 1 task - upgrading, while if you migrate now, you will have to both keep developing the functionality, and solve incompatability problems.
2011/5/29 egervari <[email protected]> > Well, I got most things to work. I just have to figure out my assets > now. I made the folders and organized them. Now it's time to get them > to work ;) > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en.
