cziegeler 2003/03/05 23:22:27
Modified: . todo.xml
Log:
Updating todo
Revision Changes Path
1.50 +11 -22 xml-cocoon2/todo.xml
Index: todo.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/todo.xml,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -r1.49 -r1.50
--- todo.xml 31 Jan 2003 15:00:43 -0000 1.49
+++ todo.xml 6 Mar 2003 07:22:27 -0000 1.50
@@ -31,23 +31,20 @@
</devs>
<actions priority="high">
- <action context="code" assigned-to="open">
- For 2.1: Rewrite the FilesystemStore. The current implementations relies on
- a correct implementation of the toString() method of the used
- keys. A correct version should rely on hashCode() and equals().
- (This is actually an Avalon action as the code is in Excalibur)
- </action>
-
- <action context="code" assigned-to="open">
- For 2.1: Implement the smart-caching for the processing pipeline and
- iron out bugs.
- </action>
-
- <action context="docs" assigned-to="open">
+ <action context="code" assigned-to="CZ">
+ Redesign the SitemapConfigurable handling.
+ </action>
+
+ <action context="docs" assigned-to="open">
For 2.1: Attend to any high+ issues in the
<link href="plan/todo-doc.html">Documentation To Do List</link>
</action>
+ <action context="code" assigned-to="open">
+ For 2.1: use (only) released versions of excalibur (xml, source, store etc).
+ This requires a release of those components in excalibur.
+ </action>
+
<action context="code" assigned-to="open">
Complete (means put everything we know of into even if it has to be
commented) the cocoon.xconf file and put descriptions into it
@@ -87,14 +84,6 @@
<action context="code">
For 2.1: Make a guide on how to upgrade Cocoon, and see how this can be eased.
- </action>
-
- <action context="code">
- For 2.1: Check how to handle the mixing of output streams when an error inside
- a pipeline occurs. When the pipeline has something written to the
- output stream and then an error occurs the result is the first written
- part with the appended exception.
- One solution could be a configurable intermediate output stream.
</action>
<action context="code">
