I am confused. We had a vote thread for 0.4.0. Did you close that vote? Maybe I just didn’t get that email again.
The commit tag for this vote is not the same as the previous commit tag. So is this really rc-2? I despise having multiple release vote threads for the same release number as it is impossible to differentiate them. Ralph > On Jul 3, 2023, at 2:29 PM, Volkan Yazıcı <vol...@yazi.ci> wrote: > > This is a vote to release the Apache Log4j Tools 0.4.0. > > Source repository: https://github.com/apache/logging-log4j-tools > Commit: 15d888fe488660b0bb5d3fc3e95c9915f277fbee > Distribution: 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. At least 3 +1 votes and more positive than negative votes are > required. > > # Release Notes > > This minor release contains small enhancements. > Most importantly, this marks the first release where the project uses > itself to generate release notes! > > ## 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
