On Mon, May 4, 2026 at 2:50 PM Piotr P. Karwasz <[email protected]> wrote: > > Hi Volkan, > > On 4.05.2026 09:45, Volkan Yazıcı wrote: > > This is a vote to release the Apache Log4j `2.26.0`. > > > > [...] > > > > [ ] +1, release the artifacts > > [ ] -1, don't release, because... > > > +1 (binding), release the artifacts. > > I followed the standard verification process: > > 1. Verified checksums > 2. Verified signatures > 3. Verified the build (unit tests + reproducibility) > > For the last step I needed a slightly different invocation: > > chmod a+x mvnw > CI=true ./mvnw verify artifact:compare \ > -Prelease,\!docker \ > > -Dreference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1325 > > I explained the need for `CI=true` in [1]. As for the rest: > > - We'll need to either bump `mvnw` to a version that can be invoked > through `sh`, or replace the custom source archive script with `git > archive`.
This is what I warned against a while back. We should not stuff a random old version of Maven on people's machines. Gary > - My version of Docker doesn't play well with the `docker-maven-plugin` > version used in the build, so I had to skip the Docker tests. > > Note also that the CI build had one failure in > `integration-test (2.26.0) / build (windows-latest)`: > > https://github.com/apache/logging-log4j2/actions/runs/25259932526 > > This failure is unrelated to the released version: it's a bug in an > integration test that was only exercised on UNIX. > > Thank you for seeing this release through, Volkan. This one wasn't easy, > with the long gap since the last minor release and the various build > issues along the way, and I really appreciate you carrying it across the > finish line. > > Piotr > > [1] https://lists.apache.org/thread/46dblzlq1x7hm4wjqgqtc32ohxs5rddj
