From 9d9f59139ea4db9ac6e55defc5156f8e8ab580f8 Mon Sep 17 00:00:00 2001 From: Aaron Patterson Date: Tue, 16 Aug 2011 16:30:29 -0700 Subject: adding lessons learned so I do not make the same mistake twice --- RELEASING_RAILS.rdoc | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'RELEASING_RAILS.rdoc') diff --git a/RELEASING_RAILS.rdoc b/RELEASING_RAILS.rdoc index c2ba4e7857..f4197e0eb2 100644 --- a/RELEASING_RAILS.rdoc +++ b/RELEASING_RAILS.rdoc @@ -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 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. -- cgit v1.2.3