I am canceling this RC2 vote. Recent `log4j-3.0.0-beta1` release caused some `log4j-changelog` issues to surface. I have already pushed fixes addressing those issues. Due to the recent versioning scheme discussion, I have also added `UPDATED` changelog entry type too. We should ideally get all these into the upcoming `logging-parent` release.
In conclusion, I will first issue a new `log4j-tools` release and then a `logging-parent` version `0.5.0` RC3. On Mon, Dec 11, 2023 at 9:57 AM Volkan Yazıcı <vol...@yazi.ci> wrote: > This is a lazy-vote to release the Apache Logging Parent version `10.5.0` > (RC2). > > Website: https://logging.staged.apache.org/logging-parent > GitHub: https://github.com/apache/logging-parent > Commit: 9bb44007955fd892d31c8c65f02cfbdd03d461b3 > Distribution: > https://dist.apache.org/repos/dist/dev/logging/logging-parent > Nexus: > https://repository.apache.org/content/repositories/orgapachelogging-1241 > 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. > > === Review kit > > The minimum set of steps needed to review the uploaded distribution > files in the Subversion repository can be summarized as follows: > > # Check out the distribution > svn co https://dist.apache.org/repos/... && cd $_ > > # Verify checksums > shasum --check *.sha512 > > # Verify signatures > wget -O - https://downloads.apache.org/logging/KEYS | gpg --import > for sigFile in *.asc; do gpg --verify $sigFile; done > > # Verify reproduciblity > umask 0022 > unzip *-src.zip -d src > cd src > export NEXUS_REPO=https://repository.apache.org/content/... > sh mvnw -Prelease verify artifact:compare -Dreference.repo=$NEXUS_REPO > > === Release notes > > This minor release contains dependency updates and a change in the way > BND is employed. > > BND Maven Plugins are upgraded to version `7.0.0`, which requires Java 17. > Log4j was the blocker for this upgrade and the issue is resolved in > apache/logging-log4j2#2021. > > ==== Changed > > * Switch from `bnd:jar` to `bnd:bnd-process` to improve integration > with the ecosystem; IDEs, Maven plugins, etc. (#69) > * Update `biz.aQute.bnd:bnd-baseline-maven-plugin` to version `7.0.0` (#78) > * Update `biz.aQute.bnd:bnd-maven-plugin` to version `7.0.0` > * Update `com.diffplug.spotless:spotless-maven-plugin` to version `2.41.1` > (#70) > * Update `com.github.spotbugs:spotbugs-annotations` to version `4.8.2` > (#68) > * Update `com.github.spotbugs:spotbugs-maven-plugin` to version `4.8.2.0` > (#71) > * Update `org.apache:apache` to version `31` (#73) > * Update `org.apache.logging.log4j:log4j-changelog-maven-plugin` to > version `0.6.0` (#72) >
