commons-xml/status.xml
2004-06-22 02:53:37 +00:00

233 lines
11 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>
<actions priority="high">
<action context="build" dev="open">
The 'build dist' for resolver is not picking up the tests and examples
in xml-commons/java/tests/resolver/
</action>
<action context="build" dev="open">
Fix resolver.xml build file to have -src and -bin distros.
</action>
<action context="build" dev="open">
Ensure proper line-endings in .zip and .tar.gz
(evidently .zip is for Win and .tar.gz is for UNIX.
</action>
<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="docs" dev="open">
Update the Resolver
<link href="components/resolver/resolver-release-notes.html">release notes</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://issues.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.) and better jar filenames with a release version number.
</action>
</actions>
</todo>
<changes>
<!-- Add new releases here -->
<release version="xml-commons-1.0" date="not-yet-released">
<action type="add" context="docs" dev="crossley">
Published the new website. Hooray.
</action>
<action type="add" context="docs" dev="crossley"
due-to="Nicola Ken Barozzi" due-to-email="nicolaken@apache.org">
Added the brilliant
<link href="http://issues.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="build" dev="crossley">
Added xml-commons/readme-build.txt to start to explain the build system.
</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>
<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>
<action type="add" context="docs" dev="curcuru">
Added some content as overview for each component.
Added some ToDo items.
</action>
<action type="add" context="docs" dev="crossley">
Added placeholder docs and tabs for components.
</action>
<action type="add" context="docs" dev="crossley">
Built demo website using Forrest. Gleaned content from
<code>xml-commons/README.html</code>
</action>
</release>
<release version="xml-commons-resolver-1.1" date="2003-11-05">
<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>
<action type="add" context="docs" dev="crossley">
Copied the docs built by forrest into the distribution and linked
to javadocs.
</action>
<action type="add" context="docs" dev="ndw">
Added brief descriptions of the following new functionality to the
<link href="site:components/resolver/release-notes">release notes</link> ...
</action>
<action type="add" context="code" dev="ndw">
The <code>CatalogManager</code> class is no longer static. It is now
possible to instantiate several catalog managers and each manager
can manage several catalogs.
</action>
<action type="add" context="code" dev="ndw">
System catalogs are always loaded.
</action>
<action type="add" context="code" dev="ndw">
Tests/Examples available in the <code>tests/resolver/</code> directory.
</action>
<action type="add" context="code" dev="ndw">
Bootstrap resolver for loading catalog files. Avoids the Catch-22
of having to resolve the catalog.dtd before the resolver is in action.
</action>
</release>
<release version="xml-commons-resolver-1.0" date="2002-11-12">
<action type="add" context="build" dev="curcuru">
This release includes just the 1.0 XmlResolver component, by request
from coccoon-dev and others. It is released for users who just want
to use the Resolver and don't need the rest of xml-commons.
Pending discussion on commons-dev, we believe that future xml-commons
releases will be separated out in this manner (external, resolver,
which, etc).
</action>
</release>
<release version="xml-commons-1.0b2" date="2002-02-06">
<action type="add" context="docs" dev="curcuru">
Various LICENSE.* and README.* files for our external sources.
</action>
<action type="add" context="code" dev="curcuru">
New code! org.apache.xml.resolver.Resolver: Norm Walsh's
<link href="site:components/resolver/overview">entity resolver</link>
utility is now checked in and building!
</action>
<action type="add" context="code">
Minor javadoc fixes.
</action>
</release>
<release version="xml-commons-1.0b1" date="2002-01-11">
<action type="add" context="code" dev="curcuru">
<link href="site:components/which/overview">Which</link> -
org.apache.env.Which - a simple environment check utility for
xml-related items in your JVM's environment: 1.0 funtionality working.
</action>
<action type="add" context="code" dev="curcuru">
<link href="site:components/external/overview">External</link> -
java/external/build/xml-apis.jar containing the follow packages:
</action>
<action type="add" context="code" dev="curcuru">
DOM Level 2 including all base files and HTML and CSS DOMs; from
<link href="http://www.w3.org/DOM/">w3c.org</link>
</action>
<action type="add" context="code" dev="curcuru">
JAXP code roughly equivalent to JAXP 1.1.3; for reference releases
from Sun, see
<link href="http://java.sun.com/xml/">java.sun.com/xml</link>
</action>
<action type="add" context="code" dev="curcuru">
SAX 2.0-r2-prerelease and SAX2-ext-1.0; plus bugfixes to
org.xml.sax.helpers.ParserAdapter (make compile in JDK 1.1.x)
and AttributesImpl (minor removeAttribute bug); from megginson.com
although SAX maintenance has now moved to
<link href="http://sax.sourceforge.net/">sax.sourceforge.net</link>
</action>
</release>
<release version="0.1" date="2001-04-26">
<action type="add" context="build" dev="curcuru">
Project started. See <link href="history.html">history</link>.
</action>
</release>
</changes>
<!-- 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" context="code"
due-to="Joe Contributor" due-to-email="joec@apache.org">
Fixed a bug in the Foo class.
</action>
-->
</status>