svn commit: r874505 - in /websites/staging/ctakes/trunk: cgi-bin/ content/ content/ctakes-release-guide.html

[bu...@apache.org]

Author: buildbot
Date: Tue Aug 13 18:32:50 2013
New Revision: 874505

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 Tue Aug 13 18:32:50 2013
@@ -1 +1 @@
-1501295
+1513610

Propchange: websites/staging/ctakes/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Aug 13 18:32:50 2013
@@ -1 +1 @@
-1501295
+1513610

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 Tue Aug 13 18:32:50 2013
@@ -92,7 +92,7 @@ Move any existing open issues to the nex
 <ol>
 <li>Send an email out to ctakes-dev@ with the intention of creating a release and that you will be volunteering for the release manager role.</li>
 <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.0).  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 of 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>
+<li>If B) create a branch from trunk (such svn copy from trunk to branches/3.1.0).  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>
 <h3 id="preparing-your-environment">Preparing your Environment</h3>
@@ -117,7 +117,7 @@ Move any existing open issues to the nex
 </ol>
 <p>This will place the artifacts to the ASF Nexus area for staging for voting.</p>
 <h3 id="preparing-the-rc-for-a-vote">Preparing the RC for a VOTE</h3>
-<p>Send an email like the following with the subject line: [VOTE} Release Apache cTAKES <version> to ctakes-dev@
+<p>Send an email like the following with the subject line: [VOTE} Release Apache cTAKES <version> to dev@ctakes.apache.org
 <pre>
 Hi,
 This is a call for a vote on releasing the following candidate as Apache cTAKES 3.1.0. This will be our first release as a TLP.</p>