aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorप्रथमेश Sonpatki <csonpatki@gmail.com>2016-02-12 13:39:33 +0530
committerप्रथमेश Sonpatki <csonpatki@gmail.com>2016-02-12 13:39:33 +0530
commit8925e37fdcc37f4ff2ab2d55168719bbe9386ebf (patch)
tree7f4a8e3f4c32106fbea6be6574dc896f452c3de8
parent737b718ea0c88d3f6c139343f957f386e06fffc9 (diff)
parent2c89123b1a369c3b9c2b498d9001595ca335a06c (diff)
downloadrails-8925e37fdcc37f4ff2ab2d55168719bbe9386ebf.tar.gz
rails-8925e37fdcc37f4ff2ab2d55168719bbe9386ebf.tar.bz2
rails-8925e37fdcc37f4ff2ab2d55168719bbe9386ebf.zip
Merge pull request #23629 from prathamesh-sonpatki/fix-numbers
Fix numbers of steps to upgrade Rails [ci skip]
-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.