On 1/30/14, 7:45 AM, Mark Thomas wrote: > On 30/01/2014 15:34, Gary Gregory wrote: >> On Thu, Jan 30, 2014 at 10:30 AM, Mark Thomas <[email protected]> wrote: >> >>> On 30/01/2014 15:20, Gary Gregory wrote: >>>> Hi All: >>>> >>>> What is the outlook on getting a pool2-based dbcp2? >>> I'm working on that at the moment. There are currently 48 open bugs for >>> DBCP, at least some of which will require API changes to fix. I haven't >>> yet formed an opinion on which ones to fix, which ones to resolve as >>> won't fix and which ones to punt to 3.0. >>> >> Ok, thanks for the update. Sounds like we are still a ways away. > It depends. Based on my experience so far today, a number of the open > issues duplicate known, fixed problems. (Part of the reason for that may > well be the time that has passed since 1.4 was released.) If a few of us > spent a little time on the DBCP bug list I suspect it would shrink > fairly quickly. Any non-committers lurking on this list that want to > help out are more than welcome. Anyone can review a bug, suggest a > patch, identify user error, spot duplicates etc. > > It is looking very much like a DBCP 2 release is on the critical path > for Apache Tomcat 8 to have its first stable release. That means DBCP2 > will be getting a lot of my attention for a while but help is always > welcome.
I will start putting some time into this. > > A release for 1.x (1.5.1, 1.4.1 and 1.3.1 assuming that we want to keep > version numbers aligned and 1.4.x and 1.3.x will be generated from the > 1.5.x branch) may be a helpful stopgap as there have been a lot of > fixes. That is a good idea in any case, as there are going to be users for some time on the old API. > There was talk of not releasing any more 1.3.x releases (Java 1.4 > support - I'd be fine with that). Phil > > Mark > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
