+1 (binding) cdutz Chris
[X] Download all staged artifacts under the url specified in the release vote email. [X] Verify the signature is correct. [X] Check if the signature references an Apache email address. [X] Verify the SHA512 hashes. [X] Unzip the archive. [X] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. [X] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. [X] [RM] Verify the staged source README, RELEASE_NOTE files correspond to those in the extracted source bundle. [X] [RM] Run RAT externally to ensure there are no surprises. [X] Search for SNAPSHOT references [X] Search for Copyright references, and if they are in headers, make sure these files containing them are mentioned in the LICENSE file. [X] Build the project according to the information in the README.md file. [X] [RM] Build the project with all with-xyz profiles and tests enabled and an empty maven local repo. Von: ott.lukas.murena.io via dev <[email protected]> Datum: Montag, 27. Juli 2026 um 16:31 An: [email protected] <[email protected]> Cc: [email protected] <[email protected]> Betreff: Re: [VOTE] Apache PLC4X Build-Tools Code-Generation 1.9.0 RC1 Minor remarks: https://www.apache.org/legal/release-policy.html/validation.html#approving-a-release -> 404 +1 (binding) Lukas [x] all staged artifacts under the url specified in the release vote email. [x] Verify the signature is correct. [x] Check if the signature references an Apache email address. [x] Verify the SHA512 hashes. [x] Unzip the archive. [x] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. [x] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. [x] [RM] Verify the staged source README, RELEASE_NOTE files correspond to those in the extracted source bundle. [x] [RM] Run RAT externally to ensure there are no surprises. [x] Search for SNAPSHOT references [x] Search for Copyright references, and if they are in headers, make sure these files containing them are mentioned in the LICENSE file. [x] Build the project according to the information in the README.md file. [x] [RM] Build the project with all with-xyz profiles and tests enabled and an empty maven local repo. executed commands: gpg --verify apache-plc4x-code-generation-1.9.0-source-release.zip.asc apache-plc4x-code-generation-1.9.0-source-release.zip shasum -a512 apache-plc4x-code-generation-1.9.0-source-release.zip java -jar apache-rat-0.18.jar apache-plc4x-code-generation-1.9.0-source-release.zip > rat.log INFO: RAT summary: INFO: Approved: 81 INFO: Archives: 0 INFO: Binaries: 2 INFO: Document types: 3 INFO: Ignored: 0 INFO: License categories: 2 INFO: License names: 2 INFO: Notices: 6 INFO: Standards: 82 INFO: Unapproved: 1 INFO: Unknown: 1 find . -type f -name 'pom.xml' -exec grep -l "SNAPSHOT" {} \; Build with ./mvnw clean install -X Apache Maven 4.0.0-rc-5 (fb3ecaef88106acb40467a450248dfdbd75f3b35) Maven home: /home/luk/.m2/wrapper/dists/apache-maven-4.0.0-rc-5/1d86e591 Java version: 21.0.11, vendor: Ubuntu, runtime: /usr/lib/jvm/java-21-openjdk-amd64 Default locale: de_DE, platform encoding: UTF-8 OS name: "linux", version: "7.0.11-76070011-generic", arch: "amd64", family: "unix" Command line: /usr/lib/jvm/java-21-openjdk-amd64/bin/java --add-exports jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED http://jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED http://jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.parser=ALL-UNNAMED http://jdk.compiler/com.sun.tools.javac.parser=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED http://jdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED http://jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED --enable-native-access=ALL-UNNAMED -classpath /home/luk/.m2/wrapper/dists/apache-maven-4.0.0-rc-5/1d86e591/boot/plexus-classworlds-2.9.0.jar -Dclassworlds.conf=/home/luk/.m2/wrapper/dists/apache-maven-4.0.0-rc-5/1d86e591/bin/m2.conf -Dmaven.home=/home/luk/.m2/wrapper/dists/apache-maven-4.0.0-rc-5/1d86e591 -Dmaven.mainClass=org.apache.maven.cling.MavenCling -Dlibrary.jline.path=/home/luk/.m2/wrapper/dists/apache-maven-4.0.0-rc-5/1d86e591/lib/jline-native -Dmaven.multiModuleProjectDirectory=/home/luk/Development/plc4x/build-tools/apache-plc4x-code-generation-1.9.0-source-release/apache-plc4x-code-generation-1.9.0 org.codehaus.plexus.classworlds.launcher.Launcher clean install -X Terminal: PosixSysTerminal (type=xterm-256color, provider=jni, pty=org.jline.terminal.impl.jni.linux.LinuxNativePty) [DEBUG] Created adapter factory; available factories [file-lock, rwlock-local, semaphore-local, noop]; available name mappers [discriminating, file-gav, file-hgav, file-static, gav, static] [INFO] Reactor Summary for PLC4X Build Tools: Code Generation 1.9.0: [INFO] [INFO] PLC4X Build Tools: Code Generation ................................................................... SUCCESS [ 3.108 s] [INFO] PLC4X Build Tools: Code Generation: Base Types ....................................................... SUCCESS [ 6.838 s] [INFO] PLC4X Build Tools: Code Generation: Language Base .................................................... SUCCESS [ 0.364 s] [INFO] PLC4X Build Tools: Code Generation: Protocol Base .................................................... SUCCESS [ 0.266 s] [INFO] PLC4X Build Tools: Code Generation: PLC4X Maven Plugin ............................................... SUCCESS [ 7.592 s] [INFO] -------------------------------------------------------------------------------------------------------------------------- [INFO] BUILD SUCCESS Am 27. Juli 2026 um 15:13 schrieb "Christofer Dutz" <[email protected] mailto:[email protected]?to=%22Christofer%20Dutz%22%20%3Cchristofer.dutz%40c-ware.de%3E >: > > Apache PLC4X Build-Tools Code-Generation 1.9.0 has been staged under [2] > and it’s time to vote on accepting it for release. > > All Maven artifacts are available under [1]. Voting will be open for 72hr. > > A minimum of 3 binding +1 votes and more binding +1 than binding -1 > are required to pass. > > Repository: https://gitbox.apache.org/repos/asf/plc4x-build-tools.git > Release tag: releases/code-generation/1.9.0 > Hash for the release tag: d66981569dec99caf5957d86d035155460758b92 > > Per [3] "Before voting +1 PMC members are required to download > the signed source code package, compile it as provided, and test > the resulting executable on their own platform, along with also > verifying that the package meets the requirements of the ASF policy > on releases." > > You can achieve the above by following [4]. > > [ ] +1 accept (indicate what you validated - e.g. performed the non-RM items > in [4]) > [ ] -1 reject (explanation required) > > [1] https://repository.apache.org/content/repositories/orgapacheplc4x-1064 > [2] > https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-generation/1.9.0/rc1/ > [3] https://www.apache.org/dev/release/validation.html#approving-a-release > [4] https://plc4x.apache.org/plc4x/latest/developers/release/validation.html >
