---
Spring Data GemFire > Nightly-ApacheGeode > #1026 was successful.
---
Scheduled
2425 tests in total.
https://build.spring.io/browse/SGF-NAG-1026/
--
Thi
I have resolved GEODE-5254
Dale
> On Aug 31, 2018, at 3:34 PM, Nabarun Nag wrote:
>
> Requesting status update on the following JIRA tickets. These tickets have
> commits into develop against its name but the status is still open /
> unresolved.
>
> GEODE-5600 - [Patrick Rhomberg]
> GEODE-5578
Announcement : The branch for 1.7.0 has been cut. Please from this point
onwards use 1.8.0 as the fixed version for your JIRAs
Regards
Nabarun Nag
On Fri, Aug 31, 2018 at 3:34 PM Nabarun Nag wrote:
> Requesting status update on the following JIRA tickets. These tickets have
> commits into devel
Requesting status update on the following JIRA tickets. These tickets have
commits into develop against its name but the status is still open /
unresolved.
GEODE-5600 - [Patrick Rhomberg]
GEODE-5578 - [Robert Houghton]
GEODE-5492 - [Robert Houghton]
GEODE-5280 - [xiaojian zhou & Biju Kunjummen]
GE
Please continue using 1.7.0 as a fix version in JIRA till the email comes
in that the 1.7.0 release branch has be cut.
Changing the fixed version for the following tickets to 1.7.0 from 1.8.0 as
these fixes will be included in the 1.7.0 release
GEODE-5671
GEODE-5662
GEODE-5660
GEODE-5652
Regards
A new feature of get/set cluster config was added as new feature to gfsh.
This needs to be added to the documentation.
Once this is done, the branch will be ready.
Regards
Nabarun
On Fri, Aug 31, 2018 at 2:15 PM Alexander Murmann
wrote:
> Nabarun, do you still see anything blocking cutting the
Nabarun, do you still see anything blocking cutting the release at this
point?
Maybe we can even get a pipeline going today? 😳
On Fri, Aug 31, 2018 at 10:38 AM, Sai Boorlagadda wrote:
> We can go ahead and cut 1.7 with out GEODE-5338 as I don't have the code
> ready.
>
> GEODE-5594, adds a new
We can go ahead and cut 1.7 with out GEODE-5338 as I don't have the code
ready.
GEODE-5594, adds a new flag to enable hostname validation and is disabled
by default so we are good with changes that are already merged and
documentation for GEODE-5594 is ready merged.
Naba, after the branch is cut
I am waiting on the documentation tickets to get closed before cutting the
branch.
Regards
Nabarun Nag
On Fri, Aug 31, 2018 at 10:18 AM Anthony Baker wrote:
> Perhaps we should cut 1.7.0 without these changes to give us more time to
> review and complete the work.
>
> Thoughts?
>
> Anthony
>
>
+1 to cutting without
Given the back and forth we have seen on the TLS change, I'd rather avoid
rushing it.
On Fri, Aug 31, 2018 at 10:18 AM, Anthony Baker wrote:
> Perhaps we should cut 1.7.0 without these changes to give us more time to
> review and complete the work.
>
> Thoughts?
>
> Anthon
Perhaps we should cut 1.7.0 without these changes to give us more time to
review and complete the work.
Thoughts?
Anthony
> On Aug 31, 2018, at 8:03 AM, Sai Boorlagadda
> wrote:
>
> I haven't yet merged GEODE-5338. The PR changes the existing behavior and
> is not acceptable.
> Working on c
I haven't yet merged GEODE-5338. The PR changes the existing behavior and
is not acceptable.
Working on changing the implementation to have a default value derived
based on how user
wants to configure SSL.
Sai
On Wed, Aug 29, 2018 at 11:45 AM Sai Boorlagadda
wrote:
> I have merged GEODE-5594 to
12 matches
Mail list logo
