On 4/27/11 8:30 AM, Gary Gregory wrote: > IMO: > > DBCP 1.4 for JDBC 4 (JDK 1.6) > => Bump it to 2.0. > > DBCP 1.3 for JDBC 3 (JDK 1.4-1.5) > => Stays as is. This is essentially the plan that we agreed to a year ago. The only difference in what you have above is that we will likely cut at least another 1.3.1/1.4.1 pair including bug fixes. The idea is that the JDBC 3 stuff is bug fix only at this point and the 2.0 version will support only JDBC 4. The 2.0 version will not be source and binary compatible with 1.4 (so will end up being o.a.c.dbcp2). I am trying now to get 1.3.1/1.4.1 ready while it is still easy to port fixes to trunk before we repackage and get trunk working with pool2. Help with the open bugs against 1.3/1.4 would be most appreciated.
Phil > Gary > > On Wed, Apr 27, 2011 at 9:05 AM, sebb <seb...@gmail.com> wrote: > >> All Commons components other than DBCP have at most one current >> version per major release (e.g. NET has 1.4.1 and 2.2). >> >> DBCP uses a different versioning scheme from all other components: >> >> DBCP 1.4 for JDBC 4 (JDK 1.6) >> DBCP 1.3 for JDBC 3 (JDK 1.4-1.5) >> >> This is rather confusing. >> >> Seems to me it would be better to move to a naming scheme that did not >> rely on the minor version number to distinguish JDBC versions. >> >> Instead of >> >> commons-dbcp-1.3-bin.zip >> commons-dbcp-1.4-bin.zip >> >> perhaps we should have >> >> commons-dbcp-2.0-jdbc3-bin.zip >> commons-dbcp-2.0-jdbc4-bin.zip >> >> or >> >> commons-dbcp-jdbc3-2.0-bin.zip >> commons-dbcp-jdbc4-2.0-bin.zip >> >> [It does not help that the README.html file only describes the 1.4 >> release; I'll fix that] >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org