Dependency review for release 1.9.0

I was reviewing the release branch and noticed a number of new dependencies have been added since the last release. When you add a new dependency, please review and follow the project license guide [1]. In particular, update the LICENSE file in geode-assembly/src/main/dist depending on the

Re: another ticket for 1.9?

I've merged the change for GEODE-6423 to the release/1.9.0 branch On 2/27/19 1:56 PM, Anthony Baker wrote: +1 On Feb 27, 2019, at 1:13 PM, Bruce Schuchardt wrote: I'm wondering if we could put the fix for GEODE-6423 in the release/1.9.0

Re: another ticket for 1.9?

+1 > On Feb 27, 2019, at 1:13 PM, Bruce Schuchardt wrote: > > I'm wondering if we could put the fix for GEODE-6423 > in the release/1.9.0 > branch. This bug can cause a server to be kicked out faster than it should > if it fails to pass an

another ticket for 1.9?

I'm wondering if we could put the fix for GEODE-6423 in the release/1.9.0 branch.  This bug can cause a server to be kicked out faster than it should if it fails to pass an availability check.

Re: next steps on release/1.9.0

The fix for 6451 has been merged into the release/1.9.0 branch On 2/27/19 11:32 AM, Bruce Schuchardt wrote: I want to merge the PR for GEODE-6451 into the release/1.9.0 branch. It's been reviewed and is going through final testing now. On 2/27/19 10:26 AM, Sai Boorlagadda wrote: By end of

Re: next steps on release/1.9.0

Sai, It looks like the documentation issue around GEODE-2113 was fixed at some point as part of another effort, so I've closed that ticket. GEODE-4794 needs some docs clarification and then it will be ready to go, as well. Best, Joey On Wed, Feb 27, 2019 at 11:32 AM Bruce Schuchardt wrote: >

Re: next steps on release/1.9.0

I want to merge the PR for GEODE-6451 into the release/1.9.0 branch.  It's been reviewed and is going through final testing now. On 2/27/19 10:26 AM, Sai Boorlagadda wrote: By end of this week, I am planning to create the first release candidate. Are there any other issues other than this last

Re: Release branch for Apache Geode 1.9.0 has been cut

Ok GEODE-6404 is merged into release/1.9.0 branch commit 40b3d9c690257d3e0e9bccfa1677c8adcbdce096 (*HEAD -> **release/1.9.0*, *origin/release/1.9.0*) Author: Jason Huynh Date: Mon Feb 25 18:31:21 2019 + GEODE-6404: work around possible sync issue with computeIfAbsent (#3196)

Re: next steps on release/1.9.0

I removed 1.9.0 from GEODE-6816. -Dan On Wed, Feb 27, 2019 at 10:26 AM Sai Boorlagadda wrote: > By end of this week, I am planning to create the first release candidate. > Are there any other issues other than this last one? > > - GEODE-6359 - Bruce is looking into it. > - geode-examples using

next steps on release/1.9.0

By end of this week, I am planning to create the first release candidate. Are there any other issues other than this last one? - GEODE-6359 - Bruce is looking into it. - geode-examples using https in build scripts. There are about 6[1] issues in JIRA that are in open/in-progress/re-opened status

Re: GEODE-6389 fixed in release/1.9.0

FYI all. GEODE-6338 is already on the release branch. Thanks, Bruce for the update. https://issues.apache.org/jira/browse/GEODE-6338 On Wed, Feb 27, 2019 at 10:10 AM Anthony Baker wrote: > Sorry I meant GEODE-6338. > > > On Feb 27, 2019, at 9:41 AM, Sai Boorlagadda > wrote: > > > > Are you

Re: Release branch for Apache Geode 1.9.0 has been cut

Ok will do. Also, I think Bruce is going to take a look at https://issues.apache.org/jira/browse/GEODE-6359. I'll let you know when I merge to 1.9 On Wed, Feb 27, 2019 at 9:19 AM Sai Boorlagadda wrote: > Jason, You can go ahead and cherry pick onto the release branch. > > Sai > > On Wed, Feb

Re: GEODE-6389 fixed in release/1.9.0

Sorry I meant GEODE-6338. > On Feb 27, 2019, at 9:41 AM, Sai Boorlagadda > wrote: > > Are you asking about GEODE-6343? > > Sai > > On Wed, Feb 27, 2019 at 7:51 AM Anthony Baker wrote: > >> Cool! Is GEODE-63438 also important to fix and merge into 1.9.0? >> >> Anthony >> >> >>> On Feb

Re: GEODE-6389 fixed in release/1.9.0

Are you asking about GEODE-6343? Sai On Wed, Feb 27, 2019 at 7:51 AM Anthony Baker wrote: > Cool! Is GEODE-63438 also important to fix and merge into 1.9.0? > > Anthony > > > > On Feb 22, 2019, at 9:01 AM, Bruce Schuchardt > wrote: > > > > This issue has been resolved on develop and

Re: Release branch for Apache Geode 1.9.0 has been cut

Jason, You can go ahead and cherry pick onto the release branch. Sai On Wed, Feb 27, 2019 at 8:54 AM Jason Huynh wrote: > Hi Sai, > > Fix for GEODE-6404 is now on develop > (2be6375a775b6b0d00d0c41a1e2a3bf4b8745a46) > Would you be able to pull it into the 1.9 branch or would you like me to? >

Re: Release branch for Apache Geode 1.9.0 has been cut

Hi Sai, Fix for GEODE-6404 is now on develop (2be6375a775b6b0d00d0c41a1e2a3bf4b8745a46) Would you be able to pull it into the 1.9 branch or would you like me to? Thanks, -Jason On Thu, Feb 21, 2019 at 3:37 PM Sai Boorlagadda wrote: > GEODE-6359 is unassigned in JIRA. Who is working on it? >

Re: GEODE-6389 fixed in release/1.9.0

Cool! Is GEODE-63438 also important to fix and merge into 1.9.0? Anthony > On Feb 22, 2019, at 9:01 AM, Bruce Schuchardt wrote: > > This issue has been resolved on develop and release/1.9.0 >