Re: 1.1.0 is done so let's start work on 1.2.0

2017-03-20 Thread Karen Miller
It'd be great to get the partitioning example merged in and make the geode-examples part of the 1.2.0 release. Everyone take a look at the revised PR: https://github.com/apache/geode-examples/pull/3 On Mon, Mar 20, 2017 at 3:54 PM, Udo Kohlmeyer wrote: > Are there any issues that we can think

Re: 1.1.0 is done so let's start work on 1.2.0

2017-03-20 Thread Udo Kohlmeyer
Are there any issues that we can think of that we would want to include into 1.2.0? I see no reason to wait. Why not start the process today? --Udo On 3/20/17 15:36, Anthony Baker wrote: Returning to this question: we’ve fixed 119 issues since we released 1.1.0 in February. I’d like to do

Re: 1.1.0 is done so let's start work on 1.2.0

2017-03-20 Thread Anthony Baker
Returning to this question: we’ve fixed 119 issues since we released 1.1.0 in February. I’d like to do an early April release of 1.2.0 so we can be done with the JSON.org license issue in plenty of time. Let’s plan to create a release candidate one week from today on 3/27.

Re: 1.1.0 is done so let's start work on 1.2.0

2017-03-01 Thread Hitesh Khamesra
I would prefer to consider GEODE-2413 as well. -Hitesh From: Anthony Baker To: dev@geode.apache.org Sent: Wednesday, March 1, 2017 1:21 PM Subject: Re: 1.1.0 is done so let's start work on 1.2.0 bump The json.org removal is complete.  Any thoughts on additional scope / t

Re: 1.1.0 is done so let's start work on 1.2.0

2017-03-01 Thread Anthony Baker
bump The json.org removal is complete. Any thoughts on additional scope / timing / release manager? Anthony > On Feb 16, 2017, at 8:20 AM, Anthony Baker wrote: > > Great job everyone on releasing 1.1.0! Let’s get organized for the next > release :-) > > Scope: > We definitely need t