aboutsummaryrefslogtreecommitdiffstats
path: root/guides
diff options
context:
space:
mode:
authorPrathamesh Sonpatki <csonpatki@gmail.com>2016-02-12 13:38:02 +0530
committerPrathamesh Sonpatki <csonpatki@gmail.com>2016-02-12 13:38:02 +0530
commit2c89123b1a369c3b9c2b498d9001595ca335a06c (patch)
tree7f4a8e3f4c32106fbea6be6574dc896f452c3de8 /guides
parent737b718ea0c88d3f6c139343f957f386e06fffc9 (diff)
downloadrails-2c89123b1a369c3b9c2b498d9001595ca335a06c.tar.gz
rails-2c89123b1a369c3b9c2b498d9001595ca335a06c.tar.bz2
rails-2c89123b1a369c3b9c2b498d9001595ca335a06c.zip
Fix numbers of steps to upgrade Rails [ci skip]
Diffstat (limited to 'guides')
-rw-r--r--guides/source/upgrading_ruby_on_rails.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/guides/source/upgrading_ruby_on_rails.md b/guides/source/upgrading_ruby_on_rails.md
index 2998e66272..cef83e4264 100644
--- a/guides/source/upgrading_ruby_on_rails.md
+++ b/guides/source/upgrading_ruby_on_rails.md
@@ -23,9 +23,9 @@ When changing Rails versions, it's best to move slowly, one minor version at a t
The process should go as follows:
1. Write tests and make sure they pass
-1. Move to the latest patch version after your current version
-1. Fix tests and deprecated features
-1. Move to the latest patch version of the next minor version
+2. Move to the latest patch version after your current version
+3. Fix tests and deprecated features
+4. Move to the latest patch version of the next minor version
Repeat this process until you reach your target Rails version. Each time you move versions, you will need to change the Rails version number in the Gemfile (and possibly other gem versions) and run `bundle update`. Then run the Update rake task mentioned below to update configuration files, then run your tests.