aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRafael Mendonça França <rafaelmfranca@gmail.com>2015-06-16 13:12:47 -0300
committerRafael Mendonça França <rafaelmfranca@gmail.com>2015-06-16 13:12:47 -0300
commit9dc8ddc39424818a3d713a353353ac20cb431218 (patch)
tree0331b4a43eeae85411caa102b417e7436720ec5c
parent180aad3a5b405141efde0b73a088aa5accbc683a (diff)
downloadrails-9dc8ddc39424818a3d713a353353ac20cb431218.tar.gz
rails-9dc8ddc39424818a3d713a353353ac20cb431218.tar.bz2
rails-9dc8ddc39424818a3d713a353353ac20cb431218.zip
Removing inaccurate note on the releasing guide
-rw-r--r--RELEASING_RAILS.rdoc3
1 files changed, 0 insertions, 3 deletions
diff --git a/RELEASING_RAILS.rdoc b/RELEASING_RAILS.rdoc
index 7bad1d01b8..f9fdd0f687 100644
--- a/RELEASING_RAILS.rdoc
+++ b/RELEASING_RAILS.rdoc
@@ -105,9 +105,6 @@ then realise it is broken.
=== Release the gem.
-IMPORTANT: Due to YAML parse problems on the rubygems.org server, it is safest
-to use Ruby 1.8 when releasing.
-
Run `rake release`. This will populate the gemspecs with data from
RAILS_VERSION, commit the changes, tag it, and push the gems to rubygems.org.
Here are the commands that `rake release` should use, so you can understand