aboutsummaryrefslogtreecommitdiffstats
path: root/RELEASING_RAILS.md
diff options
context:
space:
mode:
Diffstat (limited to 'RELEASING_RAILS.md')
-rw-r--r--RELEASING_RAILS.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/RELEASING_RAILS.md b/RELEASING_RAILS.md
index 3ff28c29f5..60434451fe 100644
--- a/RELEASING_RAILS.md
+++ b/RELEASING_RAILS.md
@@ -14,14 +14,14 @@ Today is mostly coordination tasks. Here are the things you must do today:
Do not release with a Red CI. You can find the CI status here:
```
-http://travis-ci.org/rails/rails
+https://travis-ci.org/rails/rails
```
### Is Sam Ruby happy? If not, make him happy.
Sam Ruby keeps a [test suite](https://github.com/rubys/awdwr) that makes
sure the code samples in his book
-([Agile Web Development with Rails](https://pragprog.com/titles/rails5/agile-web-development-with-rails-5th-edition))
+([Agile Web Development with Rails](https://pragprog.com/book/rails51/agile-web-development-with-rails-51))
all work. These are valuable system tests
for Rails. You can check the status of these tests here:
@@ -141,7 +141,7 @@ lists where you should announce:
Use Markdown format for your announcement. Remember to ask people to report
issues with the release candidate to the rails-core mailing list.
-NOTE: For patch releases there's a `rake announce` task to generate the release
+NOTE: For patch releases, there's a `rake announce` task to generate the release
post. It supports multiple patch releases too:
```