You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Carsten Ziegeler <cz...@s-und-n.de> on 2002/10/02 14:27:04 UTC

RE: Release Plan for 2.1

Giacomo Pati wrote:
> 
> On Tue, 24 Sep 2002, Carsten Ziegeler wrote:
> 
> > Hi Team,
> >
> > we should start to form at least a plan for 2.1.
> >
> > It seems that one major point, the flow maps, are working well,
> > so the only open point is the "big blocks" thing.
> > I would propose that we shift the "real blocks implementation"
> > to 2.2 and start with the "blocks modules". Nicola has already
> > started this for FOP - Thanks Nicola. And others have followed
> > as well.
> 
> +1 on shifting "real blocks" to 2.2 as the new containers
> (Merlin/Fortress) can be a big help in creating that feature.
> 
Good.

> > Apart from this we have some serious bugs/problems which should
> > be fixed.
> 
> Could you enumerate them?

I know, you know this, but they are all in bugzilla. Have a look at
the blockers, critical and major bugs - perhaps zum normal bugs
are critical as well.

> 
> > If we agree, we could make an alpha release very soon, fix the
> > bugs, move the not finished components into scratchpad, make
> > a beta - let's say by the 18th of November :) - and
> > release 2.1 in december.
> 
> If you think that is possible you'll have my +1
> 
It lies in our own hands - so it should be possible, shouldn't it?

Carsten

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