Return-Path: 
 <cocoon-dev-return-40287-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 8538 invoked by uid 500); 12 Apr 2003 14:47:15 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 8522 invoked from network); 12 Apr 2003 14:47:15 -0000
Received: from unknown (HELO host.leverageweb.com) (64.91.232.157)
  by daedalus.apache.org with SMTP; 12 Apr 2003 14:47:15 -0000
Received: from 66-44-57-5.s259.tnt2.lnhva.md.dialup.rcn.com ([66.44.57.5]
 helo=geoff2k)
	by host.leverageweb.com with asmtp (Exim 3.36 #1)
	id 194MEZ-0004SN-00
	for cocoon-dev@xml.apache.org; Sat, 12 Apr 2003 10:43:59 -0400
From: "Geoff Howard" <cocoon@leverageweb.com>
To: <cocoon-dev@xml.apache.org>
Subject: RE: [proposal] rethinking distribution strategy
Date: Sat, 12 Apr 2003 11:03:21 -0400
Message-ID: <CAEFLDPFNJFPMBLBKFLOIEFACEAA.cocoon@leverageweb.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <3E9721D2.50403@apache.org>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
X-AntiAbuse: This header was added to track abuse,
 please include it with any abuse report
X-AntiAbuse: Primary Hostname - host.leverageweb.com
X-AntiAbuse: Original Domain - xml.apache.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0]
X-AntiAbuse: Sender Address Domain - leverageweb.com
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

I'd be for it - but what about bugs marked blocking 2.1 release?  And 
what about pending major changes to central contracts (flow)?  
How do we avoid getting stalled in beta?  

Geoff

> -----Original Message-----
> From: Stefano Mazzocchi [mailto:stefano@apache.org]
> 
<snip/>
> I propose the following:
> 
>  1) release Cocoon 2.1 beta *RIGHT NOW*. This means package what we have
> and shipt it. No cleanup, no todo list, no docs to add, nothing. Just
> "build dist" and go go go.
<snip/>
> 
> What do you think?
>