Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 27344 invoked from network); 2 Sep 2003 10:40:57 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 2 Sep 2003 10:40:57 -0000 Received: (qmail 57421 invoked by uid 500); 2 Sep 2003 10:40:50 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 57337 invoked by uid 500); 2 Sep 2003 10:40:49 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 57231 invoked from network); 2 Sep 2003 10:40:45 -0000 Received: from unknown (HELO lapgp.otego.com) (195.216.81.146) by daedalus.apache.org with SMTP; 2 Sep 2003 10:40:45 -0000 Received: (qmail 5242 invoked from network); 2 Sep 2003 10:40:20 -0000 Received: from localhost (127.0.0.1) by localhost with SMTP; 2 Sep 2003 10:40:20 -0000 Date: Tue, 2 Sep 2003 12:40:19 +0200 (CEST) From: Giacomo Pati Sender: giacomo@lapgp.otego.com To: dev@cocoon.apache.org cc: 'Carsten Ziegeler' , bloritsch@apache.org Subject: RE: [VOTE] Migrate from the aging ECM In-Reply-To: <000a01c37112$caf6d570$dd506bc2@WRPO> Message-ID: References: <000a01c37112$caf6d570$dd506bc2@WRPO> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Tue, 2 Sep 2003, Reinhard Poetz wrote: > > From: Reinhard Poetz [mailto:reinhard@apache.org] > > > > > From: Berin Loritsch > > > > > > > > The new Cocoon should be able to use the new Fortress > > > container. This should have little to no impact on component > > > writers. It boasts faster startup, and it provides easier > > > component definition. I will be happy to do the work. > > > > > > +1 from me. > > > > +1 from me > > Please wait until Cocoon 2.1.1 (with working scheduler for continuation > invalidation) is shipped. I would have a better feeling if we could test > the new container some time before it is released. Otherwise we would > have a good reason to delay 2.1.1 for a (too) long time and IMO we > shouldn't wait to long with a new minor release. > > What do you think of the Sept, 15th releasing 2.1.1? Good for me. -- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com