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.
