kotovalexarian-likes-github/rails--rails
1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
Code Releases Activity

making the order more clear, adding linux distros mailing lists to our cc

Browse source
This commit is contained in:
Aaron Patterson 2011-08-16 17:39:58 -07:00
parent 9d9f59139e
commit 22e611ed5b
1 changed files with 14 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

25
RELEASING_RAILS.rdoc
View file

@ -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.
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.
Email the security reports to: rubyonrails-security@googlegroups.com
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 announcement
* Email security lists
* Email general announcement lists
=== Emailing the rails security announce list
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
* 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,