You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Anthony Baker <ab...@pivotal.io> on 2017/02/16 16:20:18 UTC

1.1.0 is done so let's start work on 1.2.0

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

Posted by Karen Miller <km...@pivotal.io>.
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 <uk...@pivotal.io>
wrote:

> 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 an early April release of 1.2.0 so we
>> can be done with the JSON.org <http://json.org/> license issue in plenty
>> of time.  Let’s plan to create a release candidate one week from today on
>> 3/27.  Thoughts?
>>
>> I’m happy to volunteer for release manager unless someone else wants it.
>>
>> 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

Posted by Udo Kohlmeyer <uk...@pivotal.io>.
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\u2019ve fixed 119 issues since we released 1.1.0 in February.  I\u2019d like to do an early April release of 1.2.0 so we can be done with the JSON.org <http://json.org/> license issue in plenty of time.  Let\u2019s plan to create a release candidate one week from today on 3/27.  Thoughts?
>
> I\u2019m happy to volunteer for release manager unless someone else wants it.
>
> Anthony
>
>> On Feb 16, 2017, at 8:20 AM, Anthony Baker <ab...@pivotal.io> wrote:
>>
>> Great job everyone on releasing 1.1.0!  Let\u2019s 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\u2019t 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

Posted by Anthony Baker <ab...@pivotal.io>.
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 <http://json.org/> license issue in plenty of time.  Let’s plan to create a release candidate one week from today on 3/27.  Thoughts?

I’m happy to volunteer for release manager unless someone else wants it.

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

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


   

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

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