Add building of resolver docs to draft website build with Forrest.

git-svn-id: https://svn.apache.org/repos/asf/xml/commons/trunk@226027 13f79535-47bb-0310-9956-ffa450edef68

status.xml

@@ -23,11 +23,25 @@
         <link href="http://nagoya.apache.org/eyebrowse/ReadMsg?listName=commons-dev@xml.apache.org&amp;msgNo=39">making TCK-compliant API's common</link>
         (Actually is neilg,ilene)
       </action>
+      <action context="build" dev="open">
+        Establish efficient distribution mirrors
+        and change the download link on the xml-commons website. See doc
+        <link href="http://cvs.apache.org/~bodewig/mirror.html">Making your downloads mirrorable</link>
+      </action>
+      <action context="docs" dev="open">
+        Fix broken links in resolver-article.xml ... only three, but important
+        ones: download, copyright, and apidocs.
+      </action>
       <action context="build" dev="open">
         Decide how to build separate distributable docs for each "component",
-        and how they will also be published to xml-commons website. Best if
-        xdocs content can remain in /java with their code. See email:
+        and how they will also be published to xml-commons website
+        (since resolver, which, etc. will get shipped as individual components,
+        even though they live in the same project).
+        Best if xdocs content can remain in /java with their code.
+        See email:
         <link href="http://marc.theaimsgroup.com/?l=xml-commons-dev&amp;m=103736060229424">draft website for xml-commons using Forrest</link>
+        and
+        <link href="http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=103967656107408">a website with separate distributable components</link>
       </action>
     </actions>
     <actions priority="medium">
@@ -63,13 +77,24 @@
 
   <changes>
     <!-- Add new releases here -->
-    <release version="0.3" date="2002-11-19">
+    <release version="0.4" date="2002-12-20">
       <action type="add" context="docs" dev="curcuru">
         Note that this release number is only really the release number of the 
         forrestized-docs, not of the individual components or code.  
-        ### Fixme: figure out how to use this part of forrest on an individual 
-        component kind of basis (since resolver, which, etc. will get shipped 
-        as individual components, even thought they live in the same project).
+      </action>
+      <action type="add" context="docs" dev="crossley">
+        Added experimental building of the Resolver component docs using
+        DocBook DTDs and XSL.
+      </action>
+      <action type="add" context="docs" dev="crossley">
+        Added some ToDo items and noted some issues in 
+        <link href="howto-forrest.html">How-to Forrest</link>.
+      </action>
+    </release>
+    <release version="0.3" date="2002-11-19">
+      <action type="add" context="docs" dev="curcuru">
+        Added some content as overview for each component.
+        Added some ToDo items.
       </action>
     </release>
     <release version="0.2" date="2002-11-16">