Return-Path: 
 <cocoon-dev-return-40865-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 50638 invoked by uid 500); 28 Apr 2003 10:06:12 -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 50623 invoked from network); 28 Apr 2003 10:06:12 -0000
Received: from grunt24.ihug.com.au (203.109.249.144)
  by daedalus.apache.org with SMTP; 28 Apr 2003 10:06:12 -0000
Received: from p261-apx1.syd.ihug.com.au (expresso.localdomain)
 [203.173.141.7]
	by grunt24.ihug.com.au with esmtp (Exim 3.35 #1 (Debian))
	id 19A5Wi-0006VJ-00; Mon, 28 Apr 2003 20:06:24 +1000
Received: from jeff by expresso.localdomain with local (Exim 3.35 #1 (Debian))
	id 19A5X1-00042q-00
	for <cocoon-dev@xml.apache.org>; Mon, 28 Apr 2003 20:06:43 +1000
Date: Mon, 28 Apr 2003 20:06:42 +1000
From: Jeff Turner <jefft@apache.org>
To: cocoon-dev@xml.apache.org
Subject: Re: Releasing 2.1-B1
Message-ID: <20030428100642.GB3844@expresso.localdomain>
Mail-Followup-To: cocoon-dev@xml.apache.org
References: <LKENJPKDAIKAPKHEOCMMOEAGDHAA.cziegeler@s-und-n.de>
 <3EACF1CD.4080100@outerthought.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3EACF1CD.4080100@outerthought.org>
User-Agent: Mutt/1.5.3i
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On Mon, Apr 28, 2003 at 11:18:05AM +0200, Steven Noels wrote:
> On 28/04/2003 9:58 Carsten Ziegeler wrote:
> 
> >Hi,
> >
> >is anything preventing us from releasing 2.1-b1 today or tomorrow?
> >If not, I will try my best to get it out :)
> 
> +1, and as-is.

+1

...
> W.r.t. nomenclature, we could go for 'Release Candidate' until APIs are 
> solid, and 'Beta' once we stabilized contracts. Another scheme however 
> might be 'Milestone', which carries no connotation of releasing a final 
> version any time soon.
> 
> Cocoon 2.1 M1 -> Mn -> (APIs solid) beta -> RC (for the impatient) -> final

+1 for Milestones.  Certainly it's better than redefining 'beta'.  IIUC,
Release Candidates happen just before a final release, so wouldn't be
suitable here.

--Jeff

> </Steven>