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

adding lessons learned so I do not make the same mistake twice

Browse source
This commit is contained in:
Aaron Patterson 2011-08-16 16:30:29 -07:00
parent 5f94b93279
commit 9d9f59139e
1 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
RELEASING_RAILS.rdoc
View file

@ -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 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. 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. === Email the rails security announce list, once for each vulnerability fixed.
You can do this, or ask the security team to do it. You can do this, or ask the security team to do it.