Hi, thanks for doing the release Chris and a special thank to all non-PMC Voters!! As some of you may know, voting is a very important duty in the project (as in every democracy...) and everybody's vote is highly welcomed.
So a special thank once again to Lukas and Volker! Julian Am 02.11.19, 16:09 schrieb "Christofer Dutz" <[email protected]>: Hi all, so the vote passes with 6 binding +1, 2 non-binding +1, no 0 and no -1 Thanks for voting :-) Chris Am 31.10.19, 15:35 schrieb "Tim Mitsch" <[email protected]>: Hey everybody, +1 (binding) I checked: - Checked out using tooling - Checked Signatures and Hashes - Checked README, RELEASE_NOTES, LICENSE and NOTICE - Checked README and RELEASE_NOTES are same as in the zip - No unexpected binaries Build on all major OS: - MacOS Mojave 10.14.6, with JDK 1.8 using './mvnw -P with-python,with-proxies,with-boost,with-java,with-cpp,with-dotnet install' without any issues - CentOS 7.6.1810, with JDK 1.8 using './mvnw -P with-python,with-proxies,with-boost,with-java,with-cpp,with-dotnet install' without any issues - Built on Windows 10 x86-64 using '.\mvnw.cmd -P with-java -DskipTests install' without any issues Minor issues: - Build on Windows made -DskipTests necessary, due to failing RawSocketChannelTest and the loopback issue, as already stated by Björn and addressed in Jira - '.\mvnw.cmd -P with-python,with-proxies,with-boost,with-java,with-cpp,with-dotnet -DskipTests install' failed due to issues on building thrift, although all WinBuilds tools as described in ReadMe were installed, but this may be related to setup of my Win-VM Best Tim Am 29.10.19, 14:04 schrieb "Christofer Dutz" <[email protected]>: Apache PLC4X 0.5.0 RC3 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.5.0-rc3 Hash for the release tag: 59cd9d3839dcb6083350144802142360182c59c1 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-1018 [2] https://dist.apache.org/repos/dist/dev/plc4x/0.5.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
