aboutsummaryrefslogtreecommitdiffstats
path: root/RELEASING_RAILS.rdoc
diff options
context:
space:
mode:
authorAaron Patterson <aaron.patterson@gmail.com>2011-08-16 16:30:29 -0700
committerAaron Patterson <aaron.patterson@gmail.com>2011-08-16 16:30:29 -0700
commit9d9f59139ea4db9ac6e55defc5156f8e8ab580f8 (patch)
treec789f2b80ec6c0059a81535e3cdaa525eb1f420b /RELEASING_RAILS.rdoc
parent5f94b93279f6d0682fafb237c301302c107a9552 (diff)
downloadrails-9d9f59139ea4db9ac6e55defc5156f8e8ab580f8.tar.gz
rails-9d9f59139ea4db9ac6e55defc5156f8e8ab580f8.tar.bz2
rails-9d9f59139ea4db9ac6e55defc5156f8e8ab580f8.zip
adding lessons learned so I do not make the same mistake twice
Diffstat (limited to 'RELEASING_RAILS.rdoc')
-rw-r--r--RELEASING_RAILS.rdoc5
1 files changed, 5 insertions, 0 deletions
diff --git a/RELEASING_RAILS.rdoc b/RELEASING_RAILS.rdoc
index c2ba4e7857..f4197e0eb2 100644
--- a/RELEASING_RAILS.rdoc
+++ b/RELEASING_RAILS.rdoc
@@ -145,6 +145,11 @@ commits should be added to the release branch besides regression fixing commits.
Many of these steps are the same as for the release candidate, so if you need
more explanation on a particular step, so the RC steps.
+=== Release the gem.
+
+See steps for releasing the RC. Make sure to release the gem before
+announcing security issues in the next step.
+
=== Email the rails security announce list, once for each vulnerability fixed.
You can do this, or ask the security team to do it.