On Sat, Jan 8, 2022, at 05:11, Julius Davies wrote:
> One person's EOL is another person's open source business model ! (RHEL
> subscriptions are not cheap!)
I doubt anybody would actually pay for log4j.
>
> Anyway, quick FYI - I noticed Atlassian has rev'd log4j-1.2.17 fifteen
> times !
One person's EOL is another person's open source business model ! (RHEL
subscriptions are not cheap!)
Anyway, quick FYI - I noticed Atlassian has rev'd log4j-1.2.17 fifteen
times ! Might be some good patches in there. They do publish the
"sources.jar":
https://packages.atlassian.com/3rdparty
End-Of-Life means End-Of-Life and that is the end of the story.
If someone keeps patching an End-Of-Life component, how should downstream
understand when they should update their product?
The answer to this question is the technical definition of End-Of-Life.
Upgrade, migrate, rewrite, throw awa
https://github.com/albfernandez/log4j/ is one fork I found that
published a fixed copy on Maven Central. Confluent also publishes a
forked copy, though I don't know where their source code is (package
names are renamed as it's mainly used by old versions of Confluent's
hosted services, so it's poss
my comment is below:
On Fri, 7 Jan 2022 at 14:23, Christian Grobmeier
wrote:
> Hello,
>
> On Fri, Jan 7, 2022, at 08:21, Ceki Gülcü wrote:
> > As for infringing on the log4j trademark, I will rename the repo to
> > something else, for example "re4j".
> >
> > As mentioned in my previous message,
Hello,
On Fri, Jan 7, 2022, at 08:21, Ceki Gülcü wrote:
> As for infringing on the log4j trademark, I will rename the repo to
> something else, for example "re4j".
>
> As mentioned in my previous message, if the ASF decides to integrate
> "re4j" as log4j 1.x, the door is open.
Thanks. You did n
On 07/01/2022 01:53, Matt Sicker wrote:
> If you had left a comment back when we voted on the EOL status
> recently, then perhaps things would be different. Waiting until
> right after the second EOL announcement makes us seem like we
> just lied about said EOL status.
On 07/01/2022 02:46, Ma
I should also note that naming a fork “relog4j” is confusingly similar to
“log4j”. Please don’t infringe the trademark.
--
Matt Sicker
> On Jan 6, 2022, at 18:18, Ceki Gülcü wrote:
>
>
>
> Hello all,
>
> Given the recent refusal to even consider work on a 1.2.18 branch, which
> would have b
If you had left a comment back when we voted on the EOL status recently, then
perhaps things would be different. Waiting until right after the second EOL
announcement makes us seem like we just lied about said EOL status.
—
Matt Sicker
> On Jan 6, 2022, at 18:18, Ceki Gülcü wrote:
>
>
>
>
Hello all,
Given the recent refusal to even consider work on a 1.2.18 branch, which
would have been subject to PMC vote before release anyway, I have
created a separate repository on github under the name "relog4j1". The
intent of relog4j1 is to fix existing critical issues in log4j 1.x.
On 07/01/2022 00:05, Ralph Goers wrote:
Unless you can convince Gary to rescind his veto there is no choice but to
revert.
Reverted in github.
--
Ceki Gülcü
Maybe I'm missing something, but shouldn't it be 1.2.18? There was already
a log4j release 1.2.8 in 2005.
On Thu, Jan 6, 2022 at 2:54 PM Matt Sicker wrote:
> Plus, the branch name sounds like a tag.
>
> On Thu, Jan 6, 2022 at 3:21 PM Gary Gregory
> wrote:
> >
> > -1 This component reached End-o
v1.2.8? Odd choice to work on 1.2.18.
However, with Gary expressing a -1 (a veto) by ASF rules the problem specified
(12 being EOL) would either need to be resolved or the commit reverted.
Unless you can convince Gary to rescind his veto there is no choice but to
revert.
Ralph
> On Jan 6, 2
Plus, the branch name sounds like a tag.
On Thu, Jan 6, 2022 at 3:21 PM Gary Gregory wrote:
>
> -1 This component reached End-of-Life in 2015.
>
> Gary
>
> On Thu, Jan 6, 2022 at 12:46 PM wrote:
>
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > ceki pushed a chang
-1 This component reached End-of-Life in 2015.
Gary
On Thu, Jan 6, 2022 at 12:46 PM wrote:
> This is an automated email from the ASF dual-hosted git repository.
>
> ceki pushed a change to branch v1.2.8
> in repository https://gitbox.apache.org/repos/asf/logging-log4j1.git.
>
>
> at 0cde9
15 matches
Mail list logo
