cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <>
Subject RE: The road to Cocoon 2.1
Date Mon, 17 Mar 2003 13:46:04 GMT
Stefano Mazzocchi wrote:
> > For 2.1 we have some additional points in our todo list in cvs
> > that have to be solved before a final release.
> Bring them on.
>From the todo.xml (perhaps some of them are obsolete; perhaps some are not

  <action context="code" assigned-to="CZ">
   Redesign the SitemapConfigurable handling.

 <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 context="code" assigned-to="open">
   For 2.1: use (only) released versions of excalibur (xml, source, store
   This requires a release of those components in excalibur.

  <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

  <action context="build" assigned-to="open">
   Complete (means put all allowed constructs and combinations)
   the lint/sitemap.xmap file. Enhance the RELAX NG grammar for sitemap.

  <action context="code" assigned-to="SW">
   For 2.1: Views must start not from the first encountered label, but from
the last one

  <action context="code" assigned-to="NKB">
   For 2.1: Make comprehensive samples with the handle-errors sitemap and
real world
   use cases. Add also specific Selector and a FaqBuilder to be used by the
   as a NotifyingBuilder.

  <action context="code" assigned-to="SW">
   Change the handle-errors to enable use of any Generator.

  <action context="code">
   Remove all useless blank strings in XSP-generated code that hinder
   This should be configurable (through an attribute?) to be able to keep
them when

  <action context="code">
   For 2.1: Make a guide on how to upgrade Cocoon, and see how this can be

  <action context="code">
   For 2.1: Redesign FragmentExtractorGenerator/Transformer so that it works
on a clustered
   server : store fragments in the session rather than in a local store.


View raw message