aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRafael França <rafaelmfranca@gmail.com>2016-11-21 14:43:26 -0500
committerGitHub <noreply@github.com>2016-11-21 14:43:26 -0500
commit5b4ee4db52beab34bbf3fcf4c0cec31bf30734d1 (patch)
treec4f67a99ccc08fa30c566b7130fa1d9f7352bcb8
parent2b4a9735d816d3a05c7fca207d97bebcb09c95a0 (diff)
parent49f7b043f2b1031b0712efa0edb23497b57ccce2 (diff)
downloadrails-5b4ee4db52beab34bbf3fcf4c0cec31bf30734d1.tar.gz
rails-5b4ee4db52beab34bbf3fcf4c0cec31bf30734d1.tar.bz2
rails-5b4ee4db52beab34bbf3fcf4c0cec31bf30734d1.zip
Merge pull request #27135 from tjai89/patch-1
Update RELEASING_RAILS.md
-rw-r--r--RELEASING_RAILS.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/RELEASING_RAILS.md b/RELEASING_RAILS.md
index 4e6b811d3e..ec8d2b657f 100644
--- a/RELEASING_RAILS.md
+++ b/RELEASING_RAILS.md
@@ -179,7 +179,7 @@ more explanation on a particular step, see the RC steps.
Today, do this stuff in this order:
* Apply security patches to the release branch
-* Update CHANGELOG with security fixes.
+* Update CHANGELOG with security fixes
* Update RAILS_VERSION to remove the rc
* Build and test the gem
* Release the gems
@@ -206,7 +206,7 @@ so we need to give them the security fixes in patch form.
* Blog announcements
* Twitter announcements
-* Merge the release branch to the stable branch.
+* Merge the release branch to the stable branch
* Drink beer (or other cocktail)
## Misc