On 12/21/11 11:09 AM, Gary Gregory wrote: > On Wed, Dec 21, 2011 at 1:03 PM, Mark Thomas <ma...@apache.org> wrote: > >> On 21/12/2011 16:57, Phil Steitz wrote: >>> On 12/21/11 9:41 AM, Christian Grobmeier wrote: >>>> On Wed, Dec 21, 2011 at 5:19 PM, Phil Steitz <phil.ste...@gmail.com> >> wrote: >>>>> 1.5.x ships with tomcat and is used by lots of other production >>>>> applications. We need to maintain the ability to patch it. >>>> Tomcat 5.5 (the oldest stable version i can find) uses Java 5: >>>> http://tomcat.apache.org/tomcat-5.5-doc/setup.html >>>> >>>> This proposed release is binary compatible - they should not have any >>>> issue to upgrade, right? >>>> How long would you like to maintain the elder 1.5.x code without java 5 >> support? >>> At least until 2.0 is out and for some time after that. Asking >>> tomcat and others to upgrade twice makes no sense. I will let Mark >>> or other tc committers comment on that. >> Tomcat will continue to use 1.5.x since that is what DBCP uses. When >> 2.0.x is ready, trunk will switch to 2.0.x and the associated DBCP >> release. Depending on the results, the release branches (5.5.x, 6.0.x >> and 7.0.x) may follow. >> >> Tomcat is highly unlikely to use Pool 1.6.x >> > Which is quite fine with me. > > My goal is only to provide a version of pool-1 with generics that is as > least disruptive as possible.
That is great for your own use, but what releasing it does is sets us up to support 3 versions. We are having a hard enough time just supporting one. When we release 2.0, we will have two release branches to maintain. The 1.5.x code itself is fairly stable, but 1.5 was pretty much a complete rewrite of the core code and I expect we will continue to get bug reports against this code. Maintaining two versions of it does not sound fun to me and I really think it is unwise to set ourselves up to try to do it. Phil > > Gary > > >> Mark >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
