There are still quite a few bugs open against [dbcp] and [pool].  We
also have an unreleased, improved pool impl in the compositepool
package.  I would like to toss out some ideas for discussion about
where to go with these two components and guage interest in helping
out.

Recent releases:  [dbcp] - The 1.2.2 release was a conservative bug
fix release - minimal change while addressing some bugs and upgrading
to [pool] 1.3.
[pool] - 1.3 less conservative vis a vis 1.2, several bug fixes,
including some added synchronization to fix thread safety issues.

Next releases:  [dbcp] - 1.3 close as many of the 1.3-marked bugs as
possible without the new pool impl and add instrumentation using JDK
logging, therefore increasing required JDK level to 1.4.  Resolution
of some issues involving close behavior may have to be deferred to
rework of pool-dbcp connection (move to CompositePools).  Continue
dependency on [pool]'s GOP in this release.  More aggressive bug
fixing, performance improvement -> more testing, public beta required.
Need to talk about a strategy for that.
[pool] - push out a 1.3.1 including fixes applied since 1.3 and if
possible, fixes for POOL-97, POOL-93, with dbcp 1.3 depending on this.
The idea here is the 1.3.x branches of [pool] and [dbcp] continue to
support existing clients with full backward compatibility at JDK 1.4
level, providing bug fixes but no new functionality or APIs.

"2.0"'s:  (Work could begin now on branches, concurrently with 1.x
releases above)
[dbcp]: 2.0 move to CompositePool backing and add JDBC 4 support,
increasing JDK level to 1.5 and removing currently deprecated classes.
If 1.x-incompatible changes are necessary (not obvious at this point
that they are), rename affected packages dbcp2.
[pool]: 2.0 release compositepool package, resolve open pool bugs.
JDK level upped to 1.5. Investigate use of JDK concurrency package to
improve performance and/or resolve some open pool issues.

Comments, suggestions, *volunteers*?

Thanks!

Phil

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

Reply via email to