Reinhard Poetz wrote:
Carsten Ziegeler wrote:Oh wow. I guess I didn't get that. So the proposal IS to have every block on its own release schedule.
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 can't put my finger on why this makes me uneasy, but it does.
It would make me uneasy too if we did it now. But if the infrastructure (solid contracts between a block and core + an easy to use deployment tool) it should be the goal to have independant blocks with their own release cycles.
--
Reinhard P�tz Independant Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}web(log): http://www.poetz.cc --------------------------------------------------------------------
