Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <4381C54B.3010808@apache.org>
Date: Mon, 21 Nov 2005 14:02:03 +0100
From: Carsten Ziegeler <cziegeler@apache.org>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Planning 2.2
References: <4380C369.4090606@apache.org> <4381996A.80408@nada.kth.se>
 <dlse8t$opa$1@sea.gmane.org>
In-Reply-To: <dlse8t$opa$1@sea.gmane.org>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit

Jorg Heymans wrote:

> 
> +1, separate release cycles for more and quicker releases.
> 
> We could start this process incrementally today by just deploying
> snapshots of the 2.2 core jar. No huge announcements or anything, just
> get it out there for the bleeding-edgers and to test the release
> process. Once we feel comfortable we can do the same for a few blocks.
> To avoid the deployment issue, we can opt to just distribute the jars
> and assume the bleeding-edgers being clever enough to add the block
> configuration themselves from the docs.
> 
> In parallel we can maintain a core 2.2 archetype that sets up a working
> webapp structure for the 2.2 core (and perhaps some samples to
> demonstrate). This should satisfy the "curious-but-not-bleeding-edge"
> people in their eagerness to explore the new and noteworthy in 2.2 core.
> 
> 
> How does that sound?
> 
+1

Carsten

-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/