-1 (binding) a) the distribution directory contains only binaries. An ASF release must have a source distribution. b) I believe you worked with INFRA to get permission to use the automation signing key, but without a link to that and instructions that pointedly require keys owned by individuals this is going to create problems.
-1 on this being a lazy vote. I have every intention of using the changelog plugin in Flume once I am comfortable that it is ready for prime time without hand-holding. Ralph > On Jul 2, 2023, at 11:54 AM, Volkan Yazıcı <vol...@yazi.ci> wrote: > > This is a lazy vote to release the Apache Log4j Tools 7.8.0. > > This minor release contains small enhancements. Most importantly, this > marks the first release where the project uses itself to generate > release notes! > > Source repository: https://github.com/apache/logging-log4j-tools > Commit: b4d75a1270d4eeaa99ffd1425332572ed3bd3e73 > Artifacts: https://dist.apache.org/repos/dist/dev/logging/log4j > Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0 > > Please download, test, and cast your votes on the Log4j developers 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. > > ## Changes > > ### Added > > * Add `versionPattern` (i.e., the regular expression pattern for > parsing versions) parameter to the Maven `release` goal (#63) > > ### Changed > > * Change the default value of `outputDirectory` to > `${project.build.directory}/generated-sources/site/changelog` for the > Maven `export` goal > * Migrate from `CHANGELOG.adoc` to using `log4j-changelog-maven-plugin` > > ### Fixed > > * Improve Maven `release` goal to accommodate repetitive invocations
