aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJon Moss <maclover7@users.noreply.github.com>2016-02-12 08:39:43 -0500
committerJon Moss <maclover7@users.noreply.github.com>2016-02-12 08:39:43 -0500
commitf7aa4c92a0a0dd609b6e07a5db256c417d0aa235 (patch)
treedd444c5dc5f2ce804d622982361a8737cede1e49
parentf709682697dd1654e4251e7c3db30e054910cccb (diff)
parentdf01fad2a95daf2c181101865075daf00dcc5e7c (diff)
downloadrails-f7aa4c92a0a0dd609b6e07a5db256c417d0aa235.tar.gz
rails-f7aa4c92a0a0dd609b6e07a5db256c417d0aa235.tar.bz2
rails-f7aa4c92a0a0dd609b6e07a5db256c417d0aa235.zip
Merge pull request #23633 from maclover7/sec-releasing
Update 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.