+1 (binding) sebastian
[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. - RELEASE_NOTES lists 1.0.0 as (Unreleased) [OK] Verify the staged source README, RELEASE_NOTE files correspond to those in the extracted source bundle. [OK] Run RAT externally to ensure there are no surprises. [MINOR] Search for SNAPSHOT references - 1.0.0-SNAPSHOT appears in labels of go utils (plc4xbrowser and ui) - 1.0.0-SNAPSHOT appears in disabled example "plc4j-s7event" [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. On 2026/09/23 14:47:48 Christofer Dutz via dev wrote: > +1 (binding) > > cdutz > > [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. > - RELEASE_NOTES lists 1.0.0 as (Unreleased) > [OK] Verify the staged source README, RELEASE_NOTE files correspond to those > in the extracted source bundle. > [OK] Run RAT externally to ensure there are no surprises. > [MINOR] Search for SNAPSHOT references > - 1.0.0-SNAPSHOT appears in labels of go utils (plc4xbrowser and ui) > - 1.0.0-SNAPSHOT appears in disabled example "plc4j-s7event" > [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. > > > > > QuanticPony via dev <[email protected]> schrieb am Dienstag, 22. September > 2026 um 21:58: > > > 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 > > > > > > >
