Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

making the order more clear, adding linux distros mailing lists to ou…

…r cc
  • Loading branch information...
commit 22e611ed5b0a708d17ef2e7574bcdf2edf2db01b 1 parent 9d9f591
@tenderlove tenderlove authored
Showing with 13 additions and 10 deletions.
  1. +13 −10 RELEASING_RAILS.rdoc
View
23 RELEASING_RAILS.rdoc
@@ -145,22 +145,25 @@ 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.
+Today, do this stuff in this order:
+
+* Apply security patches to the release branch
+* Update CHANGELOG with security fixes.
+* Update RAILS_VERSION to remove the rc
+* Release the gems
+* Email security lists
+* Email general announcement lists
-See steps for releasing the RC. Make sure to release the gem before
-announcing security issues in the next step.
+=== Emailing the rails security announce list
-=== Email the rails security announce list, once for each vulnerability fixed.
+Email the security announce list once for each vulnerability fixed.
You can do this, or ask the security team to do it.
-Email the security reports to: rubyonrails-security@googlegroups.com
+Email the security reports to:
-* Apply security patches to the release branch
-* Update CHANGELOG with security fixes.
-* Update RAILS_VERSION to remove the rc
-* Release the gems
-* Email announcement
+* rubyonrails-security@googlegroups.com
+* linux-distros@vs.openwall.org
Be sure to note the security fixes in your announcement along with CVE numbers
and links to each patch. Some people may not be able to upgrade right away,
Please sign in to comment.
Something went wrong with that request. Please try again.