aboutsummaryrefslogtreecommitdiffstats
path: root/RELEASING_RAILS.rdoc
diff options
context:
space:
mode:
authorSteve Klabnik <steve@steveklabnik.com>2013-02-01 11:16:28 -0800
committerSteve Klabnik <steve@steveklabnik.com>2013-02-01 11:16:28 -0800
commit5342797e2f18d753d5f79e027a5c8e633ab7b2b2 (patch)
treed9a8f6c6867066b1edb4040c670f281c3cf37945 /RELEASING_RAILS.rdoc
parent9d2187efb7da3c531997eb0261bc39cf48a69821 (diff)
downloadrails-5342797e2f18d753d5f79e027a5c8e633ab7b2b2.tar.gz
rails-5342797e2f18d753d5f79e027a5c8e633ab7b2b2.tar.bz2
rails-5342797e2f18d753d5f79e027a5c8e633ab7b2b2.zip
Added extra note about when to email other rubies to RELEASING_RAILS.rdoc
Diffstat (limited to 'RELEASING_RAILS.rdoc')
-rw-r--r--RELEASING_RAILS.rdoc3
1 files changed, 3 insertions, 0 deletions
diff --git a/RELEASING_RAILS.rdoc b/RELEASING_RAILS.rdoc
index 9af79f73e2..b065be4922 100644
--- a/RELEASING_RAILS.rdoc
+++ b/RELEASING_RAILS.rdoc
@@ -42,6 +42,9 @@ addressed, and that can impact your release date.
Ruby implementors have high stakes in making sure Rails works. Be kind and
give them a heads up that Rails will be released soonish.
+This only needs done for major and minor releases, bugfix releases aren't a
+big enough deal, and are supposed to be backwards compatible.
+
Send an email just giving a heads up about the upcoming release to these
lists: