Return-Path: Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 10818 invoked by uid 500); 18 Jul 2003 10:39:30 -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 10801 invoked from network); 18 Jul 2003 10:39:29 -0000 Received: from imap.gmx.net (HELO mail.gmx.net) (213.165.64.20) by daedalus.apache.org with SMTP; 18 Jul 2003 10:39:29 -0000 Received: (qmail 2044 invoked by uid 65534); 18 Jul 2003 10:39:28 -0000 Received: from unknown (EHLO WRPO) (193.81.161.142) by mail.gmx.net (mp009) with SMTP; 18 Jul 2003 12:39:28 +0200 Reply-To: From: =?iso-8859-1?Q?Reinhard_P=F6tz?= To: Subject: RE: [Vote] Controller/Sitemap integration Date: Fri, 18 Jul 2003 12:39:34 +0200 Message-ID: <003601c34d18$e2752df0$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 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N From: Stephan Michels > But nevertheless, I like most ... I could write again *my* best way of integrating it but I don't see the value of delaying the release because of this neverending discussion. So I'm +1 to release the flow implementation as it is ASAP and discuss this again when the second implementation is on the table. As already mentioned there will be only littly changes necessary for flow users (not more changes than with 2.0 --> 2.1). Before being off-list for about 10 days I'll summarize the current status of the flow implementation. Expect a mail soon. Cheers, Reinhard