Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: pass (herse.apache.org: domain of phil.steitz@gmail.com
 designates 66.249.90.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=Zx5VoZR1Ih8XS7bzLYY6A198pubVOw3j237vAjErarNM/91/5/xLrQWJPqK0Oplc90dD1rfc25+JHjQWHp9s+YEol3D3FUOxsKlEwYlZTu/MZ+yvWB6yQSczAmBJARPa0UO2wQ6StIg2ofY9TfFAfotCIg2b93qMQTKESMnD1yA=
Message-ID: <8a81b4af0706212132v6e5da76cpceb61e2fe52890df@mail.gmail.com>
Date: Thu, 21 Jun 2007 21:32:46 -0700
From: "Phil Steitz" <phil.steitz@gmail.com>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Subject: [pool] 2.0 releaese WAS: [jira] Commented: (POOL-98) Make
 GenericObjectPool better extensible
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Leaving the ticket because this is really general discussion.

<snip.>
>
> ok, I can understand this. Any time frame on compositepool / what is needed to get the code release-ready?

As with all things apache, that depends on available volunteer cycles.
 I posted a straw man roadmap for both [pool] and [dbcp] earlier this
week (http://marc.info/?l=jakarta-commons-dev&m=118237533115289&w=4).
Comments are welcome.  There are some bugs open against the
GenericObjectPool impl that I think we should fix in a pool 1.3.1 or
1.4 that could in theory be worked (and maintained) concurrently with
pool 2.0.  I am willing to do the grunt RM work if others will step up
to contribute and most of all review and test.  The compositepool impl
is in good shape but needs review and testing.  There are also some
things that could be added or improved if we up the JDK requirement to
1.5 so we can use the concurrent package.

Another reason to patch 1.3 is to address things like POOL-97,
POOL-93, POOL-102, POOL-86 for direct users of GenericObjectPool and
to provide a drop-in fix for tomcat and others who use pool with dbcp
while we work on moving dbcp to use pool 2.0.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org