Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 60294 invoked from network); 7 Jun 2005 05:36:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Jun 2005 05:36:47 -0000 Received: (qmail 45497 invoked by uid 500); 7 Jun 2005 05:36:44 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 45472 invoked by uid 500); 7 Jun 2005 05:36:44 -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 List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 45459 invoked by uid 99); 7 Jun 2005 05:36:44 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from viefep14-int.chello.at (HELO viefep14-int.chello.at) (213.46.255.13) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 06 Jun 2005 22:36:43 -0700 Received: from [192.168.1.31] (really [62.178.239.20]) by viefep12-int.chello.at (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20050607053317.UWZY2846.viefep12-int.chello.at@[192.168.1.31]> for ; Tue, 7 Jun 2005 07:33:17 +0200 Message-ID: <42A53197.7030409@apache.org> Date: Tue, 07 Jun 2005 07:33:11 +0200 From: Reinhard Poetz User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: Marking cforms stable in 2.1.8 References: <42A499AA.4020801@dslextreme.com> In-Reply-To: <42A499AA.4020801@dslextreme.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Ralph Goers wrote: > We have a project that needs to use a forms framework that is more > advanced than what SimpleForms provides. However, it is difficult on > selling cforms simply because they are marked unstable. What is it > going to take to mark it stable in 2.1.8? Can we simply identify the > known bugs in bugzilla and mark it stable? > Frankly, given the number of folks who appear to be using cforms > already, and since this list has been recommending it for the last year, > we should probably be treating it as stable now. If I wrote block.xml for cFroms I would fill in the "state" section as follows: We have to finish the Flowscript API, review the repeater binding and flatten the forms.xconf entries to get the interfaces stable too. (http://wiki.apache.org/cocoon/22StabilizeCocoonForms) -- Reinhard P�tz Independent Consultant, Trainer & (IT)-Coach {Software Engineering, Open Source, Web Applications, Apache Cocoon} web(log): http://www.poetz.cc --------------------------------------------------------------------