Files
commons-xml/status.xml
T
crossley 07876e866c Annotated example CatalogManager.properties
Submitted by: Mark R. Diggory mdiggory<AT>latte.harvard.edu
and started new "Resolver tips" page.


git-svn-id: https://svn.apache.org/repos/asf/xml/commons/trunk@226103 13f79535-47bb-0310-9956-ffa450edef68
2003-09-06 03:43:45 +00:00

147 lines
6.8 KiB
XML

<?xml version="1.0"?>
<status>
<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>
<todo>
<!-- Add todo items. @context is an arbitrary string. -->
<actions priority="high">
<action context="docs" dev="open">
Finish attending to license inconsistencies as per:
<link href="http://marc.theaimsgroup.com/?l=xml-commons-dev&amp;m=106255258125081">Re: some issues with docs: license review</link>
</action>
<action context="docs" dev="open">
Finish initial website. Follow procedure in
<link href="howto-forrest.html">How-to Forrest</link>
</action>
<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&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> and the infrastructure@ list.
</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
(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>
<action context="code" dev="open">
Fix the bugs that are listed in the
<link href="site:issues">Bug database</link> for "XmlCommons".
</action>
</actions>
<actions priority="medium">
<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&amp;m=103766277714207&amp;w=2">[PROPOSAL] xml-commons project organization: several subprojects
</link>
</action>
<action context="build" dev="open">
Decide directory layout. See email:
<link href="http://marc.theaimsgroup.com/?l=xml-commons-dev&amp;m=103734209214955">Repository layout</link>
</action>
<action context="docs" dev="open">
Replace the README file at
<link href="http://xml.apache.org/commons/dist/">http://xml.apache.org/commons/dist/</link>
</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="1.0" date="not-yet-released">
<action type="add" context="docs" dev="crossley"
due-to="Nicola Ken Barozzi" due-to-email="nicolaken@apache.org">
Added the brilliant
<link href="http://nagoya.apache.org/eyebrowse/BrowseList?listName=commons-dev@xml.apache.org&amp;by=thread&amp;from=320776">xml-commons logo</link>.
</action>
<action type="add" context="docs" dev="crossley"
due-to="Mark Diggory" due-to-email="mdiggory@latte.harvard.edu">
Annotated example CatalogManager.properties for Resolver
(see <link href="http://marc.theaimsgroup.com/?l=xml-commons-dev&amp;m=106273408211244">discussion</link>)
and new <link href="components/resolver/tips.html">Tips</link> page.
</action>
</release>
<release version="0.5" date="2003-09-05">
<action type="add" context="docs" dev="curcuru">
Note that this release number is only the release number of the
forrestized-docs, not of the individual components or code.
</action>
<action type="update" context="docs" dev="crossley">
Fixed some license issues in various areas.
</action>
<action type="update" context="docs" dev="crossley">
Improved the build process for docs and consistency between the
website and the distribution. Integrated javadocs with website.
</action>
</release>
<release version="0.4" date="2002-12-20">
<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">
<!-- Some action types have associated images. By default, images are
defined for 'add', 'fix', 'remove' and 'update'. If you add
src/documentation/resources/images/<foo>.jpg images, these will
automatically be used for entries of type <foo>. -->
<!-- Sample action:
<action dev="JB" type="fix" due-to="Joe Contributor"
due-to-email="joec@apache.org">
Fixed a bug in the Foo class.
</action>
-->
<action type="add" context="docs" dev="crossley">
Added placeholder docs and tabs for components.
</action>
</release>
<release version="0.1" date="2002-11-14">
<action type="add" context="docs" dev="crossley">
Built demo website using Forrest. Gleaned content from
<code>xml-commons/README.html</code>
</action>
</release>
</changes>
</status>