+1 (binding) Unai
[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. [MINOR] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. - RELEASE_NOTES title has a (Unreleased) for 1.0.0 [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. [MINOR] Search for SNAPSHOT references - 1.0.0-SNAPSHOT version on plc4j-s7event example [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. On Thursday, September 24th, 2026 at 7:28 AM, ott.lukas.murena.io via dev <[email protected]> wrote: > +1 (binding) > > Lukas > > [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 > > Buld with: ./mvnw -X -P with-c,with-java install > > INFO: Apache Creadur RAT 0.18 (Apache Software Foundation) > ***************************************************** > Summary > ***************************************************** > Generated at: 2026-09-24T07:06:36+02:00 > by Apache Creadur RAT 0.18 (Apache Software Foundation) > > ----------------------------------------------------- > Counters > ----------------------------------------------------- > (Entries starting with '!' exceed the minimum or maximum values) > Approved: 364 A count of approved licenses. > Archives: 0 A count of archive files. > Binaries: 12 A count of binary files. > Document types: 3 A count of distinct document types. > Ignored: 0 A count of ignored files. > License categories: 2 A count of distinct license categories. > License names: 2 A count of distinct license names. > Notices: 6 A count of notice files. > Standards: 369 A count of standard files. > ! Unapproved: 5 A count of unapproved licenses. > Unknown: 5 A count of unknown file types. > > > Am 22. September 2026 um 21:57 schrieb "QuanticPony via dev" > <[email protected] > mailto:[email protected]?to=%22QuanticPony%20via%20dev%22%20%3Cdev%40plc4x.apache.org%3E > >: > > > > > > Apache PLC4X Extras 1.0.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: v1.0.0 > > Hash for the release tag: ed67ec04efe852e6802b6ab1a6a9fd2276956e09 > > > > 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-1068 > > [2] https://dist.apache.org/repos/dist/dev/plc4x/plc4x-extras/1.0.0/rc1 > > [3] https://www.apache.org/dev/release.html#approving-a-release > > [4] https://plc4x.apache.org/plc4x/latest/developers/release/validation.html > >
