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
;
> 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, February 14, 2024
Sicker
> XA> Sent: Wednesday, February 14, 2024 1:22:48 AM
> XA> To: Apache Logging Developers List
> XA> Subject: Re: Migrate *all* Issue Tracking and Discussions to GitHub
>
> XA> I think it’s a good idea, especially since Jira registrations are
> closed.
>
> &
+1 from me
Jan
XA> +1.
XA>
XA> From: Matt Sicker
XA> Sent: Wednesday, February 14, 2024 1:22:48 AM
XA> To: Apache Logging Developers List
XA> Subject: Re: Migrate *all* Issue Tracking and Discussions to GitHub
XA> I think it’s a good i
+1.
From: Matt Sicker
Sent: Wednesday, February 14, 2024 1:22:48 AM
To: Apache Logging Developers List
Subject: Re: Migrate *all* Issue Tracking and Discussions to GitHub
I think it’s a good idea, especially since Jira registrations are closed.
> On Feb
I think it’s a good idea, especially since Jira registrations are closed.
> On Feb 13, 2024, at 02:20, Volkan Yazıcı wrote:
>
> Log4j has deprecated JIRA in favor of GitHub Issues and enabled GitHub
> Discussions as an alternative (not replacement!) to mailing lists. So far
> it has been a great
Log4j has deprecated JIRA in favor of GitHub Issues and enabled GitHub
Discussions as an alternative (not replacement!) to mailing lists. So far
it has been a great success[1]. I suggest doing the same for Log4cxx and
Log4net too. Thoughts? Objections?
Note that I am not talking about only enablin
