It seems that we all agree more or less on moving the blocks out of the core, so which directory structure do we want to use in svn?
We recently had this suggestion: /cocoon/trunk /cocoon/blocks/core/ /cocoon/blocks/supported/ /cocoon/blocks/unsupported/
And then under core, supported, unsupported, come the different blocks with a trunk, tags, releases directory each, right?
yes, e.g.
/cocoon/blocks/core/forms/trunk/ ............. the current forms block /cocoon/blocks/core/forms/branches/ .......... empty for now /cocoon/blocks/core/forms/tags/ .............. empty for now
I think the first step is easy, we could move the blocks to the new directory structure and then use svn:external to link the blocks into the core, so nothing really changes but we are one step further.
an excellent idea. So my work on the build system won't break Cocoon and lowers a bit the pressure to do everything at once.
--
Reinhard Pötz Independant Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}web(log): http://www.poetz.cc --------------------------------------------------------------------
