I’ve started another geode-release build but my confidence in jenkins test results is pretty low. The last successful nightly build was almost 6 weeks ago.
Anthony > On Sep 13, 2017, at 10:22 AM, Dan Smith <dsm...@pivotal.io> wrote: > > The jenkins build had failures for this revision. They look like they might > be environmental issues but I don't think we should actually ship this > unless we have a green build. Can someone kick the pipeline to restart the > build? > > https://builds.apache.org/blue/organizations/jenkins/Geode-release/detail/Geode-release/88/tests > > On Mon, Sep 11, 2017 at 2:03 PM, Anthony Baker <aba...@apache.org> wrote: > >> This is the third release candidate for Apache Geode, version 1.2.1. >> Thanks to all the community members for their contributions to this >> release! >> >> *** Please download, test and vote by Thursday, September 14, 1200 hrs >> US Pacific. *** >> >> It fixes the following issues: >> https://issues.apache.org/jira/secure/ReleaseNote.jspa? >> projectId=12318420&version=12341124 >> >> Note that we are voting upon the source tags: rel/v1.2.1.RC3 >> https://github.com/apache/geode/tree/rel/v1.2.1.RC3 >> https://github.com/apache/geode-examples/tree/rel/v1.2.1.RC3 >> >> Commit ID: >> 0b881b515eb1dcea974f0f5c1b40da03d42af9cf (geode) >> 5d034de588a43cdefb8fbb3a6259579785768340 (geode-examples) >> >> Source and binary files: >> https://dist.apache.org/repos/dist/dev/geode/1.2.1.RC3 >> >> Maven staging repo: >> https://repository.apache.org/content/repositories/orgapachegeode-1023 >> >> Geode's KEYS file containing PGP keys we use to sign the release: >> https://github.com/apache/geode/blob/develop/KEYS >> >> pub 4096R/C72CFB64 2015-10-01 >> Fingerprint=948E 8234 14BE 693A 7F74 ABBE 19DB CAEE C72C FB64 >> >> >> Anthony >>
