Phil Steitz wrote: > Mark Thomas wrote: >> I have finished working my way through the open POOL bugs. >> >> Of the remaining issues, 2 are bugs that only affect the 2.0 branch and >> rest are improvements. >> >> Given that Tomcat is waiting on a DBCP release and DBCP is waiting on a >> POOL release I would like to progress a POOL 1.5 release asap. >> >> Does POOL have a usual release manager? If so, do they want to do this >> release? If not, I'll start working my way through the release >> procedures. >> > Big +1 for releasing and THANKS for plowing through the backlog of > issues. I did the last release and will do this one so you can focus > your available cycles on DBCP - unless you are dying to learn the > try-as-we-might-will-always-be-a-black-art commons release process. Or > unless some other victi...er, I mean "volunteer" steps up.
Thanks for the offer. I must confess I feel no great urge to learn this particular black art ;) That said, if there is anything I can do to help just let me know. > I have not reviewed the POOL-75 patches completely yet, but looks like a > *big* improvement. Thanks again for taking this on. I will also start > running my zoo of concurrency / load tests using commons-performance to > make sure we have not broken anything. Finally, I have some > documentation improvements that I want to make for this release - mostly > taking the vagueness out of the descriptions of maxActive, maxIdle, etc. All sounds good to me. I've fixed the new issues sebb raised as best I can. They really have highlighted that sync needs a complete rethink for 2.0. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
