cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Pötz <reinh...@apache.org>
Subject Re: [VOTE RESULT] javaflow
Date Thu, 01 Apr 2004 11:07:41 GMT
Carsten Ziegeler wrote:

>Ok, we guess we can continue this discussion forever :)
>I would say, do what you think is better, we will see what
>happens.
>  
>

+1
Carsten, I like your pragmatic approaches ;-)

Best,
Reinhard

>>-----Original Message-----
>>From: Reinhard Pötz [mailto:reinhard@apache.org] 
>>Sent: Thursday, April 01, 2004 12:53 PM
>>To: dev@cocoon.apache.org
>>Subject: Re: [VOTE RESULT] javaflow
>>
>>Torsten Curdt wrote:
>>
>>    
>>
>>>>>but then I'd propose to disable *all* unstable blocks
>>>>>
>>>>>          
>>>>>
>>>>Oh no, please not because this will lead to everyone wanting to 
>>>>declare his favorite block "stable" :)
>>>>        
>>>>
>>>don't wanna bitch around but... if you want prevent users to use 
>>>unstable code (or at least make them aware of the fact) we should 
>>>handle blocks all the same.
>>>
>>>and as you see with the midi block
>>>...if we can consider it stable it'll
>>>become marked stable. no big deal.
>>>      
>>>
>>I think so too. Either all unstable blocks are disabled or noone.
>>
>>    
>>
>>>I don't think "stable" has anything to do with preference 
>>>      
>>>
>>but instead 
>>    
>>
>>>how it has proven to be stable in production over time.
>>>      
>>>
>>... and IMO there must be more than one person willing to support it. 
>>(of course no guarantee that it will be supported forever but 
>>it increases the chances)
>>
>>--
>>Reinhard
>>    
>>

Mime
View raw message