aboutsummaryrefslogtreecommitdiffstats
path: root/RELEASING_RAILS.md
diff options
context:
space:
mode:
authorJon Moss <me@jonathanmoss.me>2016-02-12 08:36:45 -0500
committerJon Moss <me@jonathanmoss.me>2016-02-12 08:38:21 -0500
commitdf01fad2a95daf2c181101865075daf00dcc5e7c (patch)
treedd444c5dc5f2ce804d622982361a8737cede1e49 /RELEASING_RAILS.md
parentf709682697dd1654e4251e7c3db30e054910cccb (diff)
downloadrails-df01fad2a95daf2c181101865075daf00dcc5e7c.tar.gz
rails-df01fad2a95daf2c181101865075daf00dcc5e7c.tar.bz2
rails-df01fad2a95daf2c181101865075daf00dcc5e7c.zip
Update RELEASING_RAILS.md
Koz is in alumni now, replaced him with rafaelfranca. [ci skip]
Diffstat (limited to 'RELEASING_RAILS.md')
-rw-r--r--RELEASING_RAILS.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/RELEASING_RAILS.md b/RELEASING_RAILS.md
index 83586c22c0..037aa8c119 100644
--- a/RELEASING_RAILS.md
+++ b/RELEASING_RAILS.md
@@ -36,7 +36,7 @@ Obviously Rails cannot be released when it depends on unreleased code.
Contact the authors of those particular gems and work out a release date that
suits them.
-### Contact the security team (either Koz or tenderlove)
+### Contact the security team (either tenderlove or rafaelfranca)
Let them know of your plans to release. There may be security issues to be
addressed, and that can impact your release date.