Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <434EC8F6.4090905@apache.org>
Date: Thu, 13 Oct 2005 22:52:06 +0200
From: Reinhard Poetz <reinhard@apache.org>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: ApplesProcessor - a little crazy idea
References: <434E7BCB.4090206@mobilebox.pl> <434E8075.2050902@apache.org>
 <434E831D.806@mobilebox.pl> <0BD69214-64A9-4634-AFA5-B741F9DAB8C1@apache.org>
 <434E8C6B.7010702@reverycodes.com> <434E8F8E.60407@dslextreme.com>
 <434EBBDB.90106@apache.org> <434EC74D.20700@dslextreme.com>
In-Reply-To: <434EC74D.20700@dslextreme.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Ralph Goers wrote:
> Reinhard Poetz wrote:
> 
>> Ralph Goers wrote:
>>
>>> I second that.  We really need to find a better term than "stable".
>>
>>
>>
>> One of those discussions hitting us every 3 to 6 months. Anyway, last 
>> time we agreed (for blocks) that we split up stability into three parts:
>>
>>  - api
>>  - implementation
>>  - community
>>
>> This is also reflected by the block.xml schema. Anything new this time?
> 
> 
> I don't recall the last discussion. Obviously, if there was an agreement 
> nothing was done about it.
> 
> Currently gump.xml only has status="value".  How do the 3 parts get 
> reflected into that?  How does the fact that the api is stable but the 
> implementation needs to be verified get presented so that we can easily 
> see that?

http://svn.apache.org/repos/asf/cocoon/trunk/src/schema/cob-schema-1.0.xsd

--> see the complex type "state"


-- 
Reinhard P�tz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------