[VOTE] Release [pool] 2.1 based on RC2

2013-12-26 Thread Phil Steitz
I have updated the release notes and MBean interface class javadoc to address feedback from RC1. Pool 2.1 RC2 is available for review here: https://dist.apache.org/repos/dist/dev/commons/pool/ Maven artifacts are here: https://repository.apache.org/content/repositories/orgapachecommons-022/

Re: svn commit: r1553569 - in /commons/proper/pool/trunk/src: changes/ main/java/org/apache/commons/pool2/impl/

2013-12-26 Thread Phil Steitz
On 12/26/13, 3:37 PM, Mark Thomas wrote: > On 26/12/2013 20:03, pste...@apache.org wrote: >> Author: psteitz >> Date: Thu Dec 26 20:03:11 2013 >> New Revision: 1553569 >> >> URL: http://svn.apache.org/r1553569 >> Log: >> Added change warnings on MBean interfaces; clarified compat statements. > > >

Re: svn commit: r1553569 - in /commons/proper/pool/trunk/src: changes/ main/java/org/apache/commons/pool2/impl/

2013-12-26 Thread Mark Thomas
On 26/12/2013 20:03, pste...@apache.org wrote: > Author: psteitz > Date: Thu Dec 26 20:03:11 2013 > New Revision: 1553569 > > URL: http://svn.apache.org/r1553569 > Log: > Added change warnings on MBean interfaces; clarified compat statements. > Modified: > commons/proper/pool/trunk/src/main/ja

Re: [OGNL] A new release

2013-12-26 Thread Henri Yandell
JIRA issue reopened btw as I noticed it was still resolved. On Wed, Dec 25, 2013 at 11:10 AM, Jason Pyeron wrote: > > -Original Message- > > From: Benedikt Ritter > > Sent: Wednesday, December 25, 2013 11:53 > > > > You've set the issue to status resolved. That's propably the > > After

Re: [CANCELLED][VOTE] Release [pool] 2.1 based on RC1

2013-12-26 Thread Phil Steitz
On 12/26/13, 1:31 AM, Mark Thomas wrote: > On 24/12/2013 20:37, Phil Steitz wrote: >> The clirr breakage needs to dealt with / explained in the release >> notes. As it stands, the statements about compatibility are not >> correct. > I would argue that there is nothing incorrect about those stateme

Re: [CANCELLED][VOTE] Release [pool] 2.1 based on RC1

2013-12-26 Thread Mark Thomas
On 24/12/2013 20:37, Phil Steitz wrote: > The clirr breakage needs to dealt with / explained in the release > notes. As it stands, the statements about compatibility are not > correct. I would argue that there is nothing incorrect about those statements. No client of Pool should be using any (.*)