Re: [lang] Ready for 3.9???

2019-02-03 Thread Pascal Schumacher
No sure if it worth it, as there are very few new features and no bugfixes, see: https://github.com/apache/commons-lang/blob/master/src/changes/changes.xml Also the function class addition: https://github.com/apache/commons-lang/commit/11d9eb47a40359e74a5e24daf681beacd71b35f0 https://githu

Re: [lang] Ready for 3.9???

2019-02-03 Thread Rob Tompkins
Ok. I’ll hold off. -Rob > On Feb 3, 2019, at 8:16 AM, Pascal Schumacher > wrote: > > No sure if it worth it, as there are very few new features and no bugfixes, > see: > > https://github.com/apache/commons-lang/blob/master/src/changes/changes.xml > > Also the function class addition: > >

Re: [lang] Ready for 3.9???

2019-02-03 Thread Gary Gregory
If the target is Java 8, it feels safe to build on Java 8. Testing on Java 11 is a must these days IMO. Gary On Sat, Feb 2, 2019 at 3:49 PM Rob Tompkins wrote: > Just curious if we want to send 3.9 out? Build on java 11 targeting java 8? > > -Rob > >

Re: [VOTE] Release Apache Commons VFS 2.3 based on RC2

2019-02-03 Thread Gary Gregory
My +1. We need more binding VOTEs please. Thank you, Gary On Fri, Feb 1, 2019 at 12:36 PM Gary Gregory wrote: > We have fixed quite a few bugs and added some significant enhancements > since Apache Commons VFS Distribution 2.2 was released, so I would like to > release Apache Commons VFS Distrib

Re: [VOTE] Release Apache Commons VFS 2.3 based on RC2

2019-02-03 Thread Rob Tompkins
Gotcha. Busy day...got a small brake now to hop in here to do a validation. -Rob > On Feb 3, 2019, at 3:47 PM, Gary Gregory wrote: > > My +1. We need more binding VOTEs please. > Thank you, > Gary > >> On Fri, Feb 1, 2019 at 12:36 PM Gary Gregory wrote: >> >> We have fixed quite a few bugs

[GitHub] asfgit closed pull request #19: reformat code & fixed some typo

2019-02-03 Thread GitBox
asfgit closed pull request #19: reformat code & fixed some typo URL: https://github.com/apache/commons-pool/pull/19 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and