+1 (binding)

Built on Mac OS 13.5.2 with Apple M2 Max using Java 11.0.20 (Amazon Coretto 
Build)

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.
[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 <christofer.d...@c-ware.de>
Datum: Freitag, 22. September 2023 um 13:20
An: dev@plc4x.apache.org <dev@plc4x.apache.org>
Betreff: [VOTE] Apache PLC4X Build-Tools Code-Generation 1.7.0 RC1
Apache PLC4X Build-Tools Code-Generation 1.7.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.

   Repository: https://gitbox.apache.org/repos/asf/plc4x-build-tools.git
   Release tag: releases/code-generation/1.7.0
   Hash for the release tag: 43b93a139c9580325c26082e7272fc224238355f

   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-1049
   [2] 
https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-generation/1.7.0/rc1/
   [3] https://www.apache.org/dev/release/validation.html#approving-a-release
   [4] https://plc4x.apache.org/developers/release/validation.html

Reply via email to