[RESULT][VOTE] Move Chainsaw to dormant

2024-02-16 Thread Christian Grobmeier
The vote succeeded with 7 +1.
Thanks to everybody who voted.
I will do the necessary steps early next week.

Kind regards
Christian

--
The Apache Software Foundation
V.P., Data Privacy

- Original message -
From: Christian Grobmeier 
To: dev@logging.apache.org
Subject: [VOTE] Move Chainsaw to dormant
Date: Monday, February 12, 2024 22:31

Hello,

This vote is to put Chainsaw to the "Dormant" components. There is much work to 
be done on this component, but not enough hours can be committed to do that 
work. To reflect this situation to the user, it is better to move Chainsaw to 
the dormant section and communicate it as "no longer maintained."  The 
component can be moved back to the "active" state whenever people are actively 
working on it. The main branch in the repository will be marked with the new 
state, but the repository will not be archived for now.

Please note:

[ ] +1, move to dormant
[ ]  -1, don't because...

I will leave this vote open for the usual 72 hours.

Thank you!

Kind regards,
Christian


Re: Version 2.23.0 release schedule

2024-02-16 Thread Gary Gregory
Hi Piotr,

Are you planning for a RC?

Gary

On Wed, Feb 14, 2024 at 8:12 AM Gary Gregory  wrote:
>
> FYI, the 1.2 bridge is fixed now. Not sure if the bug is present or not for 
> JUL.
>
> Gary
>
> On Mon, Feb 12, 2024, 8:07 AM Piotr P. Karwasz  
> wrote:
>>
>> Hi Gary,
>>
>> On Mon, 12 Feb 2024 at 13:22, Gary Gregory  wrote:
>> >
>> > I'll continue later today to try and fix the set Level issue...
>>
>> Great! I have created a bug for that:
>>
>> https://github.com/apache/logging-log4j2/issues/2281
>>
>> Piotr


Re: Version 2.23.0 release schedule

2024-02-16 Thread Piotr P. Karwasz
Hi Gary,

On Sat, 17 Feb 2024 at 03:12, Gary Gregory  wrote:
>
> Hi Piotr,
>
> Are you planning for a RC?

Yes, I'll prepare a release this weekend.

Piotr