This is a vote to release the Apache Log4j 2.21.1. Website: https://logging-log4j2.staged.apache.org/log4j GitHub: https://github.com/apache/logging-log4j2 Commit: e613e9ed71279bb52753a4df810d61c11389df81 Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j Nexus: https://repository.apache.org/content/repositories/orgapachelogging-1209 Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0
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. == Countdown https://www.timeanddate.com/countdown/party?iso=20231023T2320&p0=1449&font=cursive == Release Notes This patch release contains only the fix of a `log4j-jcl` bug that prevents it from connecting with `commons-logging`. The Log4j 2.21.1 API, as well as the other artifacts, maintains binary compatibility with the previous release. Apache Log4j 2.21.1 requires Java 8 to run. The build requires JDK 11 and generates reproducible binaries. For complete information on Apache Log4j 2, including instructions on how to submit bug reports, patches, get support, or suggestions for improvement, see http://logging.apache.org/log4j/2.x/[the Apache Log4j 2 website]. === Fixed * Fixes the Apache Commons Logging (JCL) bridge: `log4j-jcl`. (#1865) Piotr
