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

[Anthony Baker <ab...@pivotal.io>]

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 <ab...@pivotal.io> wrote:
> 
> Great job everyone on releasing 1.1.0!  Let’s get organized for the next release :-)
> 
> Scope:
> 	We definitely need to focus on eliminating JSON.org prior to 4/31.  See GEODE-629, GEODE-2142, GEODE-2331, GEODE-2380.
> 	Anything else?
> 
> Timing:
> 	I suggest shooting for a release candidate around mid-March if possible (release often!)
> 
> Release Manager:
> 	Any volunteers?
> 
> Note:  as a process reminder please don’t set Fix Version in JIRA unless you fix a bug that has been merged to develop or the issue has been prioritized by the community for inclusion in a release.
> 
> Thanks,
> Anthony
> 

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

[Hitesh Khamesra <hi...@yahoo.com.INVALID>]

I would prefer to consider GEODE-2413 as well.
-Hitesh
      From: Anthony Baker <ab...@pivotal.io>
 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 / timing / release manager?

Anthony

> On Feb 16, 2017, at 8:20 AM, Anthony Baker <ab...@pivotal.io> wrote:
> 
> Great job everyone on releasing 1.1.0!  Let’s get organized for the next release :-)
> 
> Scope:
>     We definitely need to focus on eliminating JSON.org prior to 4/31.  See GEODE-629, GEODE-2142, GEODE-2331, GEODE-2380.
>     Anything else?
> 
> Timing:
>     I suggest shooting for a release candidate around mid-March if possible (release often!)
> 
> Release Manager:
>     Any volunteers?
> 
> Note:  as a process reminder please don’t set Fix Version in JIRA unless you fix a bug that has been merged to develop or the issue has been prioritized by the community for inclusion in a release.
> 
> Thanks,
> Anthony
>