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 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 < >

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

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

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

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

Re: [VOTE] Apache Geode 1.6.0 RC1

Deleted my local copy of ‘rel/v1.6.0.RC1’ and refetched. The tag now correctly points to this commit: 5ce726bd7 With that change, I’ll vote +1. Aside on voting: for releases a -1 doesn’t automatically veto the release candidate [1]. It is, however, a strong signal that the community may

Re: [VOTE] Apache Geode 1.6.0 RC1

Thanks for catching that tag error Anthony. I fixed it to have the SHA matching the build. If you're good with this could you change your -1 to a +1 so the vote can continue? On Thu, Apr 26, 2018 at 2:05 PM, Mike Stolz wrote: > This is the first release candidate for

Re: [VOTE] Apache Geode 1.6.0 RC1

- checked signatures - checked hashes - build from source - ran examples The tag for the geode repo differs from the source and binary release archives: ~/working/apache-geode-1.6.0$ bin/gfsh version --full Build-Date: 2018-04-23 14:04:21 -0400 Build-Id: mikestolz 0 Build-Java-Version: 1.8.0_151

Re: [VOTE] Apache Geode 1.6.0 RC1

Yeah, looks like a copy and paste issue that caused the link to get wrapped to a new line. Sorry. -- Mike Stolz Principal Engineer, GemFire Product Lead Mobile: +1-631-835-4771 Download the GemFire book here. On Thu,

Re: [VOTE] Apache Geode 1.6.0 RC1

Here is the correct link to the Release notes: https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.6.0 On Thu, Apr 26, 2018 at 2:13 PM, Diane Hardman wrote: > The link to the Release notes seems to be incorrect. > > > > On Thu, Apr 26, 2018 at

Re: [VOTE] Apache Geode 1.6.0 RC1

The link to the Release notes seems to be incorrect. On Thu, Apr 26, 2018 at 11:05 AM, Mike Stolz wrote: > This is the first release candidate for Apache Geode, version 1.6.0. > Thanks to all the community members for their contributions to this > release! > > *** Please

[VOTE] Apache Geode 1.6.0 RC1

This is the first release candidate for Apache Geode, version 1.6.0. Thanks to all the community members for their contributions to this release! *** Please download, test and vote by Monday, April 30, 1500 hrs US Pacific. *** It fixes 157 issues. Release notes can be found at: