Re: [RESULT][VOTE] Apache Geode 1.6.0.RC1

Reminder on release voting requirements [1]: - Must have 3 binding (PMC) +1 votes - Must have a majority of +1 votes In this case Galen, Dan, Swapnil, and myself are members of the Geode PMC. All votes are "binding". Anthony [1] https://www.apache.org/foundation/voting.html

[RESULT][VOTE] Apache Geode 1.6.0.RC1

This vote passes with three +1 votes and one +0 and zero -1 votes. Summary: Anthony Baker +1 Galen O'Sullivan +0 Dan Smith +1 Swapnil Bawaskar +1

Re: [VOTE] Apache Geode 1.6.0 RC1

+1 On Tue, May 1, 2018 at 2:19 PM Dan Smith wrote: > +1 > > Ran geode-release-check, looks good to me. > > -Dan > > On Tue, May 1, 2018 at 11:55 AM, Anthony Baker wrote: > > > Ok, thanks Galen. AFAICT, the KEYS file being referred to is this one: > > https://dist.apache.org/repos/dist/release/

Re: [VOTE] Apache Geode 1.6.0 RC1

+1 Ran geode-release-check, looks good to me. -Dan On Tue, May 1, 2018 at 11:55 AM, Anthony Baker wrote: > Ok, thanks Galen. AFAICT, the KEYS file being referred to is this one: > https://dist.apache.org/repos/dist/release/geode/KEYS < > https://dist.apache.org/repos/dist/release/geode/KEYS>.

Re: [VOTE] Apache Geode 1.6.0 RC1

Ok, thanks Galen. AFAICT, the KEYS file being referred to is this one: https://dist.apache.org/repos/dist/release/geode/KEYS . Other Apache projects like Flink, Beam, Impala, or Kafka don’t version control their KEYS file. @PMC - we need

Re: [VOTE] Apache Geode 1.6.0 RC1

Thanks for the clarification, Anthony. The release signing page you linked does say this: > Since the KEYS may be needed to check signatures for archived releases, it is important that all keys that have ever been used to sign releases are retained in the file. Entries should only be added (as

Re: [VOTE] Apache Geode 1.6.0 RC1

Galen, Given the above information what are your thoughts? Anthony > On Apr 30, 2018, at 3:01 PM, Anthony Baker wrote: > > Please review the ASF policy on signing releases [1]. I think these points > are pertinent: > > - The release manager signs the release. That provides the verificati

Re: [VOTE] Apache Geode 1.6.0 RC1

Please review the ASF policy on signing releases [1]. I think these points are pertinent: - The release manager signs the release. That provides the verification that the release binaries were in fact created by the release manager and have not been modified. Multiple signatures are not requ

Re: [VOTE] Apache Geode 1.6.0 RC1

ps://dist.apache.org/repos/dist/dev/geode/1.6.0.RC1 Maven staging repo: https://repository.apache.org/content/repositories/orgapachegeode-1041 Geode's KEYS file containing PGP keys we use to sign the release: https://github.com/apache/geode/blob/develop/KEYS Release Signed with Fingerprin

Re: [VOTE] Apache Geode 1.6.0 RC1

;> b4ba77f5131018d36b79608ef007dd3cbd761cd9 (geode) >> 45d174a1280e539108341b286ff79938f9729bc7 (geode-examples) >> >> Source and binary files: >> https://dist.apache.org/repos/dist/dev/geode/1.6.0.RC1 >> >> Maven staging repo: >> https://repository.apa

Re: [VOTE] Apache Geode 1.6.0 RC1

ID: > b4ba77f5131018d36b79608ef007dd3cbd761cd9 (geode) > 45d174a1280e539108341b286ff79938f9729bc7 (geode-examples) > > Source and binary files: > https://dist.apache.org/repos/dist/dev/geode/1.6.0.RC1 > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachegeode-1041 >

Re: [VOTE] Apache Geode 1.6.0 RC1

s://github.com/apache/geode/tree/rel/v1.6.0.RC1 > https://github.com/apache/geode-examples/tree/rel/v1.6.0.RC1 > > Commit ID: > b4ba77f5131018d36b79608ef007dd3cbd761cd9 (geode) > 45d174a1280e539108341b286ff79938f9729bc7 (geode-examples) > > Source and binary files: > https://

Re: [VOTE] Apache Geode 1.6.0 RC1

gt;> Commit ID: > >> b4ba77f5131018d36b79608ef007dd3cbd761cd9 (geode) > >> 45d174a1280e539108341b286ff79938f9729bc7 (geode-examples) > >> > >> Source and binary files: > >> https://dist.apache.org/repos/dist/dev/geode/1.6.0.RC1 > >> > &g

Re: [VOTE] Apache Geode 1.6.0 RC1

tree/rel/v1.6.0.RC1 >> https://github.com/apache/geode-examples/tree/rel/v1.6.0.RC1 >> >> Commit ID: >> b4ba77f5131018d36b79608ef007dd3cbd761cd9 (geode) >> 45d174a1280e539108341b286ff79938f9729bc7 (geode-examples) >> >> Source and binary files: >> https

Re: [VOTE] Apache Geode 1.6.0 RC1

t; https://github.com/apache/geode/tree/rel/v1.6.0.RC1 > https://github.com/apache/geode-examples/tree/rel/v1.6.0.RC1 > > Commit ID: > b4ba77f5131018d36b79608ef007dd3cbd761cd9 (geode) > 45d174a1280e539108341b286ff79938f9729bc7 (geode-examples) > > Source and binary files: > h

[VOTE] Apache Geode 1.6.0 RC1

(geode) 45d174a1280e539108341b286ff79938f9729bc7 (geode-examples) Source and binary files: https://dist.apache.org/repos/dist/dev/geode/1.6.0.RC1 Maven staging repo: https://repository.apache.org/content/repositories/orgapachegeode-1041 Geode's KEYS file containing PGP keys we use to sig

Re: [gemfire-pm] Geode 1.6.0 RC1

+1 On Mon, Apr 23, 2018 at 9:30 AM Michael Stolz wrote: > The concourse pipeline is green. > Can I go ahead and start the build for RC1? > > -- > Mike Stolz > Principal Engineer, GemFire Product Lead > Mobile: +1-631-835-4771 <(631)%20835-4771> > Download the GemFire book here. >

Geode 1.6.0 RC1

The concourse pipeline is green. Can I go ahead and start the build for RC1? -- Mike Stolz Principal Engineer, GemFire Product Lead Mobile: +1-631-835-4771 Download the GemFire book here.