ctakes-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r888523 - in /websites/staging/ctakes/trunk: cgi-bin/ content/ content/ctakes-release-guide.html
Date Fri, 29 Nov 2013 15:38:39 GMT
Author: buildbot
Date: Fri Nov 29 15:38:38 2013
New Revision: 888523

Log:
Staging update by buildbot for ctakes

Modified:
    websites/staging/ctakes/trunk/cgi-bin/   (props changed)
    websites/staging/ctakes/trunk/content/   (props changed)
    websites/staging/ctakes/trunk/content/ctakes-release-guide.html

Propchange: websites/staging/ctakes/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Nov 29 15:38:38 2013
@@ -1 +1 @@
-1545851
+1546583

Propchange: websites/staging/ctakes/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Nov 29 15:38:38 2013
@@ -1 +1 @@
-1545851
+1546583

Modified: websites/staging/ctakes/trunk/content/ctakes-release-guide.html
==============================================================================
--- websites/staging/ctakes/trunk/content/ctakes-release-guide.html (original)
+++ websites/staging/ctakes/trunk/content/ctakes-release-guide.html Fri Nov 29 15:38:38 2013
@@ -84,8 +84,8 @@
   <div id="contenta">
     <h2 id="how-does-ctakes-manage-releases">How does cTAKES manage releases?</h2>
 <p>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).</p>
 <p>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.
 Move any existing open issues to the next release.</p>
@@ -94,7 +94,7 @@ Move any existing open issues to the nex
 <li>Decide if you like to A) freeze any development in trunk until the release has
been completed. B) Create a branch that this release will be created from and development
in trunk could continue.</li>
 <li>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.</li>
 </ol>
-<p>Finally the release manager would trigger the release build, sign the generated
artifacts and host them on Apache Nexus &amp; 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.</p>
+<p>Finally the release manager would trigger the release build, sign the generated
artifacts and host them on Apache Nexus &amp; 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.</p>
 <h3 id="preparing-your-environment">Preparing your Environment</h3>
 <ol>
 <li>Read: <a href="http://www.apache.org/dev/publishing-maven-artifacts.html">http://www.apache.org/dev/publishing-maven-artifacts.html</a></li>
@@ -102,7 +102,7 @@ Move any existing open issues to the nex
 </ol>
 <h3 id="preparing-a-release-using-maven">Preparing a Release using Maven</h3>
 <p>Note: Using 3.1.1 as an example</p>
-<p>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.</p>
+<p>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.</p>
 <ol>
 <li>$svn co https://svn.apache.org/repos/asf/ctakes/trunk ctakes</li>
 <li>$mvn release:clean</li>
@@ -145,7 +145,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/
 
@@ -184,11 +183,11 @@ 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/</p>
 <h3 id="creating-final-tag-from-rc-tag-after-vote-passes">Creating Final Tag from RC
Tag after VOTE Passes</h3>
-<p>For example, if the VOTE for RCX passes for release A.B.C
+<p>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  \
@@ -222,7 +221,7 @@ Once the release hits:</p>
 <p>Wait for versions to hit the mirrors (hint: keep checking <a href="http://www.apache.org/dyn/closer.cgi/ctakes">http://www.apache.org/dyn/closer.cgi/ctakes</a>
until you see something).</p>
 <p>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 <a href="http://gmailblog.blogspot.com/2009/07/send-mail-from-another-address-without.html">to
set up</a>. 
+<a href="http://gmailblog.blogspot.com/2009/07/send-mail-from-another-address-without.html">Gmail
forwarding</a> 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.</p>
 <h3 id="post-announce">Post-announce</h3>
 <p>After announce, if the release included a new component, 



Mime
View raw message