cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Poetz <reinh...@apache.org>
Subject Re: Marking cforms stable in 2.1.8
Date Tue, 07 Jun 2005 05:33:11 GMT
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:

<state
  community="stable"
  interfaces="unstable"
  implementation="stable"/>

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
--------------------------------------------------------------------

Mime
View raw message