Re: [pool] POOL-376 and release?

2019-10-01 Thread Gary Gregory
On Tue, Oct 1, 2019 at 5:03 PM Phil Steitz wrote: > Good news. I think I now understand the actual root cause for > POOL-376. Bad news is the fix that I committed masks but does not > really fix the problem. I will update the ticket and commit a full fix > this evening. I will try to get a te

Re: [pool] POOL-376 and release?

2019-10-01 Thread Phil Steitz
Good news.  I think I now understand the actual root cause for POOL-376.  Bad news is the fix that I committed masks but does not really fix the problem.  I will update the ticket and commit a full fix this evening.  I will try to get a test case but that is going to be tricky because it requir

Re: [VOTE] Release Apache Commons BCEL 6.4.1 based on RC1

2019-10-01 Thread Gary Gregory
Ping :-) On Mon, Sep 30, 2019, 08:59 Gary Gregory wrote: > May we get more PMC reviews please? > > Gary > > On Thu, Sep 26, 2019 at 9:38 PM Gary Gregory wrote: > >> We have fixed one important bug since Apache Commons BCEL 6.4.0 was >> released, so I would like to release Apache Commons BCEL 6.

Re: [VOTE] Release Apache Commons Daemon 1.2.2 RC2

2019-10-01 Thread Gary Gregory
On Tue, Oct 1, 2019 at 3:43 AM Mark Thomas wrote: > On 30/09/2019 21:09, Gary Gregory wrote: > > Hi Mark, > > > > I know you said you fixed a bunch of warnings but I still warning get > these > > using CPU=X64; I had only tested CPU=X86 previously (sorry): > > No problem. I think you hit upon I c

ApacheCon North America 2020, project participation

2019-10-01 Thread Rich Bowen
Hi, folks, (Note: You're receiving this email because you're on the dev@ list for one or more Apache Software Foundation projects.) For ApacheCon North America 2019, we asked projects to participate in the creation of project/topic specific tracks. This was very successful, with about 15 projects

Re: [VOTE] Release Apache Commons Daemon 1.2.2 RC2

2019-10-01 Thread Mark Thomas
On 30/09/2019 21:09, Gary Gregory wrote: > Hi Mark, > > I know you said you fixed a bunch of warnings but I still warning get these > using CPU=X64; I had only tested CPU=X86 previously (sorry): No problem. I think you hit upon I configuration I've never tested. > C:\Program Files (x86)\Windows