+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 13,
+1 for to guthub issues.
well if people still care about jira we can try make a jira plugin to auto
create jira issue for every pr.
But I really doubt if there be many people really love jira that much...
From: Gary Gregory
Sent: Sunday, November 6, 2022 1:59:20
I mean, even though some guy make it fails locally, CI shall stop manager for
merging that pr, shouldn't it？
XenoAmess
From: Xeno Amess
Sent: Monday, May 2, 2022 9:23:11 PM
To: dev@logging.apache.org
Subject: Re: Please verify your stuff.
I don't understand
I don't understand.
What is CI doing？
XenoAmess
From: Ralph Goers
Sent: Monday, May 2, 2022 8:58:50 PM
To: dev@logging.apache.org
Subject: Please verify your stuff.
Remko,
Did you run a full build of master when you committed your latest changes? I
don’t see
I see the icons.
They are travis ci badges...
Should be removed when we abandon travis ci
XenoAmess
From: Xeno Amess
Sent: Tuesday, January 18, 2022 9:13:50 PM
To: dev@logging.apache.org
Subject: Re: CI red
at which repo？
XenoAmess
at which repo？
XenoAmess
From: Gary Gregory
Sent: Tuesday, January 18, 2022 8:41:51 PM
To: Apache Logging Developers List
Subject: CI red
We have red CI builds all the time. Why? I don't really care but I see that
the GitHub portions of the builds are green all
and it uses eclipse formatter to file, so I do think you can export
Eclipse config file
Xeno Amess 于2022年1月13日周四 17:54写道：
> try this:
>
> net.revelc.code.formatter:formatter-maven-plugin:2.17.1
>
> It worked well in my team for 2 years, never cause any trouble.
>
> Gary G
try this:
net.revelc.code.formatter:formatter-maven-plugin:2.17.1
It worked well in my team for 2 years, never cause any trouble.
Gary Gregory 于2022年1月13日周四 17:36写道：
> I am ok with formatting code but I want to do it in Eclipse. I did not even
> notice the POM was changed. I would think it
procedure...
Xeno Amess 于2022年1月3日周一 23:39写道：
> +0
>
> I just worried several things.
>
> 1. Will it make the cve's fix come out more slowly?
> A vote means waiting for 72 hours usually.
>
> 2. Do all PMC who enter the vote always have enough ability and knowledge
&g
+0
I just worried several things.
1. Will it make the cve's fix come out more slowly?
A vote means waiting for 72 hours usually.
2. Do all PMC who enter the vote always have enough ability and knowledge
for notifying how severe a vulnerability? Some vulnerabilities are, seems
small problem,
+0
> People should migrate to log4j2.
good thinking, but what if they migrate to logback...
IMO logback is a thing more likely log4j1 than log4j2, just user side.
Ralph Goers 于2022年1月1日周六 23:18写道：
> +1 to Option 1
>
> Ralph
>
> > On Dec 29, 2021, at 12:33 PM, Christian Grobmeier
> wrote:
>
sigh..
so 2.17.1 IS a security fix now？
XenoAmess
From: Matt Sicker
Sent: Wednesday, December 29, 2021 4:07:48 AM
To: dev@logging.apache.org
Subject: Re: CVE-2021-44832: Apache Log4j2 vulnerable to RCE via JDBC Appender
when attacker controls configuration
Yes...
Benchmark is only meaningful when on same machine, and totally same
situation.
Benchmark on the cloud seems weird and pointless...
Besides, they are time-costing, thus will make our ci worse.
Dominik Psenner 于2021年12月28日周二 17:17写道：
> Hi Stephen,
>
> The trouble with benchmarks in CI is
Hi
Is this version about safety or functionality？
XenoAmess
From: Matt Sicker
Sent: Tuesday, December 28, 2021 8:31:14 AM
To: dev@logging.apache.org
Subject: [VOTE] Release Apache Log4j 2.17.1-rc1
This is a vote to release Log4j 2.17.1, the next version of the
Do read only mean we cannot give pull request？
Then how can I help you clean the pom correct...
XenoAmess
From: Ralph Goers
Sent: Thursday, December 23, 2021 2:34:02 PM
To: dev@logging.apache.org
Subject: New Log4j 1 repo
I have cloned the read-only log4j repo
15 matches
Mail list logo
