Unless someone objects I plan to start the release process for Log4j 2.10
>> tomorrow. I had wanted to include a fix for LOG4J2-2106 but the problem only
>> occurs in rare situations and I am not sure how to fix it yet. There are a
>> lot of other issues that deserve looking
OK for me. Thanks for the RM work.
On 2017-11-16 05:31, Ralph Goers wrote:
Unless someone objects I plan to start the release process for Log4j 2.10
tomorrow. I had wanted to include a fix for LOG4J2-2106 but the problem only
occurs in rare situations and I am not sure how to fix it yet
OK for me. Thanks for the RM work.
On 2017-11-16 05:31, Ralph Goers wrote:
Unless someone objects I plan to start the release process for Log4j 2.10
tomorrow. I had wanted to include a fix for LOG4J2-2106 but the problem only
occurs in rare situations and I am not sure how to fix it yet
> Great! And thank you for RM'ing again.
> >
> > Gary
> >
> > On Wed, Nov 15, 2017 at 9:31 PM, Ralph Goers >
> > wrote:
> >
> >> Unless someone objects I plan to start the release process for Log4j
> 2.10
> >> tomorrow. I had wanted t
No objection, and thanks for RM-ing!
Remko
> On Nov 16, 2017, at 14:04, Gary Gregory wrote:
>
> Great! And thank you for RM'ing again.
>
> Gary
>
> On Wed, Nov 15, 2017 at 9:31 PM, Ralph Goers
> wrote:
>
>> Unless someone objects I plan to st
Great! And thank you for RM'ing again.
Gary
On Wed, Nov 15, 2017 at 9:31 PM, Ralph Goers
wrote:
> Unless someone objects I plan to start the release process for Log4j 2.10
> tomorrow. I had wanted to include a fix for LOG4J2-2106 but the problem
> only occurs in rare situation
Unless someone objects I plan to start the release process for Log4j 2.10
tomorrow. I had wanted to include a fix for LOG4J2-2106 but the problem only
occurs in rare situations and I am not sure how to fix it yet. There are a lot
of other issues that deserve looking at but nothing I can see
