Re: [dbcp] Next

2018-06-17 Thread Rob Tompkins
> On Jun 17, 2018, at 12:38 PM, Matt Sicker wrote: > > Ideally, if we can just keep various branches around in releasable states, > then we can keep old dbcp 2.x.* maintenance releases moving forward. Based > on my experiences trying to release this module before, though, I think > that

Re: [dbcp] Next

2018-06-17 Thread Claude Warren
If we look at java version numbering as 1.x then the argument could be made that each java minor version is really a new version in the semantic numbering scheme. With this in mind then the version number for DBCP should jump when the java version jumps. I would argue that the java 8 version

Re: [dbcp] Next

2018-06-17 Thread sebb
On 16 June 2018 at 22:41, Gary Gregory wrote: > Hello Mark and all, > > Thank you for the heads up on the Tomcat plans. > > Asking DBCP to stay on Java 7 for 4-5 years is insane IMO, and it certainly > is not going to attract anyone to maintain and grow this component (IMO > again.) If that is a

[ANNOUNCEMENT] Apache Commons DBCP 2.4.0 Released.

2018-06-17 Thread Gary Gregory
The Apache Commons DBCP team is pleased to announce the release of Apache Apache Commons DBCP 2.4.0-SNAPSHOT. Apache Commons DBCP software implements Database Connection Pooling. This is a minor release, including bug fixes and enhancements. Changes in this version include: Fixed Bugs: o

Re: [dbcp] Next

2018-06-17 Thread Gary Gregory
The real question is should we change Maven coordinates and package name? I've barely started on JDBC 4.2 and it does not seem required yet. 3.0.0 somewhat implies API breakage which has not happened yet so 2.5.0 is better for now IMO... Gary On Sun, Jun 17, 2018, 04:40 Claude Warren wrote: >

Re: [dbcp] Next

2018-06-17 Thread Matt Sicker
Ideally, if we can just keep various branches around in releasable states, then we can keep old dbcp 2.x.* maintenance releases moving forward. Based on my experiences trying to release this module before, though, I think that process would need to be streamlined and backported. On 17 June 2018

Re: [dbcp] Next

2018-06-17 Thread Gary Gregory
Note that while I am working on getting git master up to JDBC 4.2 on Java 8, the current version is JDBC 4.3 on Java 9. I am only looking at 4.2. Gary On Sun, Jun 17, 2018, 11:06 Rob Tompkins wrote: > > > > On Jun 17, 2018, at 12:38 PM, Matt Sicker wrote: > > > > Ideally, if we can just keep