[ANNOUNCE] Apache Geode 1.6.0

2018-05-04 Thread Mike Stolz
The Apache Geode community is pleased to announce the availability of Apache Geode 1.6.0. Apache Geode is a data management platform that provides a database-like consistency model, reliable transaction processing and a shared-nothing architecture to maintain very low latency performance

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

2018-05-01 Thread Anthony Baker
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

2018-05-01 Thread Mike Stolz
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

2018-05-01 Thread Swapnil Bawaskar
+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

2018-05-01 Thread Dan Smith
+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

2018-05-01 Thread Anthony Baker
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

2018-05-01 Thread Galen O'Sullivan
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

2018-05-01 Thread Anthony Baker
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

2018-04-30 Thread Anthony Baker
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

2018-04-30 Thread Galen O'Sullivan
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

2018-04-30 Thread Anthony Baker
;> 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

2018-04-27 Thread Mike Stolz
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

2018-04-27 Thread Anthony Baker
- 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

2018-04-26 Thread Michael Stolz
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

2018-04-26 Thread Diane Hardman
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

2018-04-26 Thread Diane Hardman
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

2018-04-26 Thread Mike Stolz
(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

2018-04-23 Thread Swapnil Bawaskar
+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

2018-04-23 Thread Michael Stolz
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.

Re: Geode 1.6.0

2018-04-17 Thread Anthony Baker
Thanks Mike. As a first-time release manager, you’ll need to add your key to the following locations: https://id.apache.org (add the fingerprint to your profile) https://github.com/apache/geode/blob/develop/KEYS https://dist.apache.org/repos/dist/release/geode/KEYS https://dist.apache.org/repos/

Re: Geode 1.6.0 release branch has been created

2018-04-13 Thread Karen Miller
Mike, I've just cherry picked commit SHA1 ac7db5b2950af134233c976b3f63f3e48e8d3fb9 onto the release/1.6.0 branch. This commit updates the documentation for GEODE-4384. This JIRA ticket already had its code committed prior to creation of the release branch, but the JIRA ticket was still unresolved

Re: Geode 1.6.0 release branch has been created

2018-04-13 Thread Sean Goller
The corresponding pipeline has been created: https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.6.0 On Thu, Apr 12, 2018 at 3:03 PM, Michael Stolz wrote: > Can someone please create a concourse pipeline for this release? > > > -- > Mike Stolz >

Geode 1.6.0 release branch has been created

2018-04-12 Thread Michael Stolz
Can someone please create a concourse pipeline for this release? -- Mike Stolz

Re: Geode 1.6.0

2018-04-11 Thread Alexander Murmann
Hi Mike, Thanks for taking on the release manager role! 👏 You mention some minor issues. Do you mind sharing the ticket numbers? I think it would be great if we all as a community could get a shared understanding of what and why we are adding. Thanks! On Wed, Apr 11, 2018 at 4:34 PM, Michael St

Geode 1.6.0

2018-04-11 Thread Michael Stolz
Hi, We are going to cut a release branch for 1.6.0 soon. Probably today or tomorrow. This is in keeping with our desire to get onto a monthly release cycle. The Geode pipeline is green, so will not be an impediment to cutting this branch. There are a couple of minor issues that we might squeeze