Mailing-List: contact commits-help@ctakes.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ctakes.apache.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r1546583 -
 /ctakes/site/trunk/content/ctakes-release-guide.mdtext
Date: Fri, 29 Nov 2013 15:38:10 -0000
To: commits@ctakes.apache.org
From: james-masanz@apache.org
Message-Id: <20131129153810.EF16D23889E3@eris.apache.org>

Author: james-masanz
Date: Fri Nov 29 15:38:10 2013
New Revision: 1546583

URL: http://svn.apache.org/r1546583
Log:
fix typo and minor word smithing

Modified:
    ctakes/site/trunk/content/ctakes-release-guide.mdtext

Modified: ctakes/site/trunk/content/ctakes-release-guide.mdtext
URL: http://svn.apache.org/viewvc/ctakes/site/trunk/content/ctakes-release-guide.mdtext?rev=1546583&r1=1546582&r2=1546583&view=diff
==============================================================================
--- ctakes/site/trunk/content/ctakes-release-guide.mdtext (original)
+++ ctakes/site/trunk/content/ctakes-release-guide.mdtext Fri Nov 29 15:38:10 2013
@@ -19,8 +19,8 @@ Notice:    Licensed to the Apache Softwa
 ##How does cTAKES manage releases?
 
 We follow the standard ASF release process. 
-One of the committers would volunteer to play the release manager role for a given release. 
-A few days will be spent on stabilizing the cTAKES development trunk, improving its documentation and test coverage. 
+One of the committers would volunteer to take on the release manager role for a given release. 
+A few days will be spent stabilizing the cTAKES development trunk, improving its documentation and test coverage. 
 The maven release plug-in (mvn release:prepare/perform) is recommended for this purpose (See details below).
 
 Open JIRA issues will be reviewed and rearranged accordingly. Many of the issues will get resolved during this process and the remaining few will be accordingly prioritized and scheduled for a future release. The unit tests and integration tests will be used extensively during this critical period to keep the development in its most stable form.
@@ -31,7 +31,7 @@ Move any existing open issues to the nex
  3. If B) create a branch from trunk (such svn copy from trunk to branches/3.1.1).  Edit the SVN connections info in the root pom.xml to the branch instead of trunk.  Continue with the steps below as usual, but just work off the newly created branch instead of trunk.  Note: It is the RM role to ensure that any fixes done in the branch are also done back in trunk.
 
 
-Finally the release manager would trigger the release build, sign the generated artifacts and host them on Apache Nexus & Maven Central. A release vote will be called urging all those interested to review the packs and provide feedback. Upon receiving the necessary number of votes, the artifacts will be uploaded to the appropriate servers for distribution.
+Finally the release manager would trigger the release build, sign the generated artifacts and host them on Apache Nexus & Maven Central. A release vote will be called urging all those interested to review the packages and provide feedback. Upon receiving the necessary number of votes, the artifacts will be uploaded to the appropriate servers for distribution.
 
 ### Preparing your Environment
 
@@ -41,7 +41,7 @@ Finally the release manager would trigge
 ### Preparing a Release using Maven 
 Note: Using 3.1.1 as an example
 
-It may prompt you to enter your PGP passphrase and SVN password multiple times for each module.  Just enter them in- as passing them in thru the CLI is found to be insecure.
+Maven may prompt you to enter your PGP passphrase and SVN password multiple times for each module.  Just enter them in - as passing them in through the CLI is found to be insecure.
 
  1. $svn co https://svn.apache.org/repos/asf/ctakes/trunk ctakes
  2. $mvn release:clean
@@ -92,7 +92,6 @@ The release was made using the cTAKES re
 The candidate is available at:
 https://dist.apache.org/repos/dist/dev/ctakes/ctakes-3.1.1/apache-ctakes-3.1.1-src.tar.gz /.zip
 
-
 The tag to be voted on:
 http://svn.apache.org/repos/asf/ctakes/tags/ctakes-3.1.1/
 
@@ -132,13 +131,13 @@ For example:
    https://dist.apache.org/repos/dist/release/ctakes/A.B.C     \
    -m "Copying tag of accepted RC for the release to final actual release tag"
 </pre>
-The svnpubsub will automatically push those to the dist area an all of the mirrors:
+The svnpubsub will automatically push those to the dist area on all of the mirrors:
 You can verify by visiting:
 http://www.apache.org/dist/ctakes/
 
 
 ### Creating Final Tag from RC Tag after VOTE Passes
-For example, if the VOTE for RCX passes for release A.B.C
+For example, if the VOTE for rcX passes for release A.B.C
 <pre>
  svn copy \
    https://svn.apache.org/repos/asf/ctakes/tags/ctakes-A.B.C-rcX  \
@@ -168,7 +167,7 @@ Wait for versions to hit the mirrors (hi
 
 Once release hits send announcement email to announce@a.o and dev@ctakes and user@ctakes. 
 This needs to be done from your @apache.org email address or the email will bounce from the announce list. 
-Gmail forwarding can help here and is a snap [to set up][4]. 
+[Gmail forwarding][4] can help here and is a snap to set up.
 It's even easier then the instructions there as it will recognize your email address and default to Apache settings.
 
 ### Post-announce