+1 (binding) Lukas / otluk [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. [] [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 repo.
[MINOR] Build with "./mvnw -P with-c,with-java install" -> To be updated in the README javac -version javac 21.0.8 java -version openjdk version "21.0.8" 2025-07-15 OpenJDK Runtime Environment (build 21.0.8+9-Ubuntu-0ubuntu124.04.1) OpenJDK 64-Bit Server VM (build 21.0.8+9-Ubuntu-0ubuntu124.04.1, mixed mode, sharing) Am 9. August 2025 um 16:49 schrieb "Christofer Dutz" <[email protected]>: > > +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 „.mvnw“ should be „./mvnw" > [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. > > Von: Christofer Dutz <[email protected]> > Datum: Samstag, 9. August 2025 um 16:37 > An: [email protected] <[email protected]> > Betreff: [VOTE] Apache PLC4X Extras 0.13.0 RC2 > > Apache PLC4X Extras 0.13.0 RC2 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: 8efbbff57fc510c2647fadf6ccfcab09b2000dd8 > > 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-1061 > [2] https://dist.apache.org/repos/dist/dev/plc4x/plc4x-extras/0.13.0/rc2/ > [3] https://www.apache.org/dev/release.html#approving-a-release > [4] > https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release >
