+1 (binding) Sebastian Rühl
[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] Search for SNAPSHOT references: Only found some in the dummy website copy in the integration-tests [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. On 2021/09/18 16:15:34, Christofer Dutz <christofer.d...@c-ware.de> wrote: > Apache PLC4X 0.9.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.9.0 > > Hash for the release tag: e9e9a58b057d7df827463f1262ded3a34015666a > > > > 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-1038 > > [2] https://dist.apache.org/repos/dist/dev/plc4x/0.9.0/rc2 > > [3] https://www.apache.org/dev/release.html#approving-a-release > > [4] > https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release > >
