Checks for certainty.
The answer also depends on many other factors related to your setup, such as:
- What is your current test strategy? Do you experience volume?
- Do you have many users who would drown your ability to respond if there is a problem?
- Do you have a backup / plan recovery / restore strategy if problems arise?
- What is your backup strategy and how well do you do it?
- How complicated is your code and what custom code does it exist?
- How similar are your development / testing / production environments?
- Is there any specific business reason for updating now, and not wait a month or two (given that it was just released).
- You are using ruby 1.9.2 (almost certainly, but you need to check it out).
- Do you plan for staff availability for downtime / interruption in case
- Have you tested the actual planned move process on test servers to make sure there are no gotchas?
In general, I would wait 2-3 months. Moreover, with Rails 3.1, since there were quite a few changes in this release, the point, although again the tests should help - although this will depend on their availability and completeness.
source share