You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@accumulo.apache.org by el...@apache.org on 2014/03/14 19:14:03 UTC

svn commit: r1577646 - /accumulo/site/trunk/content/release_notes/1.5.1.mdtext

Author: elserj
Date: Fri Mar 14 18:14:03 2014
New Revision: 1577646

URL: http://svn.apache.org/r1577646
Log:
ACCUMULO-2473 Better verbage

Modified:
    accumulo/site/trunk/content/release_notes/1.5.1.mdtext

Modified: accumulo/site/trunk/content/release_notes/1.5.1.mdtext
URL: http://svn.apache.org/viewvc/accumulo/site/trunk/content/release_notes/1.5.1.mdtext?rev=1577646&r1=1577645&r2=1577646&view=diff
==============================================================================
--- accumulo/site/trunk/content/release_notes/1.5.1.mdtext (original)
+++ accumulo/site/trunk/content/release_notes/1.5.1.mdtext Fri Mar 14 18:14:03 2014
@@ -160,8 +160,8 @@ The following documentation updates were
 
 ## Testing
 
-Below is a list of all platforms that 1.5.1 was tested against by developers. A value of *All* in the "Tests"
-column mean that all required release tests were run on this platform. That list includes the following:
+Below is a list of all platforms that 1.5.1 was tested against by developers. Each Apache Accumulo release
+has a set of tests that must be run before the candidate is capable of becoming an official release. That list includes the following:
 
  1. Successfully run all unit tests
  2. Successfully run all functional test (test/system/auto)
@@ -170,7 +170,7 @@ column mean that all required release te
  5. Successfully complete two 72-hour Continuous Ingest tests, with and without "agitation"
 
 Each unit and functional test only runs on a single node, while the RandomWalk and Continuous Ingest tests run 
-on a number of nodes. *Agitation* refers to randomly killing Accumulo processes, Hadoop Datanode processes,
+on any number of nodes. *Agitation* refers to randomly restarting Accumulo processes and Hadoop Datanode processes,
 and, in HDFS High-Availability instances, forcing NameNode failover.
 <table id="release_notes_testing">
   <tr>