commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Phil Steitz <phil.ste...@gmail.com>
Subject [dbcp] 2.2 plan - feedback requested
Date Sun, 12 Jul 2015 20:18:25 GMT
There are a few decisions to make before we start rolling RCs for
DBCP 2.2.  I would appreciate feedback / patches for the following:

DBCP-436
Seems a reasonable request but hard to implement and test.  I would
say either WONT_FIX or bump to 3.0.  I am curious about how
important this actually is with modern drivers (i.e., whether there
actually is much cost in what we are doing in the 2.x line).

DBCP-438
I need help reviewing the code here.  The null check fix makes the
symptom go away, but I suspect there is a deeper problem here.

DBCP-427
I agree with Vladmir's comment on the re-open, but am hesitant to
change default behavior in a . release.  Interested in other
opinions on this.

DBCP-388
Can moves down the road as [pool] does not yet support this. So bump
to 2.3.

Thanks in advance!

Phil


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


Mime
View raw message