Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <3E647755.5000206@apache.org>
Date: Tue, 04 Mar 2003 10:52:21 +0100
From: Stefano Mazzocchi <stefano@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.3b) Gecko/20030202
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: Stabilizing flow in order to release
References: <MLEAJJEAAELCMLAIJNFIIEPMFMAA.mlangham@s-und-n.de>
In-Reply-To: <MLEAJJEAAELCMLAIJNFIIEPMFMAA.mlangham@s-und-n.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Matthew Langham wrote:
>>At the same time, Cocoon 2.1-dev has to reach beta state ASAP since we
>>are nearly feature complete and our internal cleanups and refactoring
>>are working very well. [in a followup I will outline what's missing
>>before release]
>>
> 
> 
> Just to add slightly to this from my area - there are quite a few large
> companies using 2.1-dev (and happy with it). However they are having major
> problems both internally (inside their corporations) and externally (being
> able to announce publically that they are using Cocoon) because of the fact
> that 2.1-dev is not at least beta.
> 
> The longer this takes - the more likely that this could be damaging to
> commercial adoption of Cocoon.

Yep.

Let's roll up our sleeves and do it.

Executive summary for release schedule coming up next.

-- 
Stefano Mazzocchi                               <stefano@apache.org>
    Pluralitas non est ponenda sine necessitate [William of Ockham]
--------------------------------------------------------------------