GEODE-2413 : Implementing a peer-to-peer protocol for mutual auth require some 
more investigation. Apart from that, we need to support backward compatibility 
as well.  Considering the complexity of the issue, would it make sense to move 
that out of 1.1.0 release?

Thoughts?

 

      From: Hitesh Khamesra <hitesh...@yahoo.com.INVALID>
 To: "dev@geode.apache.org" <dev@geode.apache.org> 
 Sent: Thursday, February 2, 2017 10:33 AM
 Subject: Re: [DISCUSS] Release branch for 1.1.0
   
We want to fix one more issue in this release
 GEODE-2413 peer-to-peer authentication: Peer need to re-authenticate 
coordinator while accepting view message 

GEODE-2386    Unable to launch dunit VMs in nightly builds
>>IMO, we can move forward with 1.1.0 since these failures seem to be related 
>>to the Jenkins environment.  Thoughts?
+1

Thanks.Hitesh



      From: Anthony Baker <aba...@pivotal.io>
 To: dev@geode.apache.org 
 Sent: Thursday, February 2, 2017 9:16 AM
 Subject: Re: [DISCUSS] Release branch for 1.1.0
  
Looks like the tests are failing even with your changes.  They pass for me when 
run locally.  Perhaps it’s time to look into dockerizing the jenkins 
environment.

IMO, we can move forward with 1.1.0 since these failures seem to be related to 
the Jenkins environment.  Thoughts?

Anthony

> On Feb 1, 2017, at 2:34 PM, Dan Smith <dsm...@pivotal.io> wrote:
> 
> I checked in what I hope is a workaround for GEODE-2386. We'll see what
> happens when the nightly build runs. It doesn't seem to reproduce in other
> environments.
> 
> -Dan
> 
> On Wed, Feb 1, 2017 at 1:34 PM, Anthony Baker <aba...@pivotal.io> wrote:
> 
>> If it doesn’t need to be fixed in 1.1.0, please unset the ‘Fix Version’ in
>> JIRA.
>> 
>> Thanks,
>> Anthony
>> 
>> 
>>> On Feb 1, 2017, at 9:53 AM, Kevin Duling <kdul...@pivotal.io> wrote:
>>> 
>>> GEODE-2247 GFSH over HTTP succeeds without authentication
>>> 
>>> The title for this is a little misleading.  Yes, it succeeds, but with an
>>> 'anonymous' and unprivileged user.  That could be a valid use-case.  For
>>> example, dev rest does not require a login to execute a ping.
>>> 
>>> I hope to have it resolved today, but in my opinion, it's not critical
>>> enough to hold up a release.
>>> 
>>> On Wed, Feb 1, 2017 at 9:46 AM, Anthony Baker <aba...@pivotal.io> wrote:
>>> 
>>>> While we’re finalizing the last fixes, let’s crowd-source the release
>>>> notes.  These will be linked from the releases page on the website and
>>>> included in the ANNOUNCE email.  You can edit the release notes here:
>>>> 
>>>> https://cwiki.apache.org/confluence/display/GEODE/Release+Notes
>>>> 
>>>> Thanks,
>>>> Anthony
>>>> 
>>>>> On Jan 31, 2017, at 3:40 PM, Hitesh Khamesra
>> <hitesh...@yahoo.com.INVALID>
>>>> wrote:
>>>>> 
>>>>> Update: We are waiting for two more fixes.
>>>>> GEODE-2386 Unable to launch dunit VMs in nightly builds
>>>>> GEODE-2247 GFSH over HTTP succeeds without authentication
>>>>> Thanks,Hitesh
>>>>> 
>>>>> 
>>>>>    From: Hitesh Khamesra <hitesh...@yahoo.com.INVALID>
>>>>> To: "dev@geode.apache.org" <dev@geode.apache.org>
>>>>> Sent: Monday, January 30, 2017 2:55 PM
>>>>> Subject: Re: [DISCUSS] Release branch for 1.1.0
>>>>> 
>>>>> Thanks Bruce. There is one more ticket GEODE-2386, which Kirk is
>> looking
>>>> into it.
>>>>> -Hitesh
>>>>> 
>>>>> 
>>>>>    From: Bruce Schuchardt <bschucha...@pivotal.io>
>>>>> To: dev@geode.apache.org
>>>>> Sent: Monday, January 30, 2017 2:21 PM
>>>>> Subject: Re: [DISCUSS] Release branch for 1.1.0
>>>>> 
>>>>> I'm done merging these two changes to release/1.1.0
>>>>> 
>>>>> Le 1/30/2017 à 10:58 AM, Hitesh Khamesra a écrit :
>>>>>> Sure. Lets include GEODE-2368 (Need to fix log message in
>>>> DirectChannel) this as well.
>>>>>> Thanks.Hitesh
>>>>>> 
>>>>>> 
>>>>>>      From: Bruce Schuchardt <bschucha...@pivotal.io>
>>>>>> To: dev@geode.apache.org
>>>>>> Sent: Monday, January 30, 2017 10:37 AM
>>>>>> Subject: Re: [DISCUSS] Release branch for 1.1.0
>>>>>> 
>>>>>> I'd like to merge into 1.1.0 the change to the Host test class that I
>>>>>> checked into develop today.  It's breaking things for some people, so
>> it
>>>>>> would be nice to have in the 1.1.0 branch.
>>>>>> 
>>>>>> Le 1/27/2017 à 11:00 AM, Hitesh Khamesra a écrit :
>>>>>>> I have created the release branch "release/1.1.0". Please look at
>> this
>>>> and raise if there is any issue.
>>>>>>> If there is no concern then we will start voting next week.
>>>>>>> Thanks.Hitesh
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>> 
>>>> 
>> 
>> 


  

   

Reply via email to