Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 4948 invoked by uid 500); 25 Sep 2002 00:44:31 -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 4937 invoked from network); 25 Sep 2002 00:44:31 -0000 Message-ID: <13c901c2642c$77565380$0100a8c0@MAUCHI> From: "Ivelin Ivanov" To: References: Subject: Re: Release Plan for 2.1 Date: Tue, 24 Sep 2002 19:42:45 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Sounds good to me. The sooner we freeze the interfaces the better. Since there were so many major additions to 2.1, I am expecting that it will take more than a month for the beta to become final. So maybe a release in January is a bit more feasible, but we will see how it goes. Do we currently have a minimal deployment Ant target? It is just wonderful that you can deploy a minimal JBoss under 2MB. That still includes the web server, JMS, JMX, JTA, Timer and many other services. Regards, Ivelin ----- Original Message ----- From: "Carsten Ziegeler" To: "Cocoon-Dev" Sent: Tuesday, September 24, 2002 7:13 AM Subject: Release Plan for 2.1 > 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. > > Apart from this we have some serious bugs/problems which should > be fixed. > > 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. > > We could then use the dark winter season for implementing blocks > and make a 2.2 early next year. > > So, what do you think? > > Carsten > > Carsten Ziegeler Chief Architect Open Source Group, S&N AG > ------------------------------------------------------------------ > Cocoon Consulting, Training and Projects > ------------------------------------------------------------------ > mailto:cziegeler@s-und-n.de http://www.s-und-n.de > http://ziegeler.bei.t-online.de > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > For additional commands, email: cocoon-dev-help@xml.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org