Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 90813 invoked by uid 500); 30 Sep 2002 11:57:46 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 90788 invoked from network); 30 Sep 2002 11:57:45 -0000 Date: Mon, 30 Sep 2002 13:57:43 +0200 (CEST) From: Giacomo Pati Sender: giacomo@localhost To: Cocoon-Dev Subject: Re: Release Plan for 2.1 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 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. > Apart from this we have some serious bugs/problems which should > be fixed. Could you enumerate them? > 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 > We could then use the dark winter season for implementing blocks > and make a 2.2 early next year. Ok Giacomo --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org