svn commit: r835480 - in /websites/staging/ctakes/trunk/content: ./ ctakes/ctakes-release-guide.html

[bu...@apache.org]

Author: buildbot
Date: Thu Oct 18 16:06:49 2012
New Revision: 835480

Log:
Staging update by buildbot for ctakes

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

Propchange: websites/staging/ctakes/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Oct 18 16:06:49 2012
@@ -1 +1 @@
-1399711
+1399714

Modified: websites/staging/ctakes/trunk/content/ctakes/ctakes-release-guide.html
==============================================================================
--- websites/staging/ctakes/trunk/content/ctakes/ctakes-release-guide.html (original)
+++ websites/staging/ctakes/trunk/content/ctakes/ctakes-release-guide.html Thu Oct 18 16:06:49 2012
@@ -82,7 +82,7 @@
 </ul>
   </div>
   <div id="contenta">
-    <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. When the code base is in a satisfactory state a release branch would be created under https://svn.apache.org/repos/asf/incubator/ctakes/tags.  The maven release plug-in (mvn release:prepare/perform) is recommend for this purpose.</p>
+    <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. When the code base is in a satisfactory state a release branch would be created under https://svn.apache.org/repos/asf/incubator/ctakes/tags.  The maven release plug-in (mvn release:prepare/perform) is recommended for this purpose.</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.</p>
 <p>Finally the release manager would trigger the release build, sign the generated artifacts and host them on https://dist.apache.org/repos/dist/dev/incubator/ctakes for review (Also 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>
   </div>