Skip to content
Browse files

Update the "upgrading" guide for people coming from 3.0 and 3.1. The …

…latest versions for 3.1 and 3.2 are now 3.2.12 and 3.1.11 respectively.
  • Loading branch information...
1 parent e466a58 commit ac0285ecb874f7e6ded736f377182972e47e3330 @plexus plexus committed Feb 20, 2013
Showing with 4 additions and 4 deletions.
  1. +4 −4 guides/source/upgrading_ruby_on_rails.md
View
8 guides/source/upgrading_ruby_on_rails.md
@@ -97,14 +97,14 @@ Upgrading from Rails 3.1 to Rails 3.2
If your application is currently on any version of Rails older than 3.1.x, you should upgrade to Rails 3.1 before attempting an update to Rails 3.2.
-The following changes are meant for upgrading your application to Rails 3.2.2, the latest 3.2.x version of Rails.
+The following changes are meant for upgrading your application to Rails 3.2.12, the latest 3.2.x version of Rails.
### Gemfile
Make the following changes to your `Gemfile`.
```ruby
-gem 'rails', '= 3.2.2'
+gem 'rails', '= 3.2.12'
group :assets do
gem 'sass-rails', '~> 3.2.3'
@@ -144,14 +144,14 @@ Upgrading from Rails 3.0 to Rails 3.1
If your application is currently on any version of Rails older than 3.0.x, you should upgrade to Rails 3.0 before attempting an update to Rails 3.1.
-The following changes are meant for upgrading your application to Rails 3.1.3, the latest 3.1.x version of Rails.
+The following changes are meant for upgrading your application to Rails 3.1.11, the latest 3.1.x version of Rails.
### Gemfile
Make the following changes to your `Gemfile`.
```ruby
-gem 'rails', '= 3.1.3'
+gem 'rails', '= 3.1.11'
gem 'mysql2'
# Needed for the new asset pipeline

0 comments on commit ac0285e

Please sign in to comment.
Something went wrong with that request. Please try again.