commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jakarta-commons Wiki] Update of "DBCP/1.2.2ReleasePlan" by PhilSteitz
Date Mon, 27 Mar 2006 05:34:46 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jakarta-commons Wiki" for change notification.

The following page has been changed by PhilSteitz:
http://wiki.apache.org/jakarta-commons/DBCP/1%2e2%2e2ReleasePlan

The comment on the change is:
Initial creation

New page:
== Release Plan For Commons DBCP 1.2.2 ==

=== Overall Status ===

The release is in the planning stage.

==== Release Manager ====

The release manager is '''TBD'''.

----

=== Background ===

This is a maintenance release.

----

=== Pre Release Tasks ===

==== Source  ====

 * Resolve bugs listed below
 * Eliminate javadoc warnings
 * Ensure javadoc, code and tests match
 * Eliminate test failures

==== Documentation ====

 * Review site docs and improve documentation of exception manangement, documenting current
behavior and indicating things likely to change in 1.3

== Outstanding Bugs ==

||'''ID'''||'''Summary'''||'''Category'''||'''Recommended disposition'''||
||[http://issues.apache.org/bugzilla/show_bug.cgi?id=24718 24718]||PoolableConnectionFactory.validateConnection()
should log exception message||Logging||Fix later||
||[http://issues.apache.org/bugzilla/show_bug.cgi?id=25511 25511]||Allow for database clusters/clustering||Enhancement||Fix
later||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=25696 25696] || initializationStatement
and destructionStatement in PoolableConnectionFactory  || Enhancement  || Fix later ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=25877 25877] || Make exceptions about
closed connections and statements more easily debuggable || Exception management  || Fix later
||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=26759 26759] || Invalidate "broken"
connections by monitoring SQLExceptions || Exception management || Fix later ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=27492 27492] || Pool prepared statements
accross a close (BasicDataSource) || Enhancement|| Fix later ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=27853 27853] || Access to the underlying
connection when using SharedPoolDataSource || Enhancement|| Fix later ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=28211 28211] || Specifying the maximum
lifetime of a connection || Enhancement || Fix later ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=30304 30304] || SharedPoolDataSource
raises exception while closing invalid connection || Exception management || Fix later ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=30375 30375] || Use commons-logging
for debugging instead of System.out.println || Logging || Fix later ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=30391 30391] || Use setQueryTimeout
in combination with validationQuery to recover from network problems || Enhancement || Fix
later ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=31343 31343] || setReadOnly & setAutoCommit
called too many times || Performance || Fix in 1.2.2 ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=31569 31569] || Dbcp doesn't meet JDBC
specification || Enhancement || WontFix ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=32441 32441] || SQLException When PoolablePreparedStatement
Already Closed || Exception management || Fix later ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=32825 32825] || Setting the defaultAutoCommit
property to false breaks the MySQL DataSource || Needs info || Fix later ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=32964 32964] || PoolingDriver.getConnectionPool()
should use contextClassLoader || Enhancement || Fix later ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=33167 33167] || Individual connection
close method || Enhancement || Fix later ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=33912 33912] || Evictor thread in GenericObjectPool
has potential for deadlock || Performance || Fix in 1.2.2 ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=33945 33945] || DelegatingConnection.close()
throws exception || Exception management || Fix later ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=33983 33983] || add/enhance toString()
Method to DelegatingCallableStatement for sql debugging || Enhancement || Fix later ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=34187 34187] || allow to register a
wrapper extending DelegatingPreparedStatement to enhance setString for compatibility ("schema
not null" issue)|| Enhancement || Fix later ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=34490 34490] || Handle changed passwords
in SharedPoolDataSource|| Enhancement || Fix later ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=34539 34539] || Deadlock when evicting
dbcp objects (testWhileIdle=true) || Performance || Fix in 1.2.2 ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=35053 35053] || redesign to use dbcp
with security manager || Enhancement || Fix later||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=35363 35363] || BasicDataSource setter
for connectionProperties || Enhancement || Fix later ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=35542 35542] || docs lie NOT maxIdle
= 0 for no limit BUT -1 || Documentation || Fix in 1.2.2 ||
||[http://issues.apache.org/bugzilla/show_bug.cgi?id=35591 35591] || transactionIsolation,
 testOnBorrow and autoCommmit=false crashes for Oracle || Enhancement || Fix later ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=35825 35825] || NullPointerException
retrieving connection from the pool || Performance || Fix in 1.2.2 ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=36077 36077] || stmt.getConnection()
!= Connection used to create the statement || JDBC compliance || Fix or close before 1.2.2
||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=36561 36561] || [http://forum.java.sun.com/thread.jspa?threadID=658047&tstart=0
Problem reported at forum.java.sun.com] || Is this really a bug?? || ??? ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=37181 37181] || SQLNestedException thrown
by server causes client ClassNotFoundException|| Enhancement || Fix later ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=37577 37577] || I'd like to run init
SQL after JDBC Connection creation in Tomcat DBCP || Enhancement || Fix later ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=37926 37926] || BasicDataSource.createDataSource()
memory leak on SQLExceptions || Exception management || Fix in 1.2.2 ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=38603 38603] || add a socketFactory
attribute to BasicDataSource (to allow SSL "thread"-safe) || Enhancement || Fix later ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=38614 38614] || allow to set >= 6
parameters to do non-global SSL|| Enhancement || Fix later ||
|| [http://issues.apache.org/bugzilla/show_bug.cgi?id=38987 38987] || commons dbcp does not
supports Firebird DB. || Enhancement || Fix later ||


===== Check Compatibility =====

||'''OS'''||'''JDK'''||'''Database(s)'''||'''Tomcat?'''||'''Comments'''||
||Windows 2000||1.3|| || || ||
|| Windows 2000 || 1.4 || || || ||
|| Windows 2000 || 1.5 ||  ||  ||  ||
|| Windows XP || 1.3 ||  ||  ||  ||
|| Windows XP || 1.4 ||  ||  ||  ||
|| Windows XP || 1.5 ||  ||  ||  ||
|| Linux || 1.3 ||  ||  ||  ||
|| Linux || 1.4 ||  ||  ||  ||
|| Linux || 1.5 ||  ||  ||  ||
|| Mac || 1.3 ||  ||  ||  ||
|| Mac || 1.4 ||  ||  ||  ||
|| Mac || 1.5 ||  ||  ||  ||
|| Solaris || 1.3 ||  ||  ||  ||
|| Solaris || 1.4 ||  ||  ||  ||
|| Solaris || 1.5 ||  ||  ||  ||

----

=== Release Tasks ===

==== SVN ====

There will be no release branch, but tags will be created for each release candidate.

==== Release Notes ====

Run clirr / jdiff against 1.2.1 tag and update changes.xml to include all changes since 1.2.1.
 Generate and distribute plain text release notes using maven announcment plugin and customized
jsl.

==== Release Candidates ====

 * The first release candidate will be prepared shortly after the pre-release tasks are done.
 * A reasonable amount of time (a week or two) will be allowed for review and testing.
 * If no issues are reported during the review time, a release VOTE will be called. Vote duration
will be 72 hours. 
 * Above steps will be repeated until a release vote passes.

----

=== Comments ===

Please post comments to the commons-dev mailing list.

----

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


Mime
View raw message