Re: Release branch for Apache Geode 1.9.0 has been cut

2019-02-27 Thread Jason Huynh
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: Release branch for Apache Geode 1.9.0 has been cut

2019-02-27 Thread Jason Huynh
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 2

Re: Release branch for Apache Geode 1.9.0 has been cut

2019-02-27 Thread Sai Boorlagadda
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

2019-02-27 Thread Jason Huynh
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: Release branch for Apache Geode 1.9.0 has been cut

2019-02-21 Thread Sai Boorlagadda
GEODE-6359 is unassigned in JIRA. Who is working on it? On Wed, Feb 20, 2019 at 9:08 AM Jason Huynh wrote: > Oh ok I thought I read that voting was going to start soon, so I thought > I'd raise a concern about the tickets not being fixed yet. > > I meant this ticket https://issues.apache.org/jir

Re: Release branch for Apache Geode 1.9.0 has been cut

2019-02-21 Thread Owen Nichols
Looks good, I see https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsUnitTestOpenJDK11/builds/285 ran successfully using the new image. Please bring this fix into 1.9.0. > On Feb 21, 2019, at 2:21 PM, Owen Nichols wrote: > > I would like to see > https

Re: Release branch for Apache Geode 1.9.0 has been cut

2019-02-21 Thread Owen Nichols
I would like to see https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-images/jobs/build-google-windows-geode-builder/builds/15 succeed and a run of windows tests on the develop pipeline using this image, if that goes well then +1 for bringing into 1.9 release branch. > O

Re: Release branch for Apache Geode 1.9.0 has been cut

2019-02-21 Thread Sai Boorlagadda
I want to merge a change related to CI infrastructure (windows image that we use to run tests on Windows). This change will fix the failing windows tests. Find more details on GEODE-6438 Sai On Wed, Feb 20, 2019 at 9:26 AM Alexander Murmann wrote: > > > > Oh ok I thought I read that voting was

Re: Release branch for Apache Geode 1.9.0 has been cut

2019-02-20 Thread Alexander Murmann
> > Oh ok I thought I read that voting was going to start soon > Are you referring to the RC vote? Per the previous discussed release schedule and the wiki , the actual release shouldn't happen till March 1st. On Wed, Feb 20, 2019

Re: Release branch for Apache Geode 1.9.0 has been cut

2019-02-20 Thread Jason Huynh
Oh ok I thought I read that voting was going to start soon, so I thought I'd raise a concern about the tickets not being fixed yet. I meant this ticket https://issues.apache.org/jira/browse/GEODE-6359 This seems like a bad thing to have in the product. It looks like a possible issue when process

Re: Release branch for Apache Geode 1.9.0 has been cut

2019-02-19 Thread Sai Boorlagadda
GEODE-6404 can be cherry-picked when it is ready. The release branch is cut to avoid any risk of regression that can be introduced by new work being merged to develop. Do you mean GEODE-6369? On Tue, Feb 19, 2019 at 4:50 PM Jason Huynh wrote: > Correction, GEODE-6359 and GEODE-6404. > > On Tue,

Re: Release branch for Apache Geode 1.9.0 has been cut

2019-02-19 Thread Jason Huynh
I still haven't gotten GEODE-6404 in... I assumed that the tickets from the last thread were going to make it into this release? Also I think GEODE-6539 should be fixed, it looks like an NPE that occurs when we process leave requests. On Tue, Feb 19, 2019 at 2:25 PM Sai Boorlagadda wrote: > M

Re: Release branch for Apache Geode 1.9.0 has been cut

2019-02-19 Thread Jason Huynh
Correction, GEODE-6359 and GEODE-6404. On Tue, Feb 19, 2019 at 4:49 PM Jason Huynh wrote: > I still haven't gotten GEODE-6404 in... I assumed that the tickets from > the last thread were going to make it into this release? > > Also I think GEODE-6539 should be fixed, it looks like an NPE that oc

Re: Release branch for Apache Geode 1.9.0 has been cut

2019-02-19 Thread Sai Boorlagadda
My earlier release branch has created as 'release/1.9' without the patch number in semver. So I have re-created a new release branch 'release/1.9.0'. I will go ahead delete the unwanted branch 'release/1.9' Sai On Tue, Feb 19, 2019 at 2:17 PM Sai Boorlagadda wrote: > Hello Everyone, > > As disc

Release branch for Apache Geode 1.9.0 has been cut

2019-02-19 Thread Sai Boorlagadda
Hello Everyone, As discussed in my earlier email I have created a new release branch for Apache Geode 1.9.0 - "release/1.9" Please do review and raise any concern with the release branch. If no concerns are raised, we will start with the voting for the release candidate soon. Regards Sai