Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 25716 invoked by uid 500); 28 Apr 2003 10:58:44 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 25653 invoked from network); 28 Apr 2003 10:58:43 -0000 Received: from nebula.mpn.com (194.72.64.30) by daedalus.apache.org with SMTP; 28 Apr 2003 10:58:43 -0000 Delivered-To: <> Received: from [10.11.155.40] (tashayarr-ext.vnu.co.uk [193.117.79.10]) by nebula.mpn.com (8.8.5/8.8.5) with ESMTP id LAA15884 for ; Mon, 28 Apr 2003 11:58:31 +0100 User-Agent: Microsoft-Entourage/10.1.1.2418 Date: Mon, 28 Apr 2003 12:01:21 +0100 Subject: Re: Releasing 2.1-B1 From: Pier Fumagalli To: Message-ID: In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N "Carsten Ziegeler" wrote: > Steven Noels wrote: > >> Cocoon 2.1 M1 -> Mn -> (APIs solid) beta -> RC (for the >> impatient) -> final >> > Very good suggestion! I like Milestone! > So, this could your first pmc chair action... :) Same here... I like the concept of milestones... It's pretty hard to define if something can be considered "alpha" or "beta" quality code without feedback from users... IIRC, in Apache 2.0 all milestones were/are labeled as 2.0.milestone and then, after a little bit of feedback it was decided where to promote the milestone as alpha or beta... Turned out to be a good approach... +1 on Cocoon 2.1m1 (or 2.1.1) now, clearly labeled as non-final! :-) Pier