Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <402A038D.6070104@gmx.de>
Date: Wed, 11 Feb 2004 11:27:25 +0100
From: Joerg Heinicke <joerg.heinicke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.6) Gecko/20040113
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [IMP] End of code freeze - new release plan
References: <OF55DDA0E6.7E7B25CD-ONC1256E37.00379FE1@sundn.de>
In-Reply-To: <OF55DDA0E6.7E7B25CD-ONC1256E37.00379FE1@sundn.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

On 11.02.2004 11:13, Carsten Ziegeler wrote:
> As already announced this is the end of the code freeze without a release :(
> 
> Any ideas about a possible new release date? Please keep in mind that if we 
> don't do a release this month we have to switch to the new licence as well
> (and this includes not only java files, but also xml, xsl and so on!).
> So, I fear a realistic date for the next release is somewhere middle/end of
> march.
> 
> WDYT?

To be honest I do not really understand this. There were 3 blocking 
issues (the minus in the vote): Javascript XSP, internal request memory 
leak and Jisp. Javascript is fixed, for the memory leak we have a 
working patch and for the JISP my -0.1 depends on the worthiness of the 
patch. Maybe the patch to the memory leak is so bad that we can not 
apply it ...?

Joerg