Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 32778 invoked from network); 12 Nov 2003 10:57:42 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 12 Nov 2003 10:57:42 -0000 Received: (qmail 87247 invoked by uid 500); 12 Nov 2003 10:57:13 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 87078 invoked by uid 500); 12 Nov 2003 10:57:12 -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 87064 invoked from network); 12 Nov 2003 10:57:12 -0000 Received: from unknown (HELO kerberos) (62.116.51.59) by daedalus.apache.org with SMTP; 12 Nov 2003 10:57:12 -0000 Received: From mail.at.efp.cc ([62.116.51.60]) by kerberos (WebShield SMTP v4.5 MR1a); id 1068634644116; Wed, 12 Nov 2003 11:57:24 +0100 Received: from WRPO (wrpo.at.intra.efp.cc [194.107.80.23]) by mail.at.efp.cc (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id hACAvMX07213 for ; Wed, 12 Nov 2003 11:57:23 +0100 From: "Reinhard Poetz" To: Subject: RE: [RT] ComponentizedProcessor (was RE: Migrating TreeProcessor to Fortress) Date: Wed, 12 Nov 2003 11:56:41 +0100 Message-ID: <000a01c3a90b$a83d9b50$1e01a8c0@WRPO> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-Reply-To: Importance: Normal 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 From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de] > > I'm wondering if we should write this new sitemap engine in the 2.2 > > branch or if it should go in the 2.1. Fortress isn't a > requirement to > > implement this, and it will allow us to provide views and resource > > inheritance before the 2.2 is out. > > > I think we shouldn't change the running implementation for > 2.1, let's do it for 2.2 and if it is the "killer > implementation", we can move it to 2.1 later on anyway. But > for now, we should focus on 2.2 and see that we get a > startable cocoon version again :) +1 -- Reinhard