+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. [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 repo.
Checked sources and ran into issues while building: https://github.com/apache/plc4x/discussions/2200 Nevertheless there is no objection not to release. (Several additional builds have been performed that where successfull) Am 2. August 2025 um 20:13 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. > [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. > [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. > [MINOR] Build the project according to the information in the README.md file. > > * > It seems that when running with-python and update-code-generation and > enable-all-checks the python generation integration test causes issues > (./mvnw -P > with-c,with-dotnet,with-go,with-java,with-python,update-generated-code,enable-all-checks > install) > > Von: Christofer Dutz <[email protected]> > Datum: Samstag, 2. August 2025 um 16:42 > An: [email protected] <[email protected]> > Betreff: [VOTE] Apache PLC4X 0.13.0 rc2 > > Apache PLC4X 0.13.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.13.0 > Hash for the release tag: 595a4636e993bae59c2db8fe9de476221896c6bf > > 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-1059 > [2] https://dist.apache.org/repos/dist/dev/plc4x/0.13.0/rc2 > [3] https://www.apache.org/dev/release.html#approving-a-release > [4] https://plc4x.apache.org/plc4x/latest/developers/release/validation.html >
