cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <>
Subject Re: [proposal - take 2] Whiteboard Branches
Date Mon, 02 Aug 2004 12:58:27 GMT
Reinhard Poetz wrote:

> In order to summarize:
> - whiteboard
>   The whiteboard can contain revelutionary stuff like Butterfly or other
>   one-man-shows. They needn't be based on the current codebase - they
>   only have to have some relationship to Cocoon.
>   Evolving from whiteboard needs a vote.
> - branches
>   Branches are based either on previous minor releases (e.g. 2.1.x)
>   or they are future, evolutionary developments based on the codebase
>   that is available at the time of branching. Branches are supported
>   by the community and fixes go into all branches that activly developed.
> - scratchpad (block)
>   Small contributions that don't require a new branch and you want
>   to indicate that this is not supported by the community at the
>   time of committing it. Examples are new components.
>   They still need a vote to be moved into a stable block or into
>   Cocoon core.

Sounds good, with the addition that scratchpad is a kind of incubator 
for unstable features that will go into the core rather than in their 
own block (either because of their small size or because of their 
core-related nature).


Sylvain Wallez                                  Anyware Technologies 
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }

View raw message