This is a vote to release the Apache Logging Parent 10.0.0. Source repository: https://github.com/apache/logging-parent Commit: 9aaef0c594cd7dd7fe1f9ffe244f55f20439b7ce Distribution: https://dist.apache.org/repos/dist/dev/logging/logging-parent Nexus: https://repository.apache.org/content/repositories/orgapachelogging-1166 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. At least 3 +1 votes and more positive than negative votes are required. # RC2..RC3 changes RC3 introduces following changes over RC2[1]: - Fixed plugin definitions [1] https://github.com/apache/logging-parent/compare/24a4b9bc706ed978f36c28c114e289547c4a71ad..9aaef0c594cd7dd7fe1f9ffe244f55f20439b7ce # RC1..RC2 changes RC2 introduces following changes over RC1[2]: - Set version to `10.0.0` (requested by Matt & Ralph) - Fix SVN path in `generate-email.sh` (requested by Gary) - Split the distribution into `src` and `bin` parts (requested by Gary) - Automate `revision` property update in `pom.xml` in CI (requested by Ralph) - Automate changelog release in CI (requested by Ralph) [2] https://github.com/apache/logging-parent/compare/3dd83461faa058690a5ed821ee81dfc2d744ec7c..24a4b9bc706ed978f36c28c114e289547c4a71ad # Remarks - `logging-parent` doesn't contain any binary artifacts, it is a `pom.xml` with some reusable CI workflow YAMLs. - One can reproduce the very same distribution by checking out the commit and running `./mvnw -P distribution -DattachmentCount=0 -DattachmentFilepathPattern=x` # Release Notes This minor release contains various improvements that we expect to relieve the load on `pom.xml` and GitHub Actions workflows of Maven-based projects we parent. This is of particular importance while managing and cutting releases from multiple repositories. See `README.adoc` for the complete list of features and their usage. See this[3] `log4j-tools` GitHub Actions workflow run demonstrating a successful release cut using a SNAPSHOT version of this `logging-parent` release. All preparations (release notes, source and binary distributions, vote & announcement emails, etc.) are staged to both Nexus and SVN and waiting the release manager to proceed. [3] https://github.com/apache/logging-log4j-tools/actions/runs/6120631921 ## Changes ### Added * Added `changelog-export` profile to easily export changelogs to Markdown files * Added `changelog-release` profile to easily move `src/changelog/.?.x.x` contents to their associated release directory * Added `deploy` profile to ease the Maven `deploy` goal * Added `distribution` profile to easily create a distribution file containing Git-tracked sources, release notes, binary attachments, `NOTICE.txt`, etc. * Documented release instructions (i.e., `RELEASING.md`) * Added `release` profile to share common release-specific Maven configuration * Added reusable GitHub Actions workflows to share CI boilerplate for other repositories * Switched to using `log4j-changelog-maven-plugin` for managing changelog and release notes ### Changed * Switched to semantic versioning (old version: `9`, new version: `10.0.0`)
