aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAaron Patterson <aaron.patterson@gmail.com>2011-08-04 14:15:45 -0700
committerAaron Patterson <aaron.patterson@gmail.com>2011-08-04 14:15:45 -0700
commitcb6a082fee1a984ce91476a48c2af57d32960080 (patch)
treea4bc32bc849cc2d8ebb1dfcdc45510f5316ecab4
parent879dcada2ec33daaa371955604746ca0ffad67f7 (diff)
downloadrails-cb6a082fee1a984ce91476a48c2af57d32960080.tar.gz
rails-cb6a082fee1a984ce91476a48c2af57d32960080.tar.bz2
rails-cb6a082fee1a984ce91476a48c2af57d32960080.zip
moving CI and Sam Ruby to the top of the list. I :heart: CI and Sam
-rw-r--r--RELEASING_RAILS.rdoc38
1 files changed, 19 insertions, 19 deletions
diff --git a/RELEASING_RAILS.rdoc b/RELEASING_RAILS.rdoc
index f780f58f2f..22fc58516e 100644
--- a/RELEASING_RAILS.rdoc
+++ b/RELEASING_RAILS.rdoc
@@ -9,25 +9,6 @@ really be considered as minimums.
Today is mostly coordination tasks. Here are the things you must do today:
-=== Contact the security team (either Koz or tenderlove)
-
-Let them know of your plans to release. There may be security issues to be
-addressed, and that can impact your release date.
-
-=== Notify implementors.
-
-Ruby implementors have high stakes in making sure Rails works. Be kind and
-give them a heads up that Rails will be released soonish.
-
-Send an email just giving a heads up about the upcoming release to these
-lists:
-
-* team@jruby.org
-* community@rubini.us
-* rubyonrails-core@googlegroups.com
-
-Implementors will love you and help you.
-
=== Is the CI green? If not, make it green. (See "Fixing the CI")
Do not release with a Red CI. You can find the CI status here:
@@ -51,6 +32,25 @@ Obviously rails cannot be released when it depends on unreleased code.
Contact the authors of those particular gems and work out a release date that
suites them.
+=== Contact the security team (either Koz or tenderlove)
+
+Let them know of your plans to release. There may be security issues to be
+addressed, and that can impact your release date.
+
+=== Notify implementors.
+
+Ruby implementors have high stakes in making sure Rails works. Be kind and
+give them a heads up that Rails will be released soonish.
+
+Send an email just giving a heads up about the upcoming release to these
+lists:
+
+* team@jruby.org
+* community@rubini.us
+* rubyonrails-core@googlegroups.com
+
+Implementors will love you and help you.
+
== 3 Days before release
This is when you should release the release candidate. Here are your tasks