Some fixes on RELEASING_RAILS.rdoc.

This commit is contained in:
Hendy Tanata 2011-11-18 11:22:18 -08:00
parent ed5586fa9e
commit 6fc2e12ec5
1 changed files with 3 additions and 3 deletions

View File

@ -100,8 +100,8 @@ branch.
Run `rake install` to generate the gems and install them locally. Then try Run `rake install` to generate the gems and install them locally. Then try
generating a new app and ensure that nothing explodes. 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 This will stop you from looking silly when you push an RC to rubygems.org and
realise it is broken. then realise it is broken.
=== Release the gem. === Release the gem.
@ -209,7 +209,7 @@ Repeat these steps until the CI is green.
=== Manually trigger docs generation === Manually trigger docs generation
We have a post-receive hook in GitHub that calls the docs server on pushes. 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. 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 The hook unfortunately is not invoked by tag pushing, so once the new stable