svn commit: r783649 - /websites/staging/aries/trunk/content/development/releasingaries.html

[bu...@apache.org]

Author: buildbot
Date: Thu Jan 20 17:06:23 2011
New Revision: 783649

Log:
Staging update by buildbot

Modified:
    websites/staging/aries/trunk/content/development/releasingaries.html

Modified: websites/staging/aries/trunk/content/development/releasingaries.html
==============================================================================
--- websites/staging/aries/trunk/content/development/releasingaries.html (original)
+++ websites/staging/aries/trunk/content/development/releasingaries.html Thu Jan 20 17:06:23 2011
@@ -348,7 +348,7 @@ failures, the easiest way I've found so 
 
 <p>This will pick out the failing file names. Some of the files that rat fails
 do not require an Apache license, eg MANIFEST.MF, but any <em>.java or </em>.js
-file does need one.</p>
+file does need one. As an alternative you can use 'mvn -Prat install'.</p>
 <p><a name="ReleasingAries-Creatingasnapshotrelease"></a></p>
 <h3 id="creating_a_snapshot_release">Creating a snapshot release</h3>
 <p>TBD. This isn't a necessary step in the release process but should still be
@@ -379,7 +379,7 @@ because everything else depends on it. R
 
 
 <p><em>Note</em> The prepare step will make some assumptions about the version of the
-development steam that is left after the release has been made. When
+development stream that is left after the release has been made. When
 releasing from a branch it may not be a good idea to accept the default for
 this, it will very likely conflict with the development version in use in
 trunk.</p>