The build and check-all scripts were successful for me. I had trouble with the integration tests. Looks like `./samza-test/src/main/python/configs/tests.json` needs to be updated s.t. '"samza_executable": "samza-test_2.11-0.12.0.tgz"'
After that, the integration tests were successful. Also, reminder for folks to kill any running Kafka and Yarn processes before running the integration test each time: https://issues.apache.org/jira/browse/SAMZA-511 On Wed, Feb 1, 2017 at 4:53 PM, Jagadish Venkatraman <jagadish1...@gmail.com > wrote: > This is a call for a vote on a release of Apache Samza 0.12.0. Thanks to > everyone who has contributed to this release. We are very glad to see some > new contributors in this release. > > The release candidate can be downloaded from here: > http://home.apache.org/~jagadish/samza-0.12.0-rc0/ > > The release candidate is signed with pgp key AF81FFBF, which can be found > on keyservers: > http://pgp.mit.edu/pks/lookup?op=get&search=0xAF81FFBF > > The git tag is release-0.12.0-rc0 and signed with the same pgp key: > https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h= > refs/tags/release-0.12.0-rc0 > > Test binaries have been published to Maven's staging repository, and are > available here: > https://repository.apache.org/content/repositories/orgapachesamza-1016 > > Note that the binaries were built with JDK8 without incident. > > 26 issues were resolved for this release: > https://issues.apache.org/jira/issues/?jql=project%20% > 3D%20SAMZA%20AND%20fixVersion%20in%20(0.12%2C%200.12.0)% > 20AND%20status%20in%20(Resolved%2C%20Closed) > > The vote will be open for 72 hours (end in 5:00pm Saturday, 02/04/2017 ). > > Please download the release candidate, check the hashes/signature, build it > and test it, and then please vote: > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > +1 from my side for the release. > > Cheers! > > -- > Jagadish V, > Graduate Student, > Department of Computer Science, > Stanford University >
