> From: Stefano Mazzocchi <snip/>
> 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)---+ > > 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. > > thoughts? I think it is a very well-thought proposal. With this lifecycle (state/transition diagram) we also don't have problems with possible interpretations of "supported" because in this context it is very clear and has also the meaning of "official" you proposed yesterday. Reinhard
