+1 (binding) sruehl 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. [OK] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. [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. [OK] Build the project according to the information in the README.md file. On 2026/09/04 08:14:20 Christofer Dutz wrote: > +1 (binding) cdutz > > 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. > > * > Minor inconsistencies, which I have already fixed on develop, but shouldn’t > cause any problems with users. (Referencing maven 4 rc6 instead of rc5, we no > longer need GraphViz for building the website, Scala is not needed, Dotnet 7 > instead of 4.5.2) > > [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. > [OK] Build the project according to the information in the README.md file. > [OK] [RM] Build the project with all with-xyz profiles and tests enabled and > an empty maven local repo. > > > > Von: Christofer Dutz <[email protected]> > Datum: Freitag, 4. September 2026 um 00:34 > An: [email protected] <[email protected]> > Betreff: [VOTE] Apache PLC4X 1.0.0 rc1 > > Apache PLC4X 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: ea229918f5d07700e04d7d69ab1645da679cb700 > > 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-1065 > [2] https://dist.apache.org/repos/dist/dev/plc4x/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 >
