+1 (binding) Chris
[OK] Download all staged artifacts under the url specified in the release vote email. [OK] Verify the signature is correct. * Checked for the release bundle as well as the two sbom variants [OK] Check if the signature references an Apache email address. * Checked for the release bundle as well as the two sbom variants [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. [OK] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. [OK] [RM] Verify the staged source README, RELEASE_NOTE files correspond to those in the extracted source bundle. [MINOR] [RM] Run RAT externally to ensure there are no surprises. * It seems that in the nifi integration we have a gitignore file, which should be merged with the root gitignore * There’s one pcap in plc4j/utils/test-generator/src/test/resources/bacnet-stack-services.cap with unclear source * The other pcaps are all created by members of the plc4x team [MINOR] Search for SNAPSHOT references * It seems the release didn’t include the code-generation/tests module (which is completely unessential for any functionality) [OK] Search for Copyright references, and if they are in headers, make sure these files containing them are mentioned in the LICENSE file. [OK] Build the project according to the information in the README.md file. [MINOR] [RM] Build the project with all with-xyz profiles and tests enabled and an empty maven local repo. * Building with docker-compose doesn’t seem to be working as the release didn’t contain the tests modules (requires manual edit of 2 poms) Von: Christofer Dutz <[email protected]> Datum: Montag, 2. Oktober 2023 um 10:28 An: [email protected] <[email protected]> Betreff: [VOTE] Apache PLC4X 0.11.0 RC1 Apache PLC4X 0.11.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.11.0 Hash for the release tag: d22042ef079ae93120770a95704571118d9c871e 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-1050 [2] https://dist.apache.org/repos/dist/dev/plc4x/0.11.0/rc1 [3] https://www.apache.org/dev/release.html#approving-a-release [4] https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
