-1 (PMC/binding) Chris
[OK] Download all staged artifacts under the url specified in the release vote email. [OK] Verify the signature is correct. [OK] Check if the signature references an Apache email address. [OK] Verify the SHA512 hashes. [OK] Unzip the archive. [OK] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. [MINOR] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. - The RELEASE_NOTES mention (Unreleased) and refer to the SNAPSHOT version - The RELEASE_NOTES mention .NET 6 being enough for PLC4Net, but it has to be 7 [OK] [RM] Verify the staged source README, RELEASE_NOTE files correspond to those in the extracted source bundle. [OK] [RM] Run RAT externally to ensure there are no surprises. [OK] Search for SNAPSHOT references [OK] Search for Copyright references, and if they are in headers, make sure these files containing them are mentioned in the LICENSE file. [MAJOR] Build the project according to the information in the README.md file. - Currently both the "docker compose up“ as well as the „./mvnw -P with-java install“ builds fail, as they require artifacts that are only built if „update-generated-code“ is enabled. However, this will only fail until this release has passed and the maven artifacts are released. I have already updated the build on `develop` to no longer have this issue in the future. For now, simply running „./mvnw -P with-java,update-generated-code install“ is enough to make it work. Unfortunately, there seem to have been other issues released to JUnit 5 that I didn’t have when running in IntelliJ that caused issues on the command line. Luckily creating a new release is now super simple. I’ll probably even delete the old branch and re-do the entire process, so I can do a recording of the process. Von: Christofer Dutz <[email protected]> Datum: Freitag, 1. August 2025 um 11:40 An: [email protected] <[email protected]> Betreff: [VOTE] Apache PLC4X 0.13.0 rc1 Apache PLC4X 0.13.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. Release tag: v0.13.0 Hash for the release tag: 721c1aa4987d21a9cd8bb5049cb8a70eb06de3fb 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-1058 [2] https://dist.apache.org/repos/dist/dev/plc4x/0.13.0/rc1 [3] https://www.apache.org/dev/release.html#approving-a-release [4] https://plc4x.apache.org/plc4x/latest/developers/release/validation.html
