I agree with your remark on priority. Using Log4j 2 API in Log4j 3 is
indeed our focus. My recent refactoring of `StatusLogger` was a part of
that effort. Since I already have my hands dirty with it, I want to take
one last step to polish it in `main` and remove the `StatusConfiguration`
wrinkle.
Hi Ralph,
On Wed, 14 Feb 2024 at 04:35, Ralph Goers wrote:
> To be honest, this isn’t a top priority on the list of things that need to be
> addressed for me which is partly why I guess I am hesitant to do anything. It
> feels like we keep talk about making changes but aren’t really focused on
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
I have no strong feelings either way. Turning on github discussions is a
good idea in my mind.
+0
-Robert Middleton
On Tue, Feb 13, 2024 at 12:45 PM Jan Friedrich
wrote:
> +1 from me
>
> Jan
>
> XA> +1.
> XA>
> XA> From: Matt Sicker
> XA> Sent: Wednesday, Feb
Keep in mind that decisions for the project still must be recorded on the
mailing list. This might be a silly reminder since the issue is the same
with Jira. Let's just be mindful of this information tracking as we've
moved more of our infrastructure to GitHub. Don't get me wrong, I love
working wi
As per consensus, enabled GitHub Discussions for both Log4Net and Log4cxx –
GitHub Issues were already enabled. I will submit a PR to both projects
updating their docs to reflect these changes.
On Tue, Feb 13, 2024 at 9:20 AM Volkan Yazıcı wrote:
> Log4j has deprecated JIRA in favor of GitHub Is
+1
Thanks!
-ck
On Mon, Feb 12, 2024, at 16:31, Christian Grobmeier wrote:
> 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 t
