Yeah, no problem. No huge memory leak for 1.0. :)

-----Original Message-----
From: Dion Gillard [mailto:[EMAIL PROTECTED] 
Sent: Sunday, September 19, 2004 6:58 PM
To: Hans Gilde
Subject: Re: Jelly and a 1.0 release

That sounds like a good idea.

I've also been following your work on the memory leak situation, and
if it's possible would like to get that into a 1.0 of jelly, as it's a
major issue for some people.

Sound ok?


On Sun, 19 Sep 2004 19:37:14 -0400, Hans Gilde
<[EMAIL PROTECTED]> wrote:
> Maybe the public API task should also be put off for 1.1. It seems to me
> that any of the suggestions would result in somewhat significant API
> changes. We could make it clear in the 1.0 release that the Java API will
> change but the Tag libs form a stable XML API.
> 
> 
> 
> -----Original Message-----
> From: Dion Gillard [mailto:[EMAIL PROTECTED]
> Sent: Friday, September 17, 2004 1:02 AM
> To: Jakarta Commons Developers List; Jakarta Commons Users List
> Subject: Jelly and a 1.0 release
> 
> There's currently one issue in Jira for Jelly Core against v1.0, which
> is the public API.
> 
> If there is anything people want fixed for 1.0, please enter it into JIRA
> ASAP.
> 
> Please note that the taglibs are now able to be released separately
> from Jelly Core, so fixing those is a separate thing to getting the
> core released.
> 
> Our focus at the moment is to fix bugs, do documentation and make a
> stable Jelly release. Major re-work and  API changes should wait till
> the 1.1 timeframe.
> 
> The plan is to release 1.0 soon, and not wait a long time like the
> beta-3 to beta-4 timeframe.
> --
> http://www.multitask.com.au/people/dion/
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 



-- 
http://www.multitask.com.au/people/dion/


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to