+1 (binding) Run on Windows 10 Professional x64 with Java: openjdk 11.0.9.1 2020-11-04 LTS OpenJDK Runtime Environment 18.9 (build 11.0.9.1+1-LTS) OpenJDK 64-Bit Server VM 18.9 (build 11.0.9.1+1-LTS, mixed mode)
[OK] Download all staged artifacts under the url specified in the release vote email [MINOR] 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] 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 [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 The next time we all meet, we should do the key signing to get rid of not being able to "trust" the signature. -----Ursprüngliche Nachricht----- Von: Otto Fowler <[email protected]> Gesendet: Montag, 14. Dezember 2020 16:04 An: [email protected] Betreff: Re: [VOTE] Apache PLC4X Build-Tools Code-Generation 1.4.0 RC2 +1 binding java version "1.8.0_171" Java(TM) SE Runtime Environment (build 1.8.0_171-b11) Java HotSpot(TM) 64-Bit Server VM (build 25.171-b11, mixed mode) > On Dec 13, 2020, at 10:52, Lukas Ott <[email protected]> wrote: > > Apache PLC4X Build-Tools Code-Generation 1.4.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.4.0 > Hash for the release tag: {replacethiswiththerealgitcommittag} > > 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-{somefourdigitnumber} > [2] > https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-generation/1.4.0/rc2/ > [3] > https://www.apache.org/dev/release/validation.html#approving-a-release > [4] https://plc4x.apache.org/developers/release/validation.html
