Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <4381996A.80408@nada.kth.se>
Date: Mon, 21 Nov 2005 10:54:50 +0100
From: Daniel Fagerstrom <danielf@nada.kth.se>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Planning 2.2
References: <4380C369.4090606@apache.org>
In-Reply-To: <4380C369.4090606@apache.org>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

Carsten Ziegeler wrote:

>Now as 2.1.8 is out, we should think about a 2.2 release. I think for a
>2.2 release we should at least finish the following things:
>
>- Finish the maven2 build
>- Sync everything with 2.1.x (apply changes that were only applied to
>2.1.x if appropriate)
>- Separate samples from blocks
>- Remove author tags
>
>While imho the first two items on the list are a simple must, I think we
>should really do the other ones as well. If we don't aim to do them for
>2.2 we'll simply never do them. And it's really not that hard to do it.
>  
>
+1

>And finally, we should make a stable forms block (and perhaps others as
>well).
>  
>
Would be nice.

The question is if we are going to start to have separate release cycles 
of the blocks with 2.2. In that case the important part is a cocoon-core 
2.2 release. Then we should preferably have releases of CForms, 
Template, Portal and some other important blocks that are compatible 
with the cocoon-core 2.2. But all blocks need not to have stable 
releases some of them can be milestone releases or even "alpha".

IMO we should go for separate release cycles for 2.2. Then the we should 
release "2.2" when the core is stable enough, and consider whether the 
blocks are stable enough, a separate concern.

/Daniel