wrote up explaining why tests are done on committed code.

git-svn-id: svn://svn.berlios.de/openocd/trunk@428 b42882b7-edfa-0310-969c-e2dbd0fdcd60

1 files changed, 1 insertions, 1 deletions

diff --git a/testing/index.html b/testing/index.html
index 267c2a7b..88f7ff59 100644
--- a/testing/index.html
+++ b/testing/index.html
@@ -16,7 +16,7 @@
 		All of the above makes it imperative that there can be no doubt about *which* code
 		is tested and thus all tests refer to committed code by subversion number.  
 		<h1>Release procedure</h1>
-		OpenOCD trunk is work in progress. Expect it to change daily and to have some work in progress.
+		OpenOCD trunk is work in progress. Expect it to change daily and to have some quirks.
 		<p>If you need the latest released and tested version, look for binary snapshots of OpenOCD. Worst case look up the test result table below for the features that are important to you and extract and build the version that has the right cocktail of working features for you. You can also work with the community to address the problems you are seing. Testing work and bug reports are highly appreciated.</p>
 		<p>The OpenOCD community may decide to create release branches. If this happens, then a branch will be created from OpenOCD trunk. The particular version to create that branch might be an older version rather than the latest and greatest. Fixes are then ported to that release branch from OpenOCD trunk.</p>
 		<h2>Vocabulary</h2>