Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 29286 invoked from network); 9 Mar 2004 15:07:50 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 9 Mar 2004 15:07:50 -0000 Received: (qmail 5257 invoked by uid 500); 9 Mar 2004 15:07:41 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 5202 invoked by uid 500); 9 Mar 2004 15:07:41 -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 5182 invoked from network); 9 Mar 2004 15:07:40 -0000 Received: from unknown (HELO otsrv1.iic.ugent.be) (157.193.121.51) by daedalus.apache.org with SMTP; 9 Mar 2004 15:07:40 -0000 Received: from [192.168.123.115] (host115 [192.168.123.115]) by otsrv1.iic.ugent.be (8.11.6/8.11.6) with ESMTP id i29F7fO14371 for ; Tue, 9 Mar 2004 16:07:41 +0100 Mime-Version: 1.0 (Apple Message framework v612) In-Reply-To: <404DDBE0.1080600@s-und-n.de> References: <4049F275.5000906@apache.org> <404DA633.6010306@apache.org> <5DFD0EA4-71BB-11D8-9FA2-000A958B684A@outerthought.org> <404DB5BD.5030500@apache.org> <404DBF2A.9060703@apache.org> <404DC35C.80804@reverycodes.com> <404DC793.8080408@s-und-n.de> <404DCA3D.1060807@reverycodes.com> <404DD804.70008@vafer.org> <404DDBE0.1080600@s-und-n.de> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <82848D7C-71DB-11D8-9FA2-000A958B684A@outerthought.org> Content-Transfer-Encoding: 7bit From: Steven Noels Subject: Re: [CocoonForms] END of code freeze Date: Tue, 9 Mar 2004 16:07:40 +0100 To: dev@cocoon.apache.org X-Mailer: Apple Mail (2.612) 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 09 Mar 2004, at 15:59, Guido Casper wrote: > Torsten Curdt wrote: >> Shouldn't one be able to keep the old block >> and use 2.1.5-dev? ...as an interim solution? > > Yes, I can live with that. But I think it's not a good sign for our > users. A user should have a chance to migrate while using a released > version. +1 - and I think most of us who have production users will agree with that. I don't want to slow down the process, but also don't want to lose users by force-feeding them migration work they haven't catered for. This is just a temporary solution, and in due time new features will emerge from the official cforms branch that will make them do the switch at their own pace. -- Steven Noels http://outerthought.org/ Outerthought - Open Source Java & XML An Orixo Member Read my weblog at http://blogs.cocoondev.org/stevenn/ stevenn at outerthought.org stevenn at apache.org