Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (herse.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Message-ID: <4580F38F.8090407@apache.org>
Date: Thu, 14 Dec 2006 07:47:43 +0100
From: Reinhard Poetz <reinhard@apache.org>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [vote] Releasing from trunk (cocoon-core-2.2.0-M2 and others)
References: <4572BAF3.4050001@apache.org> <457D6E4C.30306@apache.org>
 <20061213070519.GB5941@igg.indexgeo.com.au> <457FD609.70901@apache.org>
 <20061214041647.GA14796@igg.indexgeo.com.au>
In-Reply-To: <20061214041647.GA14796@igg.indexgeo.com.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

David Crossley wrote:

> Hmmm, sorry, i see them now. Not sure what i was looking at then.
> I am happy about the "sources" aspect now, so +1 from me.

fine :-)

> I thought that the "milestone" naming was something leading
> up to a release, and intended for developers.
> 
> So at what point do we drop the "-M*" appendage?

Some time ago we decided that we want to name our releases milestones instead of 
  beta as long as we don't want to guarentee that the API is stable.

I have no idea when we will drop the -M' appendage. The next steps are providing 
documentation and splitting up core as Daniel proposed some hours ago.

When this is done and after getting feedback from a wider audience then a 
handful committers, we should turn into RC (release candiate) mode.

-- 
Reinhard P�tz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------

		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de