You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Ramanathan Muthu <ra...@gmail.com> on 2026/06/24 08:12:58 UTC
[ANNOUNCE] Release Apache Log4j 2.26.1
This is a discussion regarding the release of patch version
I propose cutting an Apache Log4j *2.26.1* patch release.
*Volkan (vy) *will assist me wherever PMC privileges are needed.
The milestone for this release is here:
Milestone #27 <https://github.com/apache/logging-log4j2/milestone/27>
The planned fixes for this release are:
- Fix "Identity Malfunction" in ThrowableStackTraceRenderer by
using IdentityHashMap for metadata caching. This prevents
ArrayIndexOutOfBoundsException and NullPointerException
when encountering exceptions with custom equals() or
unstable hashCode() implementations. (Issue #3933
<https://github.com/apache/logging-log4j2/issues/3933>, PR #4143
<https://github.com/apache/logging-log4j2/pull/4143>, PR #4133
<https://github.com/apache/logging-log4j2/pull/4133>).
- Fix resource leaks in ConfigurationSource when loading
configurations via URL. (PR #4127
<https://github.com/apache/logging-log4j2/pull/4127>)
- Fix DatePatternConverter locale parsing when the timezone
is omitted. (Issue #4129
<https://github.com/apache/logging-log4j2/issues/4129>, PR #4130
<https://github.com/apache/logging-log4j2/pull/4130>)
- Improve logging for LinkageError and Disruptor
initialization failures to provide better diagnostics.
(Issue #2250 <https://github.com/apache/logging-log4j2/issues/2250>, PR
#4124 <https://github.com/apache/logging-log4j2/pull/4124>, PR #4134
<https://github.com/apache/logging-log4j2/pull/4134>)
- Fix RollingFileAppender with createOnDemand="true" to
prevent the eager creation of parent directories when no
logs are being written. (Issue #2006
<https://github.com/apache/logging-log4j2/issues/2006>, PR #4072
<https://github.com/apache/logging-log4j2/pull/4072>)
- Fix KafkaAppender retry logic to prevent reporting spurious
errors to the error handler after a successful retry. (Issue #4125
<https://github.com/apache/logging-log4j2/pull/4125>)
- Fix encoding of MSGID and SD-ID fields of
StructuredDataMessage to XML. (PR #4136
<https://github.com/apache/logging-log4j2/pull/4136>)
Please let me know if there are any
additional changes or concerns before
we proceed.
Re: [ANNOUNCE] Release Apache Log4j 2.26.1
Posted by "Piotr P. Karwasz" <pi...@mailing.copernik.eu>.
Hi Gary,
On 24.06.2026 21:25, Gary Gregory wrote:
> I thought we had made a release and I missed the vote!
I thought the same.
Piotr
Re: [ANNOUNCE] Release Apache Log4j 2.26.1
Posted by Ramanathan Muthu <ra...@gmail.com>.
Yes.. next time i will correct it
On Thu, Jun 25, 2026 at 12:57 AM Gary Gregory <ga...@gmail.com>
wrote:
> Side note: the subject of this email is very misleading, it's the exact
> same we send when a release is actually made. We are not announcing
> anything here.
>
> If you want to say you are planning to create a release candidate, then
> just say that.
>
> I thought we had made a release and I missed the vote!
>
> Gary
>
> On Wed, Jun 24, 2026, 15:19 Piotr P. Karwasz <pi...@mailing.copernik.eu>
> wrote:
>
> > Hi Volkan,
> >
> > On 24.06.2026 13:36, Volkan Yazıcı wrote:
> > > #4146 has API changes, it cannot go to a patch release. If you
> disagree,
> > > please explain.
> >
> >
> > Oh, the PR is much bigger than I remembered. Just fixing `onMatch` and
> > `onMismatch` from what I remembered doesn't need a lot changes. I can
> > look into that.
> >
> > > Ramanathan, you can create the `2.26.x` branch from the `rel/2.26.0`
> tag,
> > > and copy `.github/dependabot.yaml` changes from the `2.25.x` branch,
> > > assuming Piotr already updated that to perform PATCH-level upgrades as
> he
> > > suggested.
> >
> >
> > I haven't done any changes to the Dependabot configuration, but I can
> > make a PR.
> >
> > Piotr
> >
>
Re: [ANNOUNCE] Release Apache Log4j 2.26.1
Posted by Gary Gregory <ga...@gmail.com>.
Side note: the subject of this email is very misleading, it's the exact
same we send when a release is actually made. We are not announcing
anything here.
If you want to say you are planning to create a release candidate, then
just say that.
I thought we had made a release and I missed the vote!
Gary
On Wed, Jun 24, 2026, 15:19 Piotr P. Karwasz <pi...@mailing.copernik.eu>
wrote:
> Hi Volkan,
>
> On 24.06.2026 13:36, Volkan Yazıcı wrote:
> > #4146 has API changes, it cannot go to a patch release. If you disagree,
> > please explain.
>
>
> Oh, the PR is much bigger than I remembered. Just fixing `onMatch` and
> `onMismatch` from what I remembered doesn't need a lot changes. I can
> look into that.
>
> > Ramanathan, you can create the `2.26.x` branch from the `rel/2.26.0` tag,
> > and copy `.github/dependabot.yaml` changes from the `2.25.x` branch,
> > assuming Piotr already updated that to perform PATCH-level upgrades as he
> > suggested.
>
>
> I haven't done any changes to the Dependabot configuration, but I can
> make a PR.
>
> Piotr
>
Re: [ANNOUNCE] Release Apache Log4j 2.26.1
Posted by "Piotr P. Karwasz" <pi...@mailing.copernik.eu>.
Hi Volkan,
On 24.06.2026 13:36, Volkan Yazıcı wrote:
> #4146 has API changes, it cannot go to a patch release. If you disagree,
> please explain.
Oh, the PR is much bigger than I remembered. Just fixing `onMatch` and
`onMismatch` from what I remembered doesn't need a lot changes. I can
look into that.
> Ramanathan, you can create the `2.26.x` branch from the `rel/2.26.0` tag,
> and copy `.github/dependabot.yaml` changes from the `2.25.x` branch,
> assuming Piotr already updated that to perform PATCH-level upgrades as he
> suggested.
I haven't done any changes to the Dependabot configuration, but I can
make a PR.
Piotr
Re: [ANNOUNCE] Release Apache Log4j 2.26.1
Posted by Ramanathan Muthu <ra...@gmail.com>.
ok, i will start the process
On Wed, Jun 24, 2026 at 5:07 PM Volkan Yazıcı <vo...@yazi.ci> wrote:
> #4146 has API changes, it cannot go to a patch release. If you disagree,
> please explain.
>
> #4142 still needs to be reviewed. `2.26.1` can be shipped with or without
> it, both are fine. But it should not be a blocker for `2.26.1`.
>
> Ramanathan, you can create the `2.26.x` branch from the `rel/2.26.0` tag,
> and copy `.github/dependabot.yaml` changes from the `2.25.x` branch,
> assuming Piotr already updated that to perform PATCH-level upgrades as he
> suggested.
>
> On Wed, Jun 24, 2026 at 11:27 AM Piotr P. Karwasz <
> piotr@mailing.copernik.eu>
> wrote:
>
> >
> > Hi Ramanathan,
> >
> > On 24.06.2026 10:12, Ramanathan Muthu wrote:
> > > Please let me know if there are any additional changes or concerns
> > > before we proceed.
> >
> >
> > Your small fixes for the `*.properties` configuration format look like
> > something you could also add:
> >
> > https://github.com/apache/logging-log4j2/pull/4116
> > https://github.com/apache/logging-log4j2/pull/4142
> >
> > Bumping our dependencies to the latest patch version, might be also a
> > good idea. On 2.x Dependabot is configured to perform any kind of
> > upgrades, but you could create a 2.26.x branch first and configure
> > Dependabot to perform PATCH level upgrades.
> >
> > Piotr
> >
>
Re: [ANNOUNCE] Release Apache Log4j 2.26.1
Posted by Volkan Yazıcı <vo...@yazi.ci>.
#4146 has API changes, it cannot go to a patch release. If you disagree,
please explain.
#4142 still needs to be reviewed. `2.26.1` can be shipped with or without
it, both are fine. But it should not be a blocker for `2.26.1`.
Ramanathan, you can create the `2.26.x` branch from the `rel/2.26.0` tag,
and copy `.github/dependabot.yaml` changes from the `2.25.x` branch,
assuming Piotr already updated that to perform PATCH-level upgrades as he
suggested.
On Wed, Jun 24, 2026 at 11:27 AM Piotr P. Karwasz <pi...@mailing.copernik.eu>
wrote:
>
> Hi Ramanathan,
>
> On 24.06.2026 10:12, Ramanathan Muthu wrote:
> > Please let me know if there are any additional changes or concerns
> > before we proceed.
>
>
> Your small fixes for the `*.properties` configuration format look like
> something you could also add:
>
> https://github.com/apache/logging-log4j2/pull/4116
> https://github.com/apache/logging-log4j2/pull/4142
>
> Bumping our dependencies to the latest patch version, might be also a
> good idea. On 2.x Dependabot is configured to perform any kind of
> upgrades, but you could create a 2.26.x branch first and configure
> Dependabot to perform PATCH level upgrades.
>
> Piotr
>
Re: [ANNOUNCE] Release Apache Log4j 2.26.1
Posted by Ramanathan Muthu <ra...@gmail.com>.
Hi Piotr,
Thanks for the suggestions. Regarding those two PRs:
*#4116 <https://github.com/apache/logging-log4j2/pull/4116>*: Volkan has
already reviewed this, i will try to complete this one.
*#4142 <https://github.com/apache/logging-log4j2/pull/4142>*: This one is
still pending review. If you or Volkan have some time to review it, I can
address any feedback
*2.26.x Branch & Dependabot*: Regarding the suggestion of creating a stable
2.26.x branch first and configuring Dependabot for patch-level upgrades, I
am happy to follow whatever you and @Volkan Yazıcı <vo...@yazi.ci> decide
and confirm. Whichever way you both agree is best for the release workflow,
I will execute.
On Wed, Jun 24, 2026 at 2:57 PM Piotr P. Karwasz <pi...@mailing.copernik.eu>
wrote:
>
> Hi Ramanathan,
>
> On 24.06.2026 10:12, Ramanathan Muthu wrote:
> > Please let me know if there are any additional changes or concerns
> > before we proceed.
>
>
> Your small fixes for the `*.properties` configuration format look like
> something you could also add:
>
> https://github.com/apache/logging-log4j2/pull/4116
> https://github.com/apache/logging-log4j2/pull/4142
>
> Bumping our dependencies to the latest patch version, might be also a
> good idea. On 2.x Dependabot is configured to perform any kind of
> upgrades, but you could create a 2.26.x branch first and configure
> Dependabot to perform PATCH level upgrades.
>
> Piotr
>
Re: [ANNOUNCE] Release Apache Log4j 2.26.1
Posted by "Piotr P. Karwasz" <pi...@mailing.copernik.eu>.
Hi Ramanathan,
On 24.06.2026 10:12, Ramanathan Muthu wrote:
> Please let me know if there are any additional changes or concerns
> before we proceed.
Your small fixes for the `*.properties` configuration format look like
something you could also add:
https://github.com/apache/logging-log4j2/pull/4116
https://github.com/apache/logging-log4j2/pull/4142
Bumping our dependencies to the latest patch version, might be also a
good idea. On 2.x Dependabot is configured to perform any kind of
upgrades, but you could create a 2.26.x branch first and configure
Dependabot to perform PATCH level upgrades.
Piotr
Re: [ANNOUNCE] Release Apache Log4j 2.26.1
Posted by Ramanathan Muthu <ra...@gmail.com>.
Thanks
On Wed, Jun 24, 2026 at 5:02 PM Gary Gregory <ga...@gmail.com> wrote:
> Welcome aboard and good luck :) ! I'll be around to review an RC.
>
> Gary
>
> On Wed, Jun 24, 2026 at 4:13 AM Ramanathan Muthu
> <ra...@gmail.com> wrote:
> >
> > This is a discussion regarding the release of patch version
> >
> > I propose cutting an Apache Log4j *2.26.1* patch release.
> >
> > *Volkan (vy) *will assist me wherever PMC privileges are needed.
> >
> > The milestone for this release is here:
> > Milestone #27 <https://github.com/apache/logging-log4j2/milestone/27>
> >
> > The planned fixes for this release are:
> >
> > - Fix "Identity Malfunction" in ThrowableStackTraceRenderer by
> > using IdentityHashMap for metadata caching. This prevents
> > ArrayIndexOutOfBoundsException and NullPointerException
> > when encountering exceptions with custom equals() or
> > unstable hashCode() implementations. (Issue #3933
> > <https://github.com/apache/logging-log4j2/issues/3933>, PR #4143
> > <https://github.com/apache/logging-log4j2/pull/4143>, PR #4133
> > <https://github.com/apache/logging-log4j2/pull/4133>).
> > - Fix resource leaks in ConfigurationSource when loading
> > configurations via URL. (PR #4127
> > <https://github.com/apache/logging-log4j2/pull/4127>)
> > - Fix DatePatternConverter locale parsing when the timezone
> > is omitted. (Issue #4129
> > <https://github.com/apache/logging-log4j2/issues/4129>, PR #4130
> > <https://github.com/apache/logging-log4j2/pull/4130>)
> > - Improve logging for LinkageError and Disruptor
> > initialization failures to provide better diagnostics.
> > (Issue #2250 <https://github.com/apache/logging-log4j2/issues/2250>,
> PR
> > #4124 <https://github.com/apache/logging-log4j2/pull/4124>, PR #4134
> > <https://github.com/apache/logging-log4j2/pull/4134>)
> > - Fix RollingFileAppender with createOnDemand="true" to
> > prevent the eager creation of parent directories when no
> > logs are being written. (Issue #2006
> > <https://github.com/apache/logging-log4j2/issues/2006>, PR #4072
> > <https://github.com/apache/logging-log4j2/pull/4072>)
> > - Fix KafkaAppender retry logic to prevent reporting spurious
> > errors to the error handler after a successful retry. (Issue #4125
> > <https://github.com/apache/logging-log4j2/pull/4125>)
> > - Fix encoding of MSGID and SD-ID fields of
> > StructuredDataMessage to XML. (PR #4136
> > <https://github.com/apache/logging-log4j2/pull/4136>)
> >
> > Please let me know if there are any
> > additional changes or concerns before
> > we proceed.
>
Re: [ANNOUNCE] Release Apache Log4j 2.26.1
Posted by Gary Gregory <ga...@gmail.com>.
Welcome aboard and good luck :) ! I'll be around to review an RC.
Gary
On Wed, Jun 24, 2026 at 4:13 AM Ramanathan Muthu
<ra...@gmail.com> wrote:
>
> This is a discussion regarding the release of patch version
>
> I propose cutting an Apache Log4j *2.26.1* patch release.
>
> *Volkan (vy) *will assist me wherever PMC privileges are needed.
>
> The milestone for this release is here:
> Milestone #27 <https://github.com/apache/logging-log4j2/milestone/27>
>
> The planned fixes for this release are:
>
> - Fix "Identity Malfunction" in ThrowableStackTraceRenderer by
> using IdentityHashMap for metadata caching. This prevents
> ArrayIndexOutOfBoundsException and NullPointerException
> when encountering exceptions with custom equals() or
> unstable hashCode() implementations. (Issue #3933
> <https://github.com/apache/logging-log4j2/issues/3933>, PR #4143
> <https://github.com/apache/logging-log4j2/pull/4143>, PR #4133
> <https://github.com/apache/logging-log4j2/pull/4133>).
> - Fix resource leaks in ConfigurationSource when loading
> configurations via URL. (PR #4127
> <https://github.com/apache/logging-log4j2/pull/4127>)
> - Fix DatePatternConverter locale parsing when the timezone
> is omitted. (Issue #4129
> <https://github.com/apache/logging-log4j2/issues/4129>, PR #4130
> <https://github.com/apache/logging-log4j2/pull/4130>)
> - Improve logging for LinkageError and Disruptor
> initialization failures to provide better diagnostics.
> (Issue #2250 <https://github.com/apache/logging-log4j2/issues/2250>, PR
> #4124 <https://github.com/apache/logging-log4j2/pull/4124>, PR #4134
> <https://github.com/apache/logging-log4j2/pull/4134>)
> - Fix RollingFileAppender with createOnDemand="true" to
> prevent the eager creation of parent directories when no
> logs are being written. (Issue #2006
> <https://github.com/apache/logging-log4j2/issues/2006>, PR #4072
> <https://github.com/apache/logging-log4j2/pull/4072>)
> - Fix KafkaAppender retry logic to prevent reporting spurious
> errors to the error handler after a successful retry. (Issue #4125
> <https://github.com/apache/logging-log4j2/pull/4125>)
> - Fix encoding of MSGID and SD-ID fields of
> StructuredDataMessage to XML. (PR #4136
> <https://github.com/apache/logging-log4j2/pull/4136>)
>
> Please let me know if there are any
> additional changes or concerns before
> we proceed.