You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-cvs@xml.apache.org by cu...@apache.org on 2002/11/20 02:03:38 UTC
cvs commit: xml-commons status.xml
curcuru 2002/11/19 17:03:38
Modified: . status.xml
Log:
Very basic status of xml-commons docs (not necessarily sources) updated
Hey - wireless works at ApacheCon!
Revision Changes Path
1.2 +34 -5 xml-commons/status.xml
Index: status.xml
===================================================================
RCS file: /home/cvs/xml-commons/status.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- status.xml 16 Nov 2002 12:59:48 -0000 1.1
+++ status.xml 20 Nov 2002 01:03:38 -0000 1.2
@@ -4,6 +4,9 @@
<developers>
<person name="Shane Curcuru" email="curcuru@apache.org" id="curcuru" />
<person name="David Crossley" email="crossley@apache.org" id="crossley" />
+<person name="Neil Graham" email="neilg@ca.ibm.com" id="neilg" />
+<person name="Ielen Seeleman" email="ilene@ca.ibm.com" id="ilene" />
+<person name="Norman Walsh" email="ndw@apache.org" id="ndw" />
<person name="Volunteer needed" email="commons-dev@xml.apache.org" id="open"/>
<!-- Add more people here -->
</developers>
@@ -15,8 +18,10 @@
Finish initial website. Follow procedure in
<link href="howto-forrest.html">How-to Forrest</link>
</action>
- <action context="docs" dev="open">
- Tweak the initial content for the top-level docs.
+ <action context="code" dev="neilg">
+ Update versions of external DOM/SAX/JAXP code to best-possible that still passes TCK-JAXP-1.2.
+ <link href="http://nagoya.apache.org/eyebrowse/ReadMsg?listName=commons-dev@xml.apache.org&msgNo=39">making TCK-compliant API's common</link>
+ (Actually is neilg,ilene)
</action>
<action context="build" dev="open">
Decide how to build separate distributable docs for each "component",
@@ -26,9 +31,12 @@
</action>
</actions>
<actions priority="medium">
- <action context="docs" dev="open">
- Add top-level documents about each resource that is provided by
- xml-commons.
+ <action context="architecture" dev="open">
+ Basic consensus building/comments about explicitly shipping various
+ portions of xml-commons as separate components.
+ See email:
+ <link href="http://marc.theaimsgroup.com/?l=xml-commons-dev&m=103766277714207&w=2">[PROPOSAL] xml-commons project organization: several subprojects
+ </link>
</action>
<action context="build" dev="open">
Decide directory layout. See email:
@@ -38,11 +46,32 @@
Replace the README file at
<link href="http://xml.apache.org/commons/dist/">http://xml.apache.org/commons/dist/</link>
</action>
+ <action context="build" dev="open">
+ Move the distribution area to be more mirror-friendly (see infrastructure@ list)
+ </action>
+ </actions>
+ <actions priority="low">
+ <action context="docs" dev="open">
+ Better overview doc of why xml-commons has it's own sets of DOM/SAX/JAXP; also
+ basic docs on TCK compliance etc.
+ </action>
+ <action context="architecture" dev="open">
+ Discussion and concensus on packaging of external DOM/SAX/JAXP interfaces (xml-apis.jar etc.).
+ </action>
</actions>
</todo>
<changes>
<!-- Add new releases here -->
+ <release version="0.3" date="2002-11-19">
+ <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>
+ </release>
<release version="0.2" date="2002-11-16">
<!-- Some action types have associated images. By default, images are
defined for 'add', 'fix', 'remove' and 'update'. If you add