[RESULT][VOTE][LAZY] Release Apache Logging Parent `11.2.0` (RC1)
On Tue, 27 Aug 2024 at 11:30, Piotr P. Karwasz wrote: > > This is a lazy-vote to release the Apache Logging Parent `11.2.0`. > > Website: https://logging.staged.apache.org/logging-parent-11.2.0 > GitHub: https://github.com/apache/logging-parent > Commit: b001c784d2a53c5f046758bfaea2550eb8dcb299 > Distribution: > https://dist.apache.org/repos/dist/dev/logging/logging-parent/11.2.0 > Nexus: > https://repository.apache.org/content/repositories/orgapachelogging-1292 > Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0 > > Please download, test, and cast your votes on this mailing list. > > [ ] +1, release the artifacts > [ ] -1, don't release, because... And here is my +1. With that the lazy vote passes with a single +1 from myself. I will continue the release process. Piotr
[ANNOUNCE] Apache Logging Parent `11.2.0` released
Apache Logging Parent team is pleased to announce the `11.2.0` release. This project contains the parent POM for other Maven-based Apache Logging Services projects. For further information (support, download, etc.) see the project website[1]. [1] https://logging.apache.org/logging-parent == Release Notes This minor release integrates Gradle Develocity into the reusable workflows. See Develocity Configuration[1] for more details. [1] https://logging.apache.org/logging-parent/features.html#develocity-configuration === Added * Add option to disable reproducibility check in reusable builds. (#195) * Add option to enable Develocity in builds. === Updated * Update `actions/checkout` to version `4.1.7` (#192) * Update `actions/setup-java` to version `4.2.2` (#217) * Update `actions/upload-artifact` to version `4.3.6` (#219) * Update `com.github.spotbugs:spotbugs-annotations` to version `4.8.6` (#194) * Update `com.github.spotbugs:spotbugs-maven-plugin` to version `4.8.6.2` (#201) * Update `com.google.errorprone:error_prone_core` to version `2.30.0` (#222) * Update `com.palantir.javaformat:palantir-java-format` to version `2.50.0` (#226) * Update `dependabot/fetch-metadata` to version `2.2.0` (#200) * Update `github/codeql-action` to version `3.26.5` (#230) * Update `org.apache:apache` to version `33` (#203) * Update `org.codehaus.mojo:build-helper-maven-plugin` to version `3.6.0` (#183) * Update `org.codehaus.mojo:exec-maven-plugin` to version `3.4.1` (#223) * Update `org.cyclonedx:cyclonedx-maven-plugin` to version `2.8.1` (#216) * Update `org.eclipse.jgit:org.eclipse.jgit` to version `6.10.0.202406032230-r` (#190) * Update `org.jspecify:jspecify` to version `1.0.0` (#206) * Update `ossf/scorecard-action` to version `2.4.0` (#212)
Re: Delaying publication of `log4j-flume-ng` in 3.x
Hi Ralph, On Fri, 30 Aug 2024 at 08:44, Piotr P. Karwasz wrote: > On Thu, 29 Aug 2024 at 23:32, Ralph Goers wrote: > > So I will say I am fine with moving it to its own module. Can it be moved > > while keeping the 2.x and main branches? > > Sure, I created a `logging-log4j-flume` repository and I'll move both > branches there preserving the commit history. The current code of both branches is available at: https://github.com/apache/logging-log4j-flume This module needs to depend on a released version of `log4j-core`, so I'll fix its build scripts after `2.24.0` hits the shelves. Piotr
