Ups … now againwith the right title 😉 Von: Christofer Dutz <christofer.d...@c-ware.de> Datum: Montag, 14. April 2025 um 21:04 An: dev@plc4x.apache.org <dev@plc4x.apache.org> Betreff: AW: [VOTE] Apache PLC4X Build-Tools Code-Generation 1.8.0 RC1 Hi all,
so the vote passes with 3 binding +1 and one non binding +1 vote. Binding: * Christofer * Likas * Sebastian Non-Binding: * Jinlin I’ll release the artifacts and update the main repo to use the released version. Chris Von: Jinlin Hong <myhongjin...@gmail.com> Datum: Sonntag, 13. April 2025 um 14:57 An: dev@plc4x.apache.org <dev@plc4x.apache.org> Betreff: Re: [VOTE] Apache PLC4X Build-Tools Code-Generation 1.8.0 RC1 +1 (binding) Jinlin Hong [OK] Download all staged artifacts under the url specified in the release vote email. [MINOR] Verify the signature is correct.(Can not install key server flow the document "gpg --keyserver pgpkeys.mit.edu --recv-key DE885DD3 gpg: failed to receive from public key server: No key server available") [MINOR] 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 [] 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. [] [RM] Build the project with all with-xyz profiles and tests enabled and an empty maven local repo. <ott.lu...@murena.io.invalid> 於 2025年4月13日 週日 下午3:54寫道： > +1 (binding) > Lukas > > [X] Download all staged artifacts under the url specified in the release > vote email. > [X] Verify the signature is correct. > [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] Build the project according to the information in the README.md file. > [X] [RM] Build the project in an empty maven local repo. > > Small remark the 2 links end up in 404: > [3] https://www.apache.org/dev/release/validation.html#approving-a-release > > > [4] https://plc4x.apache.org/developers/release/validation.html -> Should > be > https://plc4x.apache.org/plc4x/latest/developers/release/validation.html > > Additional helpful link: > https://apache.org/info/verification.html > > > > Am 11. April 2025 um 18:29 schrieb "Christofer Dutz" < > christofer.d...@c-ware.de>: > > > > > > > Apache PLC4X Build-Tools Code-Generation 1.8.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.8.0 > > Hash for the release tag: 24a3a98af739eae35dbdc2d1e7d7bacbb4d9312d > > > > 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-1055 > > [2] > https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-generation/1.8.0/rc1/ > > [3] > https://www.apache.org/dev/release/validation.html#approving-a-release > > [4] https://plc4x.apache.org/developers/release/validation.html > >
