Re: [dbcp] [pool] Roadmap ideas

2007-06-22 Thread Phil Steitz
On 6/21/07, Henri Yandell [EMAIL PROTECTED] wrote: On 6/20/07, Phil Steitz [EMAIL PROTECTED] wrote: Next releases: [dbcp] - 1.3 close as many of the 1.3-marked bugs as possible without the new pool impl and add instrumentation using JDK logging, therefore increasing required JDK level to

Re: [dbcp] [pool] Roadmap ideas

2007-06-21 Thread Henri Yandell
On 6/20/07, Phil Steitz [EMAIL PROTECTED] wrote: Next releases: [dbcp] - 1.3 close as many of the 1.3-marked bugs as possible without the new pool impl and add instrumentation using JDK logging, therefore increasing required JDK level to 1.4. +1. Instrumentation is strongly needed.

[dbcp] [pool] Roadmap ideas

2007-06-20 Thread Phil Steitz
There are still quite a few bugs open against [dbcp] and [pool]. We also have an unreleased, improved pool impl in the compositepool package. I would like to toss out some ideas for discussion about where to go with these two components and guage interest in helping out. Recent releases:

Re: [pool] roadmap 1.3, 2.0, 3.0

2006-02-18 Thread robert burrell donkin
On Tue, 2006-02-14 at 21:47 -0500, Sandy McArthur wrote: A lot of this was brought up in Nov 2005 starting with Robert's post: http://tinyurl.com/aq7cx feel free to add this road map to the wiki ;) Now that all known issues for the existing Pool code have been fixed I'd like to see one more

[pool] roadmap 1.3, 2.0, 3.0

2006-02-14 Thread Sandy McArthur
A lot of this was brought up in Nov 2005 starting with Robert's post: http://tinyurl.com/aq7cx Now that all known issues for the existing Pool code have been fixed I'd like to see one more release of the current code base, probably dubbed 'Pool 1.3'. I also think this should be announced as the

Re: [pool] roadmap

2005-11-21 Thread robert burrell donkin
On Mon, 2005-11-14 at 19:42 -0500, Sandy McArthur wrote: On 11/14/05, robert burrell donkin [EMAIL PROTECTED] wrote: On Fri, 2005-11-11 at 02:32 -0500, Sandy McArthur wrote: * The javadacs for [Keyed]ObjectPool.borrowObject should list NoSuchElementException as one of the thrown

Re: [pool] roadmap

2005-11-14 Thread robert burrell donkin
On Fri, 2005-11-11 at 00:25 +, Stephen Colebourne wrote: robert burrell donkin wrote: (unless anyone else with karma wants to jump in here as a volunteer) i'm willing to act as release manager for this release. however, i would need help with this release so i need to gauge the level of

Re: [pool] roadmap

2005-11-14 Thread robert burrell donkin
On Fri, 2005-11-11 at 02:32 -0500, Sandy McArthur wrote: On 11/10/05, robert burrell donkin [EMAIL PROTECTED] wrote: thanks to sandy's hard work, looks like pool's starting to gain some momentum. this seems like a good time to start a thread about the future. Here is my Pool wish list.

Re: [pool] roadmap

2005-11-14 Thread Sandy McArthur
On 11/14/05, robert burrell donkin [EMAIL PROTECTED] wrote: On Fri, 2005-11-11 at 02:32 -0500, Sandy McArthur wrote: * The javadacs for [Keyed]ObjectPool.borrowObject should list NoSuchElementException as one of the thrown exceptions. Techically a NSEE is included with throws Exception but

[pool] roadmap

2005-11-10 Thread robert burrell donkin
thanks to sandy's hard work, looks like pool's starting to gain some momentum. this seems like a good time to start a thread about the future. trunk is now versioned 2.0-dev and this seems appropriate since it seems that the next release of this code will contain quite a few changes. however,

Re: [pool] roadmap

2005-11-10 Thread Stephen Colebourne
robert burrell donkin wrote: (unless anyone else with karma wants to jump in here as a volunteer) i'm willing to act as release manager for this release. however, i would need help with this release so i need to gauge the level of support amongst the wider development community. any

Re: [pool] roadmap

2005-11-10 Thread Sandy McArthur
On 11/10/05, robert burrell donkin [EMAIL PROTECTED] wrote: thanks to sandy's hard work, looks like pool's starting to gain some momentum. this seems like a good time to start a thread about the future. Here is my Pool wish list. Since these could change the behavior of existing code (but not