get documantation ready for pre release

documentation/RELEASE_NOTES.html

@@ -1,4 +1,4 @@
-<h1>Release release/3.1 IN DEVELOPMENT</h1>
+<h1>Release 4.0 IN DEVELOPMENT</h1>
 <p>The main changes since release 3.0.2 are:</p>
 <ul>
 <li>array semantics now enforce Copy On Write.</li>

documentation/RELEASE_NOTES.md

@@ -1,4 +1,4 @@
-Release release/3.1 IN DEVELOPMENT
+Release 4.0 IN DEVELOPMENT
 ===========
 
 The main changes since release 3.0.2 are:

documentation/TODO.html

@@ -9,9 +9,9 @@ that are treated like a top level field.</p>
 <p>Currently if a subField of any of these is changed postMonitor is not called for the field itself.</p>
 <p>David asked if this could be changed so that it is called.
 Marty thinks this may not be a good idea.</p>
-<h2>timeStamp, display, control, and valueAlarm</h2>
-<p>normativeTypes.html defines time_t,  display_t, control_t, and alarmlimit_t.
-The definitions are not compatible with how property defined timeStamp, display, control, and valueAlarm.
-The definition of alarm_t does match the definition of property alarm.</p>
+<h2>valueAlarm</h2>
+<p>normativeTypes.html describes valueAlarm only for a value field that has type
+double.
+The implementation also supports all the numeric scalar types.</p>
 <h2>monitorPlugin</h2>
 <p>A debate is on-going about what semantics should be.</p>

documentation/TODO.md

@@ -23,12 +23,13 @@ Currently if a subField of any of these is changed postMonitor is not called for
 David asked if this could be changed so that it is called.
 Marty thinks this may not be a good idea.
 
-timeStamp, display, control, and valueAlarm
-----------
 
-normativeTypes.html defines time_t,  display_t, control_t, and alarmlimit_t.
-The definitions are not compatible with how property defined timeStamp, display, control, and valueAlarm.
-The definition of alarm_t does match the definition of property alarm.
+valueAlarm
+---------
+
+normativeTypes.html describes valueAlarm only for a value field that has type
+double.
+The implementation also supports all the numeric scalar types.
 
 monitorPlugin
 -------------

documentation/pvDataCPP.html

@@ -46,11 +46,11 @@
     </dd>
     <dt>This version:</dt>
     <dd><a
-      href="pvDataCPP_20140708.html">pvDataCPP_20140708.html</a>
+      href="pvDataCPP_20140723.html">pvDataCPP_20140723.html</a>
     </dd>
     <dt>Previous version:</dt>
     <dd><a
-      href="pvDataCPP_20140501.html">pvDataCPP_20140501.html</a>
+      href="pvDataCPP_20140708.html">pvDataCPP_20140708.html</a>
     </dd>
     <dt>Editors:</dt>
     <dd>Marty Kraimer, BNL</dd>
@@ -78,8 +78,6 @@ V4 control system programming environment:<br />
 
 <h2 class="nocount">Status of this Document</h2>
 
-<p>For now this is a working copy so it is not the same as "This version" shown above.</p>
-
 <p>This is the 23-July-2014 version of the C++ implementation of pvData.
 </p>