Working on a new project, is it wise to continue working on ruby on rails 3.0 or start working on 3.1? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed 9 years ago.

Improve this question

Working on a new project, is it wise to continue working on ruby on开发者_开发知识库 rails 3.0 or start working on 3.1?

This question came to my mind when I realised how deep I was getting in my current project. Rather than switch over later I wondered if it would be good to make the switch now? or if it is too early?

---

Ask yourself: what would be the benefits of switching to Rails 3.1?

You'll have access to the latest and greatest upgrades to the framework such as the Asset Pipeline and better engine support. Rails 3.1 is where Rails is headed, so why not make the switch now?

As for staying on Rails 3.0, I don't see any reason to do that at all.

---

I as for me, I would switch to Rails 3.1, if your project is not quite large. I have 3 projects: rails 2.3.5, rails 3.0.5 and 3.1. And it is become hard to maintain older versions. When your project is not complex - you can easily migrate to fresh Rails and not fix any database or other dependencies.