I'd stick with 2.x since it's still backwards compatible. Upgrading the base Java version is not a semantic change IMO, but it shouldn't be done in a patch release.
On 19 June 2018 at 16:48, Gary Gregory <[email protected]> wrote: > To be clear: > > DBCP 2.4.0 - Java 7 - JDBC 4.1 (just released) > DBCP 2.5.0 or 3.0.0 - Java 8 - JDBC 4.2 (in git master) > DBCP 2.6.0 or 4.0.0 - Java 9 - JDBC 4.3 (to do) > > Thoughts? > > Gary > > > > On Tue, Jun 19, 2018 at 2:28 PM Gary Gregory <[email protected]> > wrote: > > > I have no API breaking changes for 3.0, so I do not see a need for a > major > > version change. Feedback welcome. I am more interested in getting the > next > > version out to pick up the new methods from JDBC 4.2 on Java 8. > > > > Gary > > > > On Tue, Jun 19, 2018, 13:49 Matt Sicker <[email protected]> wrote: > > > >> Bumping to 3.0 could allow for adopting lessons from other connection > pool > >> libraries in API incompatible ways. I have no specific examples, but > >> HikariCP is a general one. > >> > >> On 19 June 2018 at 14:27, Jochen Wiedmann <[email protected]> > >> wrote: > >> > >> > On Sun, Jun 17, 2018 at 2:42 PM Gary Gregory <[email protected]> > >> > wrote: > >> > > >> > > 3.0.0 somewhat implies API breakage which has not happened yet so > >> 2.5.0 > >> > is > >> > > better for now IMO... > >> > > >> > +1 for going to 3.0.0 anyways. This would perhaps fix the problem for > >> > Tomcat, assuming that we keep a maintenance branch for 2.x. > >> > > >> > Jochen > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: [email protected] > >> > For additional commands, e-mail: [email protected] > >> > > >> > > >> > >> > >> -- > >> Matt Sicker <[email protected]> > >> > > > -- Matt Sicker <[email protected]>
