Re: Please update Flume DOAP
On Tue, 19 Mar 2024 at 20:40, Jan Friedrich wrote: > > Hi Sebb, > > is this what you want? > > https://github.com/apache/logging-flume/pull/421 That is what needs to be done so that projects.a.o works properly for Flume. [It is not something that I personally want] > Regards. > > Jan > > Tuesday, March 19, 2024, 6:44:10 PM, you wrote: > > > PING - still needs to be fixed. > > > On Fri, 15 Mar 2024 at 00:42, sebb wrote: > >> > >> Note: this is the line that needs to be fixed: > >> > >> https://github.com/apache/logging-flume/blob/trunk/doap_Flume.rdf#L29 > >> > >> On Thu, 14 Mar 2024 at 08:57, sebb wrote: > >> > > >> > Ping? > >> > > >> > On Thu, 7 Mar 2024 at 11:42, sebb wrote: > >> > > > >> > > https://github.com/apache/logging-flume/blob/trunk/doap_Flume.rdf > >> > > still shows the PMC as Flume; please update to show PMC Logging. > >> > > > >> > > Thanks, > >> > > Sebb >
Re: [VOTE] Release Apache Log4j Tools 0.8.0 (RC2)
+1 Tested src zip file SHA512 OK ASC OK Apache RAT check OK Build 'mvn clean verify' OK Using: openjdk version "17.0.10" 2024-01-16 OpenJDK Runtime Environment Homebrew (build 17.0.10+0) OpenJDK 64-Bit Server VM Homebrew (build 17.0.10+0, mixed mode, sharing) Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) Maven home: /usr/local/Cellar/maven/3.9.6/libexec Java version: 17.0.10, vendor: Homebrew, runtime: /usr/local/Cellar/openjdk@17/17.0.10/libexec/openjdk.jdk/Contents/Home Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "14.3.1", arch: "x86_64", family: "mac" Darwin 23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:28:58 PST 2023; root:xnu-10002.81.5~7/RELEASE_X86_64 x86_64 Gary On Tue, Mar 19, 2024 at 7:35 AM Volkan Yazıcı wrote: > > This is a vote to release the Apache Log4j Tools 0.8.0 (RC2). > > Website: https://logging.staged.apache.org/log4j/tools > GitHub: https://github.com/apache/logging-log4j-tools > Commit: 2bb07037bbbfe14fe1c224d46a3e4135b48ffde6 > Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-tools > Nexus: > https://repository.apache.org/content/repositories/orgapachelogging-1265 > 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. > > === 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 > # If preferred, augment `mvnw` with `-DskipTests` to speed things up > > === Release notes > > This release delivers the first version of Log4j Docgen (Documentation > Generator). It is a set of tools to auto-generate the Log4j plugin > documentation (to be integrated into the website) and the Log4j > configuration XSD file (for assisting the configuration of the Log4j > runtime, i.e., `log4j2.xml`) from the Log4j source code. See the > project website for details. > > Added > > * Add the `log4j-docgen` et al. containing a universal XML model to > document Log4j plugins > > Changed > > * Move Log4j Changelog XML namespace and schema location to > `https://logging.apache.org/xml/ns` and > `https://logging.apache.org/xml/ns/log4j-changelog-0.xsd`, > respectively > > Removed > > * Remove `author` from Log4j Changelog. It was yet another bit to > maintain and created role-related (who did what) problems. Many modern > software projects use a VCS (e.g., Git) and support services (e.g., > GitHub) which make it trivial to trace back the origin of a change > using commit and issue IDs. > > Updated > > * Update `org.apache.logging:logging-parent` to version `10.6.0` > * Update `jakarta.inject:jakarta.inject-api` to version `2.0.1` (#94) > * Update `org.apache.logging.log4j:log4j-core` to version `2.23.1` (#108) > * Update `org.apache.logging.log4j:log4j-plugins` to version > `3.0.0-beta2` (#107) > * Update `org.apache.maven.plugin-tools:maven-plugin-annotations` to > version `3.11.0` (#98) > * Update `org.assertj:assertj-core` to version `3.25.3` (#104) > * Update `org.codehaus.modello:modello-maven-plugin` to version `2.3.0` (#105) > * Update `org.junit:junit-bom` to version `5.10.2` (#103)
Re: Please update Flume DOAP
Interesting. I hadn’t noticed that the GitHub repos had changed urls. Ralph > On Mar 19, 2024, at 1:40 PM, Jan Friedrich wrote: > > Hi Sebb, > > is this what you want? > > https://github.com/apache/logging-flume/pull/421 > > Regards. > > Jan > > Tuesday, March 19, 2024, 6:44:10 PM, you wrote: > >> PING - still needs to be fixed. > >> On Fri, 15 Mar 2024 at 00:42, sebb wrote: >>> >>> Note: this is the line that needs to be fixed: >>> >>> https://github.com/apache/logging-flume/blob/trunk/doap_Flume.rdf#L29 >>> >>> On Thu, 14 Mar 2024 at 08:57, sebb wrote: Ping? On Thu, 7 Mar 2024 at 11:42, sebb wrote: > > https://github.com/apache/logging-flume/blob/trunk/doap_Flume.rdf > still shows the PMC as Flume; please update to show PMC Logging. > > Thanks, > Sebb >
Re: Please update Flume DOAP
Hi Sebb, is this what you want? https://github.com/apache/logging-flume/pull/421 Regards. Jan Tuesday, March 19, 2024, 6:44:10 PM, you wrote: > PING - still needs to be fixed. > On Fri, 15 Mar 2024 at 00:42, sebb wrote: >> >> Note: this is the line that needs to be fixed: >> >> https://github.com/apache/logging-flume/blob/trunk/doap_Flume.rdf#L29 >> >> On Thu, 14 Mar 2024 at 08:57, sebb wrote: >> > >> > Ping? >> > >> > On Thu, 7 Mar 2024 at 11:42, sebb wrote: >> > > >> > > https://github.com/apache/logging-flume/blob/trunk/doap_Flume.rdf >> > > still shows the PMC as Flume; please update to show PMC Logging. >> > > >> > > Thanks, >> > > Sebb
Re: [VOTE] Release Apache Log4j Tools 0.8.0 (RC2)
Hi Volkan, On Tue, 19 Mar 2024 at 12:35, Volkan Yazıcı wrote: > > This is a vote to release the Apache Log4j Tools 0.8.0 (RC2). > > Website: https://logging.staged.apache.org/log4j/tools > GitHub: https://github.com/apache/logging-log4j-tools > Commit: 2bb07037bbbfe14fe1c224d46a3e4135b48ffde6 > Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-tools > Nexus: > https://repository.apache.org/content/repositories/orgapachelogging-1265 > Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0 > > Please download, test, and cast your votes on this mailing list. > > [ ] +1, release the artifacts > [ ] -1, don't release, because... I repeated the same checks as in RC1: * distribution hashes: OK * distribution signatures: OK * Maven artifacts are reproducible: OK * Maven artifacts are the same as binary distribution: OK * new artifacts are documented on the website. +1, release the artifacts. Piotr
Re: Please update Flume DOAP
PING - still needs to be fixed. On Fri, 15 Mar 2024 at 00:42, sebb wrote: > > Note: this is the line that needs to be fixed: > > https://github.com/apache/logging-flume/blob/trunk/doap_Flume.rdf#L29 > > On Thu, 14 Mar 2024 at 08:57, sebb wrote: > > > > Ping? > > > > On Thu, 7 Mar 2024 at 11:42, sebb wrote: > > > > > > https://github.com/apache/logging-flume/blob/trunk/doap_Flume.rdf > > > still shows the PMC as Flume; please update to show PMC Logging. > > > > > > Thanks, > > > Sebb
Re: [VOTE] Release Apache Log4j Tools 0.8.0 (RC2)
+1, tested as before On Tue, Mar 19, 2024, at 12:34, Volkan Yazıcı wrote: > This is a vote to release the Apache Log4j Tools 0.8.0 (RC2). > > Website: https://logging.staged.apache.org/log4j/tools > GitHub: https://github.com/apache/logging-log4j-tools > Commit: 2bb07037bbbfe14fe1c224d46a3e4135b48ffde6 > Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-tools > Nexus: > https://repository.apache.org/content/repositories/orgapachelogging-1265 > 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. > > === 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 > # If preferred, augment `mvnw` with `-DskipTests` to speed things up > > === Release notes > > This release delivers the first version of Log4j Docgen (Documentation > Generator). It is a set of tools to auto-generate the Log4j plugin > documentation (to be integrated into the website) and the Log4j > configuration XSD file (for assisting the configuration of the Log4j > runtime, i.e., `log4j2.xml`) from the Log4j source code. See the > project website for details. > > Added > > * Add the `log4j-docgen` et al. containing a universal XML model to > document Log4j plugins > > Changed > > * Move Log4j Changelog XML namespace and schema location to > `https://logging.apache.org/xml/ns` and > `https://logging.apache.org/xml/ns/log4j-changelog-0.xsd`, > respectively > > Removed > > * Remove `author` from Log4j Changelog. It was yet another bit to > maintain and created role-related (who did what) problems. Many modern > software projects use a VCS (e.g., Git) and support services (e.g., > GitHub) which make it trivial to trace back the origin of a change > using commit and issue IDs. > > Updated > > * Update `org.apache.logging:logging-parent` to version `10.6.0` > * Update `jakarta.inject:jakarta.inject-api` to version `2.0.1` (#94) > * Update `org.apache.logging.log4j:log4j-core` to version `2.23.1` (#108) > * Update `org.apache.logging.log4j:log4j-plugins` to version > `3.0.0-beta2` (#107) > * Update `org.apache.maven.plugin-tools:maven-plugin-annotations` to > version `3.11.0` (#98) > * Update `org.assertj:assertj-core` to version `3.25.3` (#104) > * Update `org.codehaus.modello:modello-maven-plugin` to version `2.3.0` (#105) > * Update `org.junit:junit-bom` to version `5.10.2` (#103)
[VOTE] Release Apache Log4j Tools 0.8.0 (RC2)
This is a vote to release the Apache Log4j Tools 0.8.0 (RC2). Website: https://logging.staged.apache.org/log4j/tools GitHub: https://github.com/apache/logging-log4j-tools Commit: 2bb07037bbbfe14fe1c224d46a3e4135b48ffde6 Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-tools Nexus: https://repository.apache.org/content/repositories/orgapachelogging-1265 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. === 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 # If preferred, augment `mvnw` with `-DskipTests` to speed things up === Release notes This release delivers the first version of Log4j Docgen (Documentation Generator). It is a set of tools to auto-generate the Log4j plugin documentation (to be integrated into the website) and the Log4j configuration XSD file (for assisting the configuration of the Log4j runtime, i.e., `log4j2.xml`) from the Log4j source code. See the project website for details. Added * Add the `log4j-docgen` et al. containing a universal XML model to document Log4j plugins Changed * Move Log4j Changelog XML namespace and schema location to `https://logging.apache.org/xml/ns` and `https://logging.apache.org/xml/ns/log4j-changelog-0.xsd`, respectively Removed * Remove `author` from Log4j Changelog. It was yet another bit to maintain and created role-related (who did what) problems. Many modern software projects use a VCS (e.g., Git) and support services (e.g., GitHub) which make it trivial to trace back the origin of a change using commit and issue IDs. Updated * Update `org.apache.logging:logging-parent` to version `10.6.0` * Update `jakarta.inject:jakarta.inject-api` to version `2.0.1` (#94) * Update `org.apache.logging.log4j:log4j-core` to version `2.23.1` (#108) * Update `org.apache.logging.log4j:log4j-plugins` to version `3.0.0-beta2` (#107) * Update `org.apache.maven.plugin-tools:maven-plugin-annotations` to version `3.11.0` (#98) * Update `org.assertj:assertj-core` to version `3.25.3` (#104) * Update `org.codehaus.modello:modello-maven-plugin` to version `2.3.0` (#105) * Update `org.junit:junit-bom` to version `5.10.2` (#103)
Re: [VOTE] Release Apache Log4j Tools 0.8.0
I need to cancel this vote. Figured `SchemaGenerator` needs to accept a schema version to correctly set the `version` attribute in the generated XSD. Sorry for the inconvenience. On Mon, Mar 18, 2024 at 10:25 PM Volkan Yazıcı wrote: > > This is a vote to release the Apache Log4j Tools 0.8.0. > > Website: https://logging.staged.apache.org/log4j/tools > GitHub: https://github.com/apache/logging-log4j-tools > Commit: 2681946896f289cd7432480712debad6af5ee684 > Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-tools > Nexus: > https://repository.apache.org/content/repositories/orgapachelogging-1264 > 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. > > === 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 > # If preferred, augment `mvnw` with `-DskipTests` to speed things up > > === Release notes > > This release delivers the first version of Log4j Docgen (Documentation > Generator). It is a set of tools to auto-generate the Log4j plugin > documentation (to be integrated into the website) and the Log4j > configuration XSD file (for assisting the configuration of the Log4j > runtime, i.e., `log4j2.xml`) from the Log4j source code. See the > project website for details. > > Added > > * Add the `log4j-docgen` et al. containing a universal XML model to > document Log4j plugins > > Changed > > * Move Log4j Changelog XML namespace and schema location to > `https://logging.apache.org/xml/ns` and > `https://logging.apache.org/xml/ns/log4j-changelog-0.xsd`, > respectively > > Removed > > * Remove `author` from Log4j Changelog. It was yet another bit to > maintain and created role-related (who did what) problems. Many modern > software projects use a VCS (e.g., Git) and support services (e.g., > GitHub) which make it trivial to trace back the origin of a change > using commit and issue IDs. > > Updated > > * Update `org.apache.logging:logging-parent` to version `10.6.0` > * Update `jakarta.inject:jakarta.inject-api` to version `2.0.1` (#94) > * Update `org.apache.logging.log4j:log4j-core` to version `2.23.1` (#108) > * Update `org.apache.logging.log4j:log4j-plugins` to version > `3.0.0-beta2` (#107) > * Update `org.apache.maven.plugin-tools:maven-plugin-annotations` to > version `3.11.0` (#98) > * Update `org.assertj:assertj-core` to version `3.25.3` (#104) > * Update `org.codehaus.modello:modello-maven-plugin` to version `2.3.0` (#105) > * Update `org.junit:junit-bom` to version `5.10.2` (#103)
Re: [VOTE] Release Apache Log4j Tools 0.8.0
+1 Did the same checks as Piotr. Thanks for the work! On Mon, Mar 18, 2024, at 23:04, Piotr P. Karwasz wrote: > Hi Volkan, > > On Mon, 18 Mar 2024 at 22:25, Volkan Yazıcı wrote: >> >> This is a vote to release the Apache Log4j Tools 0.8.0. >> >> Website: https://logging.staged.apache.org/log4j/tools >> GitHub: https://github.com/apache/logging-log4j-tools >> Commit: 2681946896f289cd7432480712debad6af5ee684 >> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-tools >> Nexus: >> https://repository.apache.org/content/repositories/orgapachelogging-1264 >> Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0 >> >> Please download, test, and cast your votes on this mailing list. >> >> [ ] +1, release the artifacts >> [ ] -1, don't release, because... > > * distribution hashes: OK > * distribution signatures: OK > * Maven artifacts are reproducible: OK > * Maven artifacts are the same as binary distribution: OK > * new artifacts are documented on the website. > > +1, release the artifacts. > > Piotr
Re: [VOTE] Release Apache Log4Net 2.0.17
+1 Checked only formalities since I don't have an idea about .NET, but so far, looks good! On Sat, Mar 16, 2024, at 11:07, Volkan Yazıcı wrote: > +1 > > Checked sigs, hashes, `LICENSE` files, and release notes. > > > > On Fri, Mar 15, 2024 at 1:29 PM Davyd McColl wrote: >> >> Hi all, >> >> This is a vote to release the Apache Log4net 2.0.17. >> >> Website: >> https://logging.staged.apache.org/log4net/release/release-notes.html >> GitHub: https://github.com/apache/logging-log4net >> GitHub release (pre-release): >> https://github.com/apache/logging-log4net/releases/tag/rel/2.0.17-rc1 >> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4net >> >> 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. >> >> >> Thanks to Jan for basically doing all of this (: >> >> -d >>
