Stefano Mazzocchi wrote: > > <SNIP/> > > +1 let's give it a shot. This is probably what Carsten was picturing > > all along. :) > > +1 as well. the magic "build script that gets missing blocks from 2.1" > would simply be a cvs checkout, followed with a few file copy > operations. > Yes, I thought of that, too, so: +1 (of course ;) ) > > 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. > +100
> 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. > Ok. Carsten
