From 6fc2e12ec5814658da26de8b0d9c1ffb4365dfa0 Mon Sep 17 00:00:00 2001 From: Hendy Tanata Date: Fri, 18 Nov 2011 11:22:18 -0800 Subject: Some fixes on RELEASING_RAILS.rdoc. --- RELEASING_RAILS.rdoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'RELEASING_RAILS.rdoc') diff --git a/RELEASING_RAILS.rdoc b/RELEASING_RAILS.rdoc index 3f05e97b91..9f25adeccc 100644 --- a/RELEASING_RAILS.rdoc +++ b/RELEASING_RAILS.rdoc @@ -100,8 +100,8 @@ branch. Run `rake install` to generate the gems and install them locally. Then try generating a new app and ensure that nothing explodes. -This will stop you looking silly when you push an RC to rubygems.org and then -realise it is broken. +This will stop you from looking silly when you push an RC to rubygems.org and +then realise it is broken. === Release the gem. @@ -209,7 +209,7 @@ Repeat these steps until the CI is green. === Manually trigger docs generation We have a post-receive hook in GitHub that calls the docs server on pushes. -Triggers generation and publication of edge docs, updates the contrib app, +It triggers generation and publication of edge docs, updates the contrib app, and generates and publishes stable docs if a new stable tag is detected. The hook unfortunately is not invoked by tag pushing, so once the new stable -- cgit v1.2.3