DPML Notify

[mcconnell at BerliOS <mcconnell AT mail.berlios.de>]

Author: mcconnell
Date: 2006-08-16 07:39:13 +0200 (Wed, 16 Aug 2006)
New Revision: 1737

Modified:
   trunk/central/site/src/docs/about/download/index.xml
   trunk/central/site/src/docs/about/news/index.xml
   trunk/index.xml
Log:
more doc corrections

Modified: trunk/central/site/src/docs/about/download/index.xml
===================================================================
--- trunk/central/site/src/docs/about/download/index.xml        2006-08-14 
18:03:11 UTC (rev 1736)
+++ trunk/central/site/src/docs/about/download/index.xml        2006-08-16 
05:39:13 UTC (rev 1737)
@@ -76,6 +76,7 @@
           </tr>
         </table>
         
+        <!--
         <p>
         Changes and/or enhancements include:
         </p>
@@ -83,6 +84,7 @@
         <ul>
           <li>Correction to the lookup tutorial documentation.</li>
         </ul>
+        -->
         
         <p>
         Please refer to the README.TXT file included in the distribution for 

Modified: trunk/central/site/src/docs/about/news/index.xml
===================================================================
--- trunk/central/site/src/docs/about/news/index.xml    2006-08-14 18:03:11 
UTC (rev 1736)
+++ trunk/central/site/src/docs/about/news/index.xml    2006-08-16 05:39:13 
UTC (rev 1737)
@@ -12,9 +12,25 @@
 
     <section name="News &amp; Events">
     
-      <subsection name="27 July 2006 Formal 1.0.0 Release">
+      <subsection name="11 Agust 2006, DPML SDK 1.0.1 Release">
       
         <p>
+        Changes in this release include the addition of a new command-line 
option to the Depot build
+        tool enabling a decimal version build policy together with some 
internal implementation 
+        enhancements that enable the generation of a full DPML system build 
using the Depot build 
+        system.  The decimal versioning option basically addresses 
functional requirements that arise
+        when evaluating the impact of small changes on dependent systems.  
In addition version 1.0.1
+        introduces the ability within the DPML build to run the entire build 
under Depot (as opposed 
+        to the earlier bootstrap+Depot build sequence).  With full 
Depot-based build sequencing in 
+        place its now much easier to address subjects such as build system 
reporting and general 
+        shortcomings in larger scale multi-project management.
+        </p>
+        
+      </subsection>
+      
+      <subsection name="27 July 2006 DPML SDK 1.0.0 Release">
+      
+        <p>
         The DPML is proud to announce the formal distribution 
         of version <tt>1.0.0</tt> of the DPML SDK.
         </p>
@@ -41,6 +57,23 @@
           
           <tr>
           
+            <td><b><i>Metro</i></b></td>
+        
+            <td>
+            Metro is an advanced deployment strategy for plugins.  In effect 
Transit plugin definitions
+            allow for the declaration of alternative object deployment 
strategies.
+            While the basic Transit plugin model supports a generic 
framework (including antlib
+            resources loading) - the Metro system goes orders of magnitude 
further in its provision 
+            for lifecycle management, custom lifestyle, Context-IOC, remote 
management, 
+            logging, and other features aimed at composite component 
management.  The Metro platform 
+            also includes a the 'Station' - in effect a server handles 
multiple JVMs and provides 
+            support for remote application management.
+            </td>
+            
+          </tr>
+          
+          <tr>
+          
             <td><b><i>Depot</i></b></td>
 
             <td>
@@ -69,23 +102,6 @@
         
           </tr>
           
-          <tr>
-          
-            <td><b><i>Metro</i></b></td>
-        
-            <td>
-            Metro is a next-gen deployment strategy for plugins.  In effect 
Transit plugin definitions
-            allow for the declaration of alternative object deployment 
strategies.
-            While the basic Transit plugin model supports a simple generic 
framework (including antlib
-            resources loading) - the Metro system goes orders of magnitude 
further in its provision 
-            for composite objects, lifecycle management, custom lifestyle, 
Context-IOC, remote management, 
-            logging, and bunch other stuff that makes for very easy 
development.  The Metro platform 
-            also includes a the 'Station' - in effect a server handles 
multiple JVMs and provides 
-            support for remote application management.
-            </td>
-            
-          </tr>
-          
         </table>
       
       </subsection>

Modified: trunk/index.xml
===================================================================
--- trunk/index.xml     2006-08-14 18:03:11 UTC (rev 1736)
+++ trunk/index.xml     2006-08-16 05:39:13 UTC (rev 1737)
@@ -18,7 +18,7 @@
     <property name="project.javadoc.linksource" value="true"/>
     <property name="project.major.version" value="1"/>
     <property name="project.minor.version" value="0"/>
-    <property name="project.micro.version" value="2"/>
+    <property name="project.micro.version" value="1"/>
   </properties>
   
   <module name="dpml" basedir="main">