Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Message-ID: <459A5051.6030504@apache.org>
Date: Tue, 02 Jan 2007 13:30:09 +0100
From: Reinhard Poetz <reinhard@apache.org>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Planing Cocoon Core 2.2 M3
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit


Daniel and Carsten have been investing a lot of time and work into splitting up 
core into smaller pieces and they have also started to transform Avalon 
components into POJOs. The question now is where to draw the line. When is 
everything being considered stable enough (interfaces, classes being in the 
right modules) to be released as release candidate and what should better go 
into point releases or 3.0? Can we render a list of finite tasks?

As discussed some weeks ago, I would like to release Cocoon Core 2.2 M3 by the 
end of the month and have a first release candidate in February.

Comments?

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

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

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