+1 binding Chris
[OK] Download all staged artifacts under the url specified in the release vote email into a directory we’ll now call download-dir: [OK] Verify the signature is correct. [OK] Check if the check is successful. [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] 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: by appendng -Dmaven.repo.local=../.m2. Am 26.02.20, 13:34 schrieb "Julian Feinauer" <[email protected]>: Hey folks, its release time again! As discussed on multiple occasions, the 0.6 release branch will be a „LTS“ release of the „old fashioned“ or „hand written“ drivers. The develop will be the 0.7.0 branch and will contain the generated drivers. Please check the RELEASE_NOTES for all details. --- Thanks for Justin, Chris and Dominik for finding issues with RC2 and helping fix them. ---- Apache PLC4X 0.6.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: release/0.6.0 Hash for the release tag: d58c4d5828a3528199584ed51a65d7c896ae1e86 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-1023 [2] https://dist.apache.org/repos/dist/dev/plc4x/0.6.0/rc3 [3] https://www.apache.org/dev/release.html#approving-a-release [4] https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
