Shamelessly copying Tim's email ... but I did all the checking. +1 Binding
All checks performed: * Checked out using the new tooling: OK * Checked signatures: OK * Checked the zip correctly unpacks to the expected directory structure: OK * verify the existence of DISCLAIMER, LICENSE, NOTICE, README, RELEASE_NOTES: OK * Checked the contents of DISCLAIMER, LICENSE, NOTICE, README, RELEASE_NOTES: OK * Built from sources (including tests) according to instructions in README: OK * All tests pass: OK Chris Am 05.03.19, 14:24 schrieb "Tim Mitsch" <[email protected]>: +1 (binding) All checks performed: * Checked out using the new tooling: OK * Checked signatures: OK * Checked the zip correctly unpacks to the expected directory structure: OK * verify the existence of DISCLAIMER, LICENSE, NOTICE, README, RELEASE_NOTES: OK * Checked the contents of DISCLAIMER, LICENSE, NOTICE, README, RELEASE_NOTES: OK * Built from sources (including tests) according to instructions in README: OK * All tests pass: OK I encountered the following issue that should be no problem: ---------------- gpg: Korrekte Signatur von "Julian Feinauer <[email protected]>" [unbekannt] gpg: alias "[jpeg image of size 8797]" [unbekannt] gpg: WARNUNG: Dieser Schlüssel trägt keine vertrauenswürdige Signatur! gpg: Es gibt keinen Hinweis, daß die Signatur wirklich dem vorgeblichen Besitzer gehört. Haupt-Fingerabdruck = ADBD 428C B5BF 6C9F FC77 B907 C336 E014 3A55 3B89 ----------------- Best Tim Am 05.03.19, 12:29 schrieb "Julian Feinauer" <[email protected]>: +1 (binding) Checks performed: - Checked out using the new tooling: OK - Checked signatures: OK - [RM] Checked signature is from a valid Apache signature referencing a valid Apache-Email address: OK gpg: Korrekte Signatur von "Julian Feinauer <[email protected]>" [ultimativ] - Checked the zip correctly unpacks to the expected directory structure: OK - [RM] Checked the "incubating" in the name of the artifacts: OK - verify the existence of DISCLAIMER, LICENSE, NOTICE, README, RELEASE_NOTES: OK - [RM] Check the RC README and RELEASE_NOTES matches that of the source bundle: OK - Checked the contents of DISCLAIMER, LICENSE, NOTICE, README, RELEASE_NOTES: OK - Built from sources (including tests) according to instructions in README: OK . [RM] Check content of rat.txt: OK (Site images and PCAP(NG) files are only binaries) - All tests pass: OK Best Julian Am 05.03.19, 12:11 schrieb "Julian Feinauer" <[email protected]>: Apache PLC4X (Incubating) 0.3.1 has been staged under [2] and it’s time to vote on accepting it for release. All Maven artifacts are available under [1]. If approved we will seek final release approval from the IPMC. 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.3.1 Hash for the release tag: 7852b6d78a2b4c36ecf0f7c902816131e339adff Per [3] "Before voting +1 [P]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-1008 [2] https://dist.apache.org/repos/dist/dev/incubator/plc4x/0.3.1-incubating/rc1 [3] https://www.apache.org/dev/release.html#approving-a-release [4] https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
