How to convince my manager of rails 3 updates | I have to go on rails 3

Question

We are currently launching rails 2.1.

My main motivation for updating is the fear that gems / plugins will appear less often / are not available / are not supported day by day for our version (and the excitement of the latest technologies).

I understand that there are many, many improvements that come with rails3, but probably what my manager wants to listen to are the advantages he received from a business point of view.

Our Saas application, application loading is not very high, but the demand for reliability is greater.

Edit:

• It seems like my penchant for updating needs to be rethought, so replies to “should be updated” are welcome.

• My original question also needs answers - how to describe the business benefits of upgrading from rails2.1 → rails3.

• The application is in active development / improvements.

Answer 1

The longer you go without an update, the harder the time will be. Sooner or later, any actively supported project will have to switch to later versions, and the more versions you have to skip along the way, the more complicated and risky. If you update regularly, this becomes a fairly simple maintenance task.

, 2.1 → 3.0 , . 2.1 → 2.3.9 . , , 2.1 → 3.1 . , . , .

Answer 2

• , , , .

• , .

Answer 3

!

, , , . , .

Rails 2.x Rails 3, . Rails, .

, , railsplugins.org , , .

: , , , , , , 2.x, 3.0 . , 2.x. , , , , , .

Answer 4

, , , , . .

, Rails 3.

Businesses . Resume Driven.

.:)

Answer 5

, , .

• - , 1 ActiveSupport. , rails1, , 2 API, restful json. , , , , .
• , - , - , , . , , , , , .
• Error correction in older versions of plugins / gems - if you encounter an error in rails or a plugin, as well as with a stone or some other integration problem, this can be fixed in a later version, but what depends on the newer version rails. This will make your path to fixing the specified error or implementing the specified improvement more, the longer you wait for the update.