Why are we releasing 2.25.x? When we are on 2.26.x?

Gary

On Wed, Jul 1, 2026, 10:22 Ramanathan Muthu <[email protected]>
wrote:

> This is a vote to release Apache Log4j `2.25.5`.
>
> Website: https://logging.staged.apache.org/log4j/2.25.5/index.html
> GitHub: https://github.com/apache/logging-log4j2
> Commit: 2e1d9c6284af1da1dec189f4b5b98ac0f32a7645
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j/2.25.5
> Nexus:
> https://repository.apache.org:443/content/repositories/orgapachelogging-1328
> Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0
> Review kit:
> https://logging.apache.org/logging-parent/release-review-instructions.html
>
> Please download, test, and cast your votes on this mailing list.
>
> [ ] +1, release the artifacts
> [ ] -1, don't release, because...
>
> This vote is open for 72 hours and will pass unless getting a
> net negative vote count. All votes are welcome and we encourage
> everyone to test the release, but only the Logging Services PMC
> votes are officially counted. At least 3 +1 votes and more
> positive than negative votes are required.
>
> == Release Notes
>
> This patch release delivers certain fixes on top of `2.25.4`.
>
> === Fixed
>
> * Improve logging for `LinkageError` scenarios involving
> the LMAX Disruptor library (#2250, #4124)
> * Fix the createOnDemand behavior of RollingFileAppender (#2006, #4072)
> * Fix resource leaks in ConfigurationSource when loading
> configuration via URL fails (#4127)
> * Improve documentation for locale handling in Pattern Layout
> date pattern converter (#4129, #4130)
> * Fix handling of non-finite numbers encoding MapMessage to JSON (#4163)
> * Fix encoding of MSGID and SD-ID fields of
> StructuredDataMessage to XML (#4136)
> * Fix stack trace rendering for exceptions with identity
> malfunction (e.g., colliding equals() and/or hashCode()
> implementations) (#3933, #4133)
> * Fix KafkaAppender reporting error to error handler even
> after a successful retry (#4125)
>

Reply via email to