cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hunsberger, Peter" <>
Subject RE: on better release and version management
Date Tue, 23 Sep 2003 14:05:39 GMT
Stefano Mazzocchi <> writes:


> Instead of associating 'maturity levels' to the actual location of a 
> block, I would state that as a 'label' attached to it, a 
> label that the 
> block deployer reacts to and prompt the user for action in case the 
> block is not considered "final" by the community.
> That would:
>   1) keep the freedom to initiate as many blocks developers want
>   2) avoid the 'move things around' CVS dance
>   3) allow easy and mechanizable checking of which blocks are 
> considered 
> "stamped" by the cocoon community.
> so, the only thing left is to define how you get those blocks 
> "stamped", but I think it would just require a community vote with a 
> majority.
> Such "stamping" should be done thru the use of a digital 
> certificate so 
> that the block deployer can say "this is a block certified by the 
> cocoon community as final".

Hmm, I think you don't mean "final" as in can't be touched, but more
like, "stable" or "certified as not being dangerous", or maybe
"certified as now being an official part of Cocoon"?

View raw message