[ogsa-dai svn] SF.net SVN: ogsa-dai:[1651] ogsa-dai/trunk/release-scripts/ogsa-dai/doc/src /DocBook/Misc/ReleaseNotes.xml

[<mik...@us...>]

Revision: 1651
          http://ogsa-dai.svn.sourceforge.net/ogsa-dai/?rev=1651&view=rev
Author:   mikej888
Date:     2011-03-01 10:58:28 +0000 (Tue, 01 Mar 2011)

Log Message:
-----------
Added some fixed bugs and redid features list, updated Java and Linux versions in tested platforms

Modified Paths:
--------------
    ogsa-dai/trunk/release-scripts/ogsa-dai/doc/src/DocBook/Misc/ReleaseNotes.xml

Modified: ogsa-dai/trunk/release-scripts/ogsa-dai/doc/src/DocBook/Misc/ReleaseNotes.xml
===================================================================
--- ogsa-dai/trunk/release-scripts/ogsa-dai/doc/src/DocBook/Misc/ReleaseNotes.xml	2011-03-01 10:57:52 UTC (rev 1650)
+++ ogsa-dai/trunk/release-scripts/ogsa-dai/doc/src/DocBook/Misc/ReleaseNotes.xml	2011-03-01 10:58:28 UTC (rev 1651)
@@ -41,6 +41,16 @@
  Add a <listitem> for each major new feature. Just a sentence or two. 
 -->
 <listitem>
+Ability to convert and transfer relational data in a
+binary format from an OGSA-DAI server to a client. This is a more
+efficient format than WebRowSet yet avoids the information loss
+issues of comma-separated values.
+</listitem>
+<listitem>
+TupleToByteArrays activity now allows relational data
+to be extracted as a JDBC ResultSet.
+</listitem>
+<listitem>
 Support for RDF resources which allows querying of Jena SDB databases
 and SPARQL endpoints using SPARQL.  
 </listitem>
@@ -52,17 +62,12 @@
 Support for modulo function in DQP.
 </listitem>
 <listitem condition="daiaxis1">
-The client toolkit now uses HTTP Keep Alive by default, 
-hence increasing efficiency.
+Use of HTTP Keep Alive by default in the client toolkit providing
+improved efficiency of client-server interactions.
 </listitem>
 <listitem>
 Numerous bug fixes.
 </listitem>
-<listitem>
-Ability to convert and transfer relational data in (more efficient) binary format from 
-an OGSA-DAI server to a client. TupleToByteArrays activity now allows relational data
-to be extracted as JDBC ResultSet.
-</listitem>
 </itemizedlist>
 </para>
 
@@ -96,7 +101,7 @@
  
 <para>
 OGSA-DAI 4.1 has been tested as follows. All tests are run on 
-Linux Red Hat 9 using Apache ANT 1.7.0
+Scientific Linux SL release 5.5 (Boron) using Apache ANT 1.7.0.
 </para>
 
 <table id="TestedPlatforms4.1Table">
@@ -115,7 +120,7 @@
 <tbody>
 <row condition="daiaxis1">
 <entry>OGSA-DAI 4.1 Axis 1.4</entry>
-<entry>1.6.0_16</entry>
+<entry>1.6.0_22</entry>
 <entry>Yes</entry>
 <entry>Yes</entry>
 <entry>Yes</entry>
@@ -123,7 +128,7 @@
 </row>
 <row condition="daigt4">
 <entry>OGSA-DAI 4.1 GT 4.2.0</entry>
-<entry>1.6.0_16</entry>
+<entry>1.6.0_22</entry>
 <entry>Yes</entry>
 <entry>Yes</entry>
 <entry>Yes</entry>
@@ -134,8 +139,9 @@
 </table>
 <para>
 Database-specific tests have been run on all the databases listed in
-<xref linkend="DataResourceProducts"/> (except SQL Server 2005/8). 
-Client-server tests were run using MySQL, eXist and Linux file system resources. 
+<xref linkend="DataResourceProducts"/>. 
+Client-server tests were run using MySQL, eXist and Linux file
+system resources. DQP client-server tests were run using MySQL.
 </para>
 </section>
 
@@ -394,6 +400,10 @@
 <ulink url="http://sourceforge.net/apps/trac/ogsa-dai/ticket/251">251</ulink>.
 <ulink url="http://sourceforge.net/apps/trac/ogsa-dai/ticket/252">251</ulink>.
 <ulink url="http://sourceforge.net/apps/trac/ogsa-dai/ticket/254">254</ulink>.
+<ulink url="http://sourceforge.net/apps/trac/ogsa-dai/ticket/294">294</ulink>.
+<ulink url="http://sourceforge.net/apps/trac/ogsa-dai/ticket/306">306</ulink>.
+<ulink url="http://sourceforge.net/apps/trac/ogsa-dai/ticket/307">307</ulink>.
+<ulink url="http://sourceforge.net/apps/trac/ogsa-dai/ticket/316">316</ulink>.
 <!-- Add as you fix. -->
 </listitem>
 </itemizedlist>


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.