diff options
| author | Leslie Viljoen <leslieviljoen@gmail.com> | 2016-02-12 11:48:11 +1300 |
|---|---|---|
| committer | Leslie Viljoen <leslieviljoen@gmail.com> | 2016-02-12 11:56:26 +1300 |
| commit | de51b0e70728396c5adffde39ebb55c10cc61204 (patch) | |
| tree | 43f39927ec8404ab24ebf5746a72e977cd2960e6 /guides | |
| parent | 4097ed5586ca23551d7f1fa3dbde4f5c86fa36ae (diff) | |
| download | rails-de51b0e70728396c5adffde39ebb55c10cc61204.tar.gz rails-de51b0e70728396c5adffde39ebb55c10cc61204.tar.bz2 rails-de51b0e70728396c5adffde39ebb55c10cc61204.zip | |
Improve wording in documentation change
[ci skip]
Diffstat (limited to 'guides')
| -rw-r--r-- | guides/source/upgrading_ruby_on_rails.md | 6 |
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 515b3ee7a3..2998e66272 100644 --- a/guides/source/upgrading_ruby_on_rails.md +++ b/guides/source/upgrading_ruby_on_rails.md @@ -18,7 +18,7 @@ The best way to be sure that your application still works after upgrading is to ### The Upgrade Process -When changing Rails versions, it's best to move slowly, one minor version at a time, in order to make good use of the deprecation warnings. Rails version numbers are in the form Major.Minor.Patch. Major and Minor versions change the API which means you will probably need to change your code. Patch versions are just bug fixes that don't change the API. +When changing Rails versions, it's best to move slowly, one minor version at a time, in order to make good use of the deprecation warnings. Rails version numbers are in the form Major.Minor.Patch. Major and Minor versions are allowed to make changes to the public API, so this may cause errors in your application. Patch versions only include bug fixes, and don't change any public API. The process should go as follows: @@ -27,9 +27,9 @@ The process should go as follows: 1. Fix tests and deprecated features 1. 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. +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. -You can find a list of all the Rails Gem versions [here](https://rubygems.org/gems/rails/versions). +You can find a list of all released Rails versions [here](https://rubygems.org/gems/rails/versions). ### Ruby Versions |