--- Stefano Mazzocchi <[EMAIL PROTECTED]> wrote:
> After a little more thinking, I think that we should avoid placing
> block code in cocoon-2.2 alltogether because we need to start talking
> about the 'community process' of accepting new blocks, where they fit,
> how they get 'certified' and all these things.
>
> So, I agree: let's make cocoon-2.2 and keep all the block code out for
> now (the build process can construct the code from the cocoon-2.1
> repository.
>
> This leaves open a single question: where do we put the various
> block.xml descriptor files? I would say cocoon-2.1 for now and later
> moved them into a new cocoon-blocks module.
>
> What do you think?
>
> --
> Stefano.
>
Lets see if I understood.
We would have three compartments: cocoon-2.1, cocoon-2.2, and cocoon-blocks.
Development would proceed roughly like this:
Step 1:
cocoon-2.1
Contains its own blocks
cocoon-2.2
Retrieves blocks from cocoon-2.1
cocoon-blocks
Empty or non-existent
Step 2:
cocoon-2.1
Contains its own blocks
Learns to retrieve additional blocks from cocoon-blocks
cocoon-2.2
Retrieves blocks from cocoon-2.1
Learns to retrieve additional blocks from cocoon-blocks
cocoon-blocks
Contains blocks markedup with version compatibility information
Some community review setup for contributed blocks
Step 3:
cocoon-2.1
Retrieves blocks from cocoon-blocks
cocoon-2.2
Retrieves blocks from from cocoon-blocks
cocoon-blocks
Contains blocks markedup with version compatibility information
Some community review setup for contributed blocks
--Tim Larson
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
