Move Chainsaw to dormant: Q

Do dormant projects clearly indicate they can be re-animated by a sufficient number of active committers? Thanks, Tim

Re: [VOTE] Move Chainsaw to dormant

+1 Gary On Mon, Feb 12, 2024 at 4:32 PM Christian Grobmeier wrote: > > 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

Re: [VOTE] Move Chainsaw to dormant

+1 Piotr On Mon, 12 Feb 2024 at 22:32, Christian Grobmeier wrote: > > 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

Re: [VOTE] Move Chainsaw to dormant

+1 Ralph > On Feb 12, 2024, at 2:31 PM, Christian Grobmeier wrote: > > 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

Re: [VOTE] Move Chainsaw to dormant

+1 Thanks Christian Scott On 2/12/24, Christian Grobmeier wrote: > 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

[VOTE] Move Chainsaw to dormant

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

Re: [log4j] Remove `` in `main`

Hi Volkan, On Mon, 12 Feb 2024 at 20:30, Volkan Yazıcı wrote: > `StatusLogger` can be configured in following ways: > >1. Passing system properties to the Java process (e.g., >`-Dlog4j2.StatusLogger.level=INFO`) >2. Providing properties in a `log4j2.StatusLogger.properties` file in >

[log4j] Remove `` in `main`

*Abstract:* I want to remove from `main` the feature that a `Configuration` (e.g., `` in a `log4j2.xml`) configuring the `StatusLogger`, and instead, only allow configuration using properties. `StatusLogger` can be configured in following ways: 1. Passing system properties to the Java process

Re: Version 2.23.0 release schedule

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

I'll continue later today to try and fix the set Level issue... Gary On Mon, Feb 12, 2024, 6:15 AM Piotr P. Karwasz wrote: > Hi all, > > This week I was planning to perform a 2.23.0 release. According to > Github most of the issues scheduled for this milestone are resolved: > >

Re: Version 2.23.0 release schedule

+1 Once #2280 (fixing the `2.x` build) and #2278 (Allow arbitrary position of `` element) are in, we can put a ribbon around `2.23.0`. On Mon, Feb 12, 2024 at 12:15 PM Piotr P. Karwasz

Version 2.23.0 release schedule

Hi all, This week I was planning to perform a 2.23.0 release. According to Github most of the issues scheduled for this milestone are resolved: https://github.com/apache/logging-log4j2/milestone/9 Are there any other issues I should be waiting for? Piotr