RE: Let's clean Cocoon and modularize it (was: Cocoon Organization(Cocoon plugins))

[Leigh Dodds <ld...@ingenta.com>]

Just to jump in a spend my two euros:

One thing that ought that I think should be collectively 
thought about is whether modularization (or indeed, 
anything) can help stabilise particular aspects of Cocoon 
such that they can be clearly labelled as stable/core, etc.

This is an issue that I've encountered when proposing that
Cocoon be deployed into a commercial environment. 
Essentially: "if we build an application on this version of 
Cocoon, are we going to easily migrate to newer versions 
of the software without having to rearchitect the application".

It seems that there are some aspects of Cocoon that are 
undergoing fairly radical changes -- I keep seeing mention 
of changes to the Sitemap processing model (blocks?) 
for instance -- this is off-putting when you can a stable 
platform for your application.

Cheers,

L.

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org