Hi all,
Since we switched to Github Issues, I rarely look at JIRA any more and
certainly I do not expect to see new issues being posted there.
Should we ask INFRA to disable issue creation on JIRA for LOG4J2? Do
we need a vote for that?
Piotr
We should NOT be creating new Jira issues. But locking down Jira completely
would mean we would have to somehow transfer any active issues to GitHub. When
that happens I would expect the Jira issue to link to the GitHub issue and vice
versa as I would not expect all the Jira content and history
Hi Ralph,
On Fri, 24 Nov 2023 at 16:50, Ralph Goers wrote:
>
> We should NOT be creating new Jira issues. But locking down Jira completely
> would mean we would have to somehow transfer any active issues to GitHub.
> When that happens I would expect the Jira issue to link to the GitHub issue
>
I’d like it if we could copy over open issues to GH.
—
Matt Sicker
> On Nov 24, 2023, at 07:12, Piotr P. Karwasz wrote:
>
> Hi all,
>
> Since we switched to Github Issues, I rarely look at JIRA any more and
> certainly I do not expect to see new issues being posted there.
>
> Should we ask INF
I’ll note that MessageSupplier is deprecated, and we eventually added support
for Supplier, so that’s already there. Since it sounds like we have
some good ideas on what a minimal v3.Logger API would look like, it would be
cool if anyone would like to propose a full API. Here’s another Logger AP
