Hi Ramanathan, On 29.06.2026 13:39, Ramanathan Muthu wrote: > This is a vote to release Apache Log4j 2.26.1. > > Website: https://logging.staged.apache.org/log4j/2.26.1/index.html > GitHub: https://github.com/apache/logging-log4j2 > Commit: dd0f9d255e24e6bcc13bd2641407a409c0524803 > Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j/2.26.1 > Nexus: > https://repository.apache.org:443/content/repositories/orgapachelogging-1327 > 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...
+1, release the artifacts. Congratulations on your first release candidate! The verification was flawless: 1. Checksums match. 2. Signatures match. 3. The release is reproducible, all unit tests pass, and all integration tests pass: https://github.com/apache/logging-log4j2/actions/runs/28354528411 A few notes for other voters: - Our Maven wrapper version has a known issue, so `sh mvnw` does not work. Either add the executable bit or use a local Maven distribution instead. - Reproducibility requires running with the `CI=true` environment variable set. - I was unable to run the Docker tests due to a version mismatch between my Docker API and the docker-maven-plugin. Piotr
