cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bertrand Delacretaz <bdelacre...@codeconsult.ch>
Subject Re: Block Management [was Re: on better release and version management]
Date Fri, 26 Sep 2003 05:29:46 GMT
Le Jeudi, 25 sep 2003, à 12:45 Europe/Zurich, Stefano Mazzocchi a écrit 
:
> ...I think that "contributed" and "experimental" are somewhat 
> orthogonal, in fact, linotype can be considered both contributed and 
> experimental....

Agreed.

> ...So:
>
>  contributed -> no broad community support
>
>  supported -> broad community support
>
>  deprecated -> community either moved onto something else or dropped 
> the concept alltogether....
>
> NOTE: a contributed block might find itself deprecated without never 
> being supported. This is the full state/transition diagram:
>
>              +------------------(rebirth)-----------------+
>              v                                            |
> -(birth)-> [contributed] ----------(death)---------> [deprecated]
>              |                                            ^
>              +--(maturity)-> [supported] --(retirement)---+

+1, looks good!

> the transitions that require community vote (majority) are:
>
>  - maturity
>  - retirement
>
> the other transitions can be done by every committer in every project 
> under control of the cocoon PMC and require only a "proposal" to be 
> discussed on the cocono development mail list.

+1 as well.

-Bertrand

Mime
View raw message