Re: [DISCUSS] Blocking merge button in PR

2019-10-18 Thread Nabarun Nag
build? > >> > >> At last discussion, one concern raised was providing a way that anyone > in > >> the community could re-trigger a failed PR check if it hit an unrelated > >> flaky failure. > >> > >> Let’s be sure we've identified the problem bef

[DISCUSS] Blocking merge button in PR

2019-10-18 Thread Nabarun Nag
till all tests are done? Regards Nabarun Nag

Re: [DISCUSS] - Cutting of release 1.9.2

2019-09-20 Thread Nabarun Nag
Just out of curiosity, do we have preliminary tests done to ensure that all the tasks under GEODE-7121 are enough to implement the solution by Spring Data Gemfire to solve the deadlock issue? +1 to include the fix. On Fri, Sep 20, 2019 at 1:13 PM John Blum wrote: > +1 for releasing Apache

Re: [VOTE] Adding a lucene specific fix to release/1.10.0

2019-09-19 Thread Nabarun Nag
+1 On Thu, Sep 19, 2019 at 10:49 AM Xiaojian Zhou wrote: > I want to merge GEODE-7208, which is lucene specific fix > > The fix will enable indexing on inherited attributes in user object. > > revision 4ec87419d456748a7d853e979c90ad4e301b2405 > > Regards > Gester >

Re: [VOTE] Adding new AEQ feature to release/1.10.0

2019-09-16 Thread Nabarun Nag
> > > wrote: > > > > > > > > > > > +1 > > > > > > > > > > > > On Fri, Sep 13, 2019 at 3:25 PM Anilkumar Gingade < > > > aging...@pivotal.io > > > > > > > > > > > wrote: > &

[VOTE] Adding new AEQ feature to release/1.10.0

2019-09-13 Thread Nabarun Nag
Will create a PR ASAP. Regards Nabarun Nag

Re: [VOTE] Apache Geode 1.10.0.RC1

2019-09-06 Thread Nabarun Nag
ava:1466) > >>> > >>> at > org.apache.geode.internal.cache.tier.sockets.command.Destroy65.cmdExecute(Destroy65.java:114) > >>> > >>> at > org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:183) > >>> > >>> at > org

Re: [VOTE] Apache Geode 1.9.1.RC3

2019-09-06 Thread Nabarun Nag
Can anyone confirm that the native client test failure happening in 1.10 RC does not occur in this candidate. I can test it if someone can point me to the instructions to do that. Regards Naba On Fri, Sep 6, 2019 at 8:38 AM Robert Houghton wrote: > +1 given the pre-existence of threw class

Re: [VOTE] Apache Geode 1.10.0.RC1

2019-09-05 Thread Nabarun Nag
; org/apache/geode/internal/cache/EvictionAttributesImpl,false > > 276d270 > > < org/apache/geode/internal/cache/PartitionAttributesImpl,false > > 517d510 > > < > > > > > org/apache/geode/management/internal/cli/functions/CacheRealizationFunction,false &g

Re: [VOTE] Apache Geode 1.10.0.RC1

2019-09-05 Thread Nabarun Nag
all stack. If it is still failing for you I recommend getting a fresh > clone of geode and then repeat the above steps. > > Thanks, > Kirk > > On Thu, Sep 5, 2019 at 10:16 AM Nabarun Nag wrote: > > > Hello, > > > > I was able to notice that after running

Re: [VOTE] Apache Geode 1.10.0.RC1

2019-09-05 Thread Nabarun Nag
if this is harmless or has some adverse consequences. I would like to know why it's designed this way. Regards Nabarun Nag On Wed, Sep 4, 2019 at 4:14 PM Dick Cavender wrote: > We manually signed the apache-geode-1.10.0-src.tgz dist and uploaded the > asc file. > > Unclear on why this

Re: Proposal to include GEODE-7088 and GEODE-7089 in 1.10.0

2019-08-26 Thread Nabarun Nag
+1 This will be a good inclusion in Apache Geode 1.10.0 release. Regards Naba On Mon, Aug 26, 2019 at 3:36 PM Jacob Barrett wrote: > +1 > > Thanks for the details! > > > On Aug 26, 2019, at 3:33 PM, Ryan McMahon wrote: > > > > Udo, > > > > Here are inline answers to your questions: > > > >

Re: [DISCUSS] Controlling event dispatch to AsyncEventListener (review by Aug 22)

2019-08-20 Thread Nabarun Nag
Hi Anil, Will it be possible to explain to the community how the starting AEQ in a paused state is different from creating gateway senders with manual start set to true. It may be of concern as 'manual start' for gateways is a deprecated. Just thinking out loud, will it be more feasible if we

Re: Propose fix for 1.10 release: Export offline data command failed with EntryDestroyedException

2019-08-16 Thread Nabarun Nag
+1 On Fri, Aug 16, 2019 at 2:45 PM Anilkumar Gingade wrote: > +1 to include > > On Fri, Aug 16, 2019 at 2:41 PM Anthony Baker wrote: > > > +1 from me. When you need to do an offline export, it’s usually > > important. Not being able to export *all* the data might lead to data > loss. > > > >

Re: Proposal to Include GEODE-7079 in 1.10.0

2019-08-15 Thread Nabarun Nag
+1 On Thu, Aug 15, 2019 at 10:15 AM Alexander Murmann wrote: > +1 > > Agreed to fixing this. It's impossible for a user to discover they hit an > edge case that we fail to support till they are in prod and restart. > > On Thu, Aug 15, 2019 at 10:09 AM Juan José Ramos > wrote: > > > Hello Udo,

Re: [DISCUSS] Time to cut Geode 1.10.0?

2019-08-06 Thread Nabarun Nag
Hi, The commit mentioned in the earlier email has now been reverted on develop and release/1.10.0 branches. Thank you for your patience. Regards Nabarun Nag On Tue, Aug 6, 2019 at 2:13 PM Nabarun Nag wrote: > Hi Geode Community, > > After some further analysis, few of the threads ar

Re: [DISCUSS] Time to cut Geode 1.10.0?

2019-08-06 Thread Nabarun Nag
n and we presume that it was introduced by the following commit. GEODE-6973: Use cachelistener to synchronize typeToId with IdToType r… (#3853) We are planning to revert this commit in the release branch as this is a necessary fix that needs to be in the release. Regards Nabarun Nag On Tue, Aug 6, 2019

Re: [DISCUSS] Time to cut Geode 1.10.0?

2019-08-06 Thread Nabarun Nag
or Geode 1.10 with the > >> 1.9.0 > >>>>>>>> release > >>>>>>>>> manager's help (Owen:). > >>>>>>>>> > >>>>>>>>> I'd like to propose cutting the release/1.10 branch off develop

Re: New release branch for Apache Geode 1.10.0

2019-08-02 Thread Nabarun Nag
fo/teams/main/pipelines/apache-release-1-10-0-main > > > >> is all green. Perhaps one way to convince the Geode community that your > >> fix satisfies the “critical fixes” rule might be to share a link to a > >> github commit adding tests that expose the issue. &

Re: New release branch for Apache Geode 1.10.0

2019-08-02 Thread Nabarun Nag
in develop. We need to hold any pipeline testing on the branch till this fix is in. Regards Nabarun Nag On Fri, Aug 2, 2019 at 11:17 AM Dick Cavender wrote: > Hello Geode Dev Community, > > We have created a new release branch for Apache Geode 1.10.0 - > "release/1.10.0"

Re: [DISCUSS] Time to cut Geode 1.10.0?

2019-07-26 Thread Nabarun Nag
, where we involved the entire community in its development, phase by phase. The wiki is up and running, if someone has any concerns can raise it as a JIRA or comment in the wiki and the community as a whole can decide if it is a valid concern or not and act upon it. Regards Nabarun Nag On Fri

Re: what is the best way to update a geode pull request

2019-05-31 Thread Nabarun Nag
ot;contextually irrelevant" noise. (also > makes it harder to follow all the changes that are in a branch). What if > I want to rollback a commit into develop, how many does one have to > revert, 1 is always simpler than 2-10... Also.. cherry picking becomes > simpler... > > --

Re: what is the best way to update a geode pull request

2019-05-31 Thread Nabarun Nag
In my opinion, I am okay will multiple commits within a PR. But please do squash them to a single commit when it is pushed to develop. This helps us a ton if it is single commit. - bisect operations are easier when it is a single commit during major failure analysis. - cherrypick is easier when

Re: [DISCUSS] require reviews before merging a PR

2019-05-31 Thread Nabarun Nag
Hi, I agree with Dan, I would like to follow what he has suggested. Also, I will not mind anyone following the 3 reviewers for everything if they chose to do so. Just please don't make it blanket rule. Regards Naba PS: I found this filter on github to look up PRs that I have reviewed till date

Re: [DISCUSS] require reviews before merging a PR

2019-05-31 Thread Nabarun Nag
Hi, I personally feel the same as how Bruce feels. - This will make life harder / inconvenient. - One approval from a person who is experienced in that part of code is more than enough for me. - The workload on the Geode developers is already too high, it is unfair to burden then with more

Re: [DISCUSS] Remove exception.getMessage() error handling

2019-05-28 Thread Nabarun Nag
an exception class name. Regards Nabarun Nag On Tue, May 28, 2019 at 3:08 PM Owen Nichols wrote: > This example came from https://issues.apache.org/jira/browse/GEODE-6796 > in which the submitter assumed that Geode was deliberately emitting a > poorly-worded and confusing error message. &g

Re: [VOTE] Apache Geode 1.9.0 RC4

2019-04-24 Thread Nabarun Nag
e-native-1.9.0-src.tar.gz > gpg: Signature made Fri Apr 19 16:25:20 2019 PDT > gpg:using RSA key DB5476815A475574577D442B468A4800EAFB2498 > gpg: Good signature from "Owen Nichols " [full] - Regards Nabarun Nag On Wed, Apr 24, 2019 at 8:36 AM Ryan McMahon wrote: > +1 Verified signatures,

Re: Geode 1.9 Release Manager

2019-02-14 Thread Nabarun Nag
se branch. > > On Thu, Feb 14, 2019 at 1:18 PM Nabarun Nag wrote: > > > I agree but not putting in these fixes means that we are releasing with > > serious known issues in the product. Hence in my opinion this risk is > > acceptable. > > > > Regards > > N

Re: Geode 1.9 Release Manager

2019-02-14 Thread Nabarun Nag
likely, but not remove the risk entirely. > > On Thu, Feb 14, 2019 at 12:00 PM Nabarun Nag wrote: > > > I could not find any DISCUSS mails about not blocking a release. I may be > > wrong, I apologize for that but could point me to the mail / > documentation > > about

Re: Geode 1.9 Release Manager

2019-02-14 Thread Nabarun Nag
I could not find any DISCUSS mails about not blocking a release. I may be wrong, I apologize for that but could point me to the mail / documentation about the release management. Regards Naba On Thu, Feb 14, 2019 at 11:52 AM Sai Boorlagadda wrote: > Did we not agreed that we won't be blocking

Re: Geode 1.9 Release Manager

2019-02-14 Thread Nabarun Nag
I agree with the cutting the release branch, keep it sanitized from additional commits going into develop but ensure only these important critical fixes mentioned above in this chain makes it into the release branch. For the second part, I am not sure how it was determined that fixes for

Re: Geode 1.9 Release Manager

2019-02-14 Thread Nabarun Nag
I think also GEODE-6391, which is to fix a NPE while propagating región destroy and invalidate region messages. Regards Naba On Thu, Feb 14, 2019 at 9:06 AM Jason Huynh wrote: > I think Kirk's topic and any solution related to stats (int to long) should > be resolved before cutting the

Re: Very red CI -> Hold merges, please

2019-02-07 Thread Nabarun Nag
FYI, I have just merged a ci timeout fix to increase the timeout for geode-benchmarks to 4h. This does not influence any geode modules. Regards Naba On Thu, Feb 7, 2019 at 9:32 AM Alexander Murmann wrote: > Hi folks, > > Our CI is very red since ~24 hours > < >

Re: Extremely long IntelliJ Gradle refresh times

2019-01-09 Thread Nabarun Nag
I have not experienced this but , for it does take a long time (but not 60min) after an IntelliJ update or invalidating IntelliJ caches. That time it indexes all the Java , maven and gradle caches , sources and jars. Subsequent refreshes are faster. Also increasing IntelliJ memory to 8g helps.

Re: Geode Version in the logs

2019-01-03 Thread Nabarun Nag
Just in case you are planning to write tests consisting of multiple versions of Apache Geode simultaneously, you can look into any RollingUpgradeDUnitTest. Those append the version number before each log statement. Regards Nabarun Nag On Thu, Jan 3, 2019 at 8:53 AM Jacob Barrett wrote: > Gi

Re: [VOTE] Apache Geode 1.8.0 RC2

2018-12-10 Thread Nabarun Nag
Hi Sai, I tried running the test on the source distribution using IntelliJ and gradle scripts. I have not encountered the failure. Regards Nabarun Nag On Mon, Dec 10, 2018 at 11:20 PM Sai Boorlagadda wrote: > -0 > > - Ran examples > - Building geode from source distribution or re

Re: [VOTE] Apache Geode 1.8.0 RC2

2018-12-06 Thread Nabarun Nag
+1 on the basis of the below tests. -- Verified SHAs -- Verified signatures. -- Build apache-geode, apache-geode-examples, apache-geode-native -- Ran the examples -- start gfsh, start server, create region, do a put, verify using query. --Verified commit IDs with the release tags. We should

Re: [VOTE] Apache Geode 1.8.0 RC1

2018-12-03 Thread Nabarun Nag
Thank you Alexander and Anthony for the explanation. I am sorry for missing the signature checks for the apache geode src. :( Was able to build and run geode-native code. Regards Nabarun Nag On Mon, Dec 3, 2018 at 9:52 AM Dan Smith wrote: > I see a few things with the artifacts that I th

Re: [VOTE] Apache Geode 1.8.0 RC1

2018-12-03 Thread Nabarun Nag
in the source release apache-geode-1.8.0-src 2. gradlew file differs in the rel/v1.8.0.RC1 repo and the source release apache-geode-1.8.0-src. Apologies if these changes are expected. Regards Nabarun Nag On Fri, Nov 30, 2018 at 5:38 PM Alexander Murmann wrote: > Hi everyone, > >

Re: Avoiding Unpredictability in Our DUnit Testing Rules

2018-11-21 Thread Nabarun Nag
Will doing this in the test, final Host host = Host.getHost(0); VM server1 = host.getVM(startingVersion, 0); be frowned upon, if I use the above over using @Rule. Regards Nabarun Nag > On Nov 21, 2018, at 10:36 AM, Robert Houghton wrote: > > Great find, Patrick. I hope this shakes

Re: GEODE Slack?

2018-11-16 Thread Nabarun Nag
It’s already present. You can find it at http://the-asf.slack.com/ On Fri, Nov 16, 2018 at 3:22 PM Ernest Burghardt wrote: > Hi Geode, > > Will there be a GEODE Slack in the near future? > > Thanks, > EB > -- Regards Nabarun Nag

Requesting access to concourse.

2018-11-15 Thread Nabarun Nag
Hi, Please grant me access to the concourse infrastructure to run/setup pipelines. Regards Nabarun Nag

Re: Release branch for Apache Geode 1.8.0 has been cut

2018-11-14 Thread Nabarun Nag
I would also like to put in the fix for GEODE-6053. It's in the review phase and soon will be in the develop and the release branch. Regards Nabarun Nag > On Nov 14, 2018, at 10:28 AM, Jason Huynh wrote: > > I'd like to cherry pick the following two commits to release/1.8. >

Re: [DISCUSS] LGTM on pull requests

2018-11-09 Thread Nabarun Nag
As per running periodically , LGTM runs it every Monday. As for who would fix it, LGTM mentions which commit caused the failure and who was the author of it. So i think its the author's responsibility to fix it. Personally, LGTM list a table that shows how many alerts we caused by which author

Re: Release process for Apache Geode wiki

2018-10-11 Thread Nabarun Nag
; > On Wed, Oct 10, 2018 at 7:01 PM Nabarun Nag wrote: > > > Hi, > > > > I have created a new wiki page on how to release Apache Geode. > > Please do a review and let me know if there are any suggestions or > > modifications required. > > > >

Release process for Apache Geode wiki

2018-10-10 Thread Nabarun Nag
Hi, I have created a new wiki page on how to release Apache Geode. Please do a review and let me know if there are any suggestions or modifications required. https://cwiki.apache.org/confluence/display/GEODE/Releasing+Apache+Geode Regard Nabarun Nag

Re: [VOTE] Time-based release schedule for minor releases

2018-10-08 Thread Nabarun Nag
+1 On Mon, Oct 8, 2018 at 2:27 PM Jacob Barrett wrote: > +0 > > My preference is to release when there is something worth releasing rather > than arbitrary points in time but I don't hold that preference strongly > enough to spike this effort. > > On Mon, Oct 8, 2018 at 2:24 PM Alexander

Re: [DISCUSS] Predictable minor release cadence

2018-10-04 Thread Nabarun Nag
the branch till releasing RC2. As testing of release/1.7.0 + RC1 was time bounded as voting time frame was 72hours. If we have the release branch for a month, we don't have to hurry with the testing. Regards Nabarun Nag On Thu, Oct 4, 2018 at 2:43 PM Dan Smith wrote: > +1 I definitely like the i

[ANNOUNCE] Apache Geode 1.7.0

2018-10-04 Thread Nabarun Nag
at: http://geode.apache.org/docs/guide/17/about_geode.html We would like to thank all the contributors that made the release possible. Regards, Nabarun Nag on behalf of the Apache Geode team

Re: Requesting access to dockerHub

2018-10-03 Thread Nabarun Nag
Thank you On Wed, Oct 3, 2018 at 3:49 PM Anthony Baker wrote: > Done! > > > On Oct 3, 2018, at 3:41 PM, Nabarun Nag wrote: > > > > nabarun13 is my dockerID > > > > On Wed, Oct 3, 2018 at 3:37 PM Nabarun Nag wrote: > > > >>

Re: Requesting access to dockerHub

2018-10-03 Thread Nabarun Nag
nabarun13 is my dockerID On Wed, Oct 3, 2018 at 3:37 PM Nabarun Nag wrote: > Requesting access to be authenticated in DockerHub and be an administrator > of the project. > This is to upload the docker artifacts > > > Regards > Nabarun Nag >

Requesting access to dockerHub

2018-10-03 Thread Nabarun Nag
Requesting access to be authenticated in DockerHub and be an administrator of the project. This is to upload the docker artifacts Regards Nabarun Nag

Re: AnalyzeSerializablesJUnitTestBase failure

2018-10-03 Thread Nabarun Nag
I used to see this issue when I make changes in the serializable class or its members but don't reflect it in the sanctioned-geode-core-serializables.txt file. If I am using a custom object in a test or something I add it as SERIALIZABLE_OBJECT_FILTER property. Is your branch hosted in github?

Re: [VOTE] Apache Geode 1.7.0 RC2

2018-10-03 Thread Nabarun Nag
My apologies Sai. I missed the name in the PMC list. Thank you for correcting the count. Regards Nabarun Nag On Wed, Oct 3, 2018 at 7:34 AM Sai Boorlagadda wrote: > One correction but this does not change the voting result. > > PMC members : > - Anthony Baker > - Dan Smith &

Re: [VOTE] Apache Geode 1.7.0 RC2

2018-10-02 Thread Nabarun Nag
. With this, we declare that Apache Geode 1.7.0 RC2 passes the vote. Release process will begin soon. Regards Nabarun Nag [1] https://www.apache.org/foundation/voting.html On Tue, Oct 2, 2018 at 11:57 AM Alexander Murmann wrote: > + 1 > > verified clean build > verified green pipeline >

Re: [VOTE] Apache Geode 1.7.0 RC2

2018-09-27 Thread Nabarun Nag
version - out scripts are now present in the source distribution -> ./ci/resource-types/gce-instances-resource/out -> ./ci/resource-types/concourse-metadata-resource/files/out Regrads Nabarun Nag On Thu, Sep 27, 2018 at 6:54 PM Nabarun Nag wrote: > This is the second release

[VOTE] Apache Geode 1.7.0 RC2

2018-09-27 Thread Nabarun Nag
Regards Nabarun Nag

Re: [VOTE] Apache Geode 1.7.0 RC1

2018-09-26 Thread Nabarun Nag
for Apache Geode 1.7.0. Please stay tuned for the next release candidate. Regards Nabarun Nag On Wed, Sep 26, 2018 at 5:41 PM Jason Huynh wrote: > Hi Nabarun, > > > > Thanks for delaying the vote, after investigating, it looks like we may > have increased our chances of

Re: [VOTE] Apache Geode 1.7.0 RC1

2018-09-24 Thread Nabarun Nag
Hi Jason, We can wait until the investigation is completed, as this can be a potential -1 to the RC. Regards Nabarun Nag On Mon, Sep 24, 2018 at 12:20 PM Jason Huynh wrote: > I'm currently looking into an issue in WAN when running this rc. Not sure > if it's a showstopper and I

Re: [VOTE] Apache Geode 1.7.0 RC1

2018-09-19 Thread Nabarun Nag
REMINDER: VOTE deadline is today (EOD 19th September 2018 PDT) Regards Nabarun Nag On Wed, Sep 19, 2018 at 7:13 AM Anthony Baker wrote: > I think we can get rid of the **/out/** exclusion in the build script, > let’s do that for the next release. > > Anthony > > > > On

Re: [VOTE] Apache Geode 1.7.0 RC1

2018-09-17 Thread Nabarun Nag
on these changes. Regards Nabarun Nag On Fri, Sep 14, 2018 at 2:50 PM Nabarun Nag wrote: > Correction : > Please note that we are voting upon the source tags: rel/v1.7.0.RC1 > > On Fri, Sep 14, 2018 at 2:49 PM Nabarun Nag wrote: > >> This is the first release candidate for

Re: [VOTE] Apache Geode 1.7.0 RC1

2018-09-14 Thread Nabarun Nag
Correction : Please note that we are voting upon the source tags: rel/v1.7.0.RC1 On Fri, Sep 14, 2018 at 2:49 PM Nabarun Nag wrote: > This is the first release candidate for Apache Geode, version 1.7.0. > Thanks to all the community members for their contributions to this > release! &

[VOTE] Apache Geode 1.7.0 RC1

2018-09-14 Thread Nabarun Nag
if there was an oversight. Regards Nabarun Nag

Write permission on cwiki

2018-09-14 Thread Nabarun Nag
Requesting write permissions on geode wiki page to update the release docs for 1.7.0RC1 username: nnag name: nabarun Regards Nabarun Nag

Re: [DISCUSS] and the NEW Apache Geode 1.7.0 release branch has been created

2018-09-13 Thread Nabarun Nag
Thank you Patrick. Starting with creation of the first release candidate Regards Nabarun Nag On Thu, Sep 13, 2018 at 11:39 AM Patrick Rhomberg wrote: > Revert of 5600 commits pushed to release/1.7.0. Built clean locally and > `$> gfsh version --full` is behaving as expected. > &

Re: [DISCUSS] and the NEW Apache Geode 1.7.0 release branch has been created

2018-09-13 Thread Nabarun Nag
GEODE-5727 is closed and merged to release/1.7.0 Thank you Jinmei On Thu, Sep 13, 2018 at 9:47 AM Nabarun Nag wrote: > Thank you Patrick. Please do send a notification email once this is > reverted in the release/1.7.0 branch. > Thank you Jinmei for putting the fix for GEODE-5727 int

Re: [DISCUSS] and the NEW Apache Geode 1.7.0 release branch has been created

2018-09-13 Thread Nabarun Nag
Thank you Patrick. Please do send a notification email once this is reverted in the release/1.7.0 branch. Thank you Jinmei for putting the fix for GEODE-5727 into release/1.7.0. However the GEODE ticket is still in open state. Can it be closed? Regards Nabarun Nag On Thu, Sep 13, 2018 at 9:21

Re: [DISCUSS] and the NEW Apache Geode 1.7.0 release branch has been created

2018-09-12 Thread Nabarun Nag
be incorporated after discussions. Is it acceptable? Regards Nabarun Nag On Wed, Sep 12, 2018 at 4:37 PM Patrick Rhomberg wrote: > Okay. So that information is definitely coming from the > GemFireVersion.properties file, which explains this issue. Either > reverting the previous G

Re: [DISCUSS] and the NEW Apache Geode 1.7.0 release branch has been created

2018-09-12 Thread Nabarun Nag
urce-Revision=c637193aa61abdfd236ae36b6d9a228fc1e84bcd Source-Repository=release/1.7.0 Hope this helps Regards Nabarun Nag On Wed, Sep 12, 2018 at 3:51 PM Patrick Rhomberg wrote: > I'm happy to work on those reverts, although if Anthony could elaborate on > where exactly the version info

Re: [DISCUSS] and the NEW Apache Geode 1.7.0 release branch has been created

2018-09-12 Thread Nabarun Nag
Nabarun Nag On Wed, Sep 12, 2018 at 2:50 PM Alexander Murmann wrote: > While there is a workaround this looks like a highly visible bug with a > fairly safe fix. I am in favor of merging, since the branch is still > distressed anyways. > > Other opinions? > > On Wed, Se

Re: [DISCUSS] and the NEW Apache Geode 1.7.0 release branch has been created

2018-09-10 Thread Nabarun Nag
Hello Anthony, I plan to do that while creating the release candidate. If there are no concerns raised on the release branch, I will start with the process soon. Regards Nabarun Nag On Mon, Sep 10, 2018 at 8:51 AM Anthony Baker wrote: > Looks good Naba! Only thing I see right

Re: [DISCUSS] and the NEW Apache Geode 1.7.0 release branch has been created

2018-09-07 Thread Nabarun Nag
CORRECTION: if '*no*' concerns are raised, we will start with the voting for the release candidate soon. Regrads Nabarun Nag On Fri, Sep 7, 2018 at 9:08 AM Nabarun Nag wrote: > Hello Geode Dev Community, > > We have created a new release branch for Apache Geode 1.7.0 - > &q

[DISCUSS] and the NEW Apache Geode 1.7.0 release branch has been created

2018-09-07 Thread Nabarun Nag
the voting for the release candidate soon. Regards Nabarun Nag

Re: Concerning Apache Geode 1.7.0

2018-09-05 Thread Nabarun Nag
in place the snapshots would be published on clean builds. > > -Jake > > > > On Sep 5, 2018, at 3:04 PM, Nabarun Nag wrote: > > > > @John, everything you mentioned in mail is how things happen in Apache > > Geode where we cut a release branch and develop moves to

Re: [DISCUSS] Apache Geode 1.7.0 release branch created

2018-09-05 Thread Nabarun Nag
[UPDATE] Cherry-picking 156333bfc397c96963e7af598897066989ff0d4e GEODE-5695 to release branch On Tue, Sep 4, 2018 at 4:45 PM Nabarun Nag wrote: > >>>>So the issue is that it takes longer to start than previous releases? > Yes > > >>>>Also, is this wait

Re: Concerning Apache Geode 1.7.0

2018-09-05 Thread Nabarun Nag
For the nightly build snapshot hosting, it will have to go through [DISCUSS] -> [VOTE] , then implemented. Currently, it is out of scope for the 1.7.0 release process. Regards Nabarun Nag On Wed, Sep 5, 2018 at 3:10 PM John Blum wrote: > I just need nightly build snapshots (with art

Re: Concerning Apache Geode 1.7.0

2018-09-05 Thread Nabarun Nag
. Regards Nabarun Nag On Wed, Sep 5, 2018 at 2:41 PM John Blum wrote: > I'd also say that, in general, those branches need to be cleaned up. There > are a crap load of branches in there! Are all those branches actively > developed and currently being built by a nightly CI? I'd argue th

Re: Concerning Apache Geode 1.7.0

2018-09-05 Thread Nabarun Nag
working on resolving them at the moment. Hopefully soon we will send out the mail and the updated release branch. Regards Nabarun Nag On Wed, Sep 5, 2018 at 2:22 PM John Blum wrote: > Doesn't the pending release branch, or something, publish (build) snapshot > artifacts to a snapsho

Re: Concerning Apache Geode 1.7.0

2018-09-05 Thread Nabarun Nag
as the branch is ready. Regards Nabarun Nag On Wed, Sep 5, 2018 at 2:10 PM John Blum wrote: > I see that the branch for Apache Geode 1.7.0 (release/1.7.0 [1]) has been > created in preparation for the upcoming the 1.7 release. > > I am trying to get an early sense/feel for the required ch

Re: 2 minute gateway startup time due to GEODE-5591

2018-09-05 Thread Nabarun Nag
*correction: cherry picked to release/1.7.0 On Wed, Sep 5, 2018 at 10:54 AM Nabarun Nag wrote: > @Udo I have mentioned in an earlier mail that it will be reverted in > develop and then cherry picked to develop. release/1.7.0 branch has not > being published yet, as it is undergoing pr

Re: 2 minute gateway startup time due to GEODE-5591

2018-09-05 Thread Nabarun Nag
@Udo I have mentioned in an earlier mail that it will be reverted in develop and then cherry picked to develop. release/1.7.0 branch has not being published yet, as it is undergoing preliminary tests before release candidate is published. Regards Nabarun Nag On Wed, Sep 5, 2018 at 10:46 AM Udo

Re: 2 minute gateway startup time due to GEODE-5591

2018-09-05 Thread Nabarun Nag
GEODE-5591 has been reverted in develop ref: 901da27f227a8ce2b7d6b681619782a1accd9330 Regards Nabarun Nag On Wed, Sep 5, 2018 at 10:14 AM Ryan McMahon wrote: > +1 for reverting in both places. > > I see that there is already an isGatewayReceiver flag in the AcceptorImpl > constr

Re: 2 minute gateway startup time due to GEODE-5591

2018-09-05 Thread Nabarun Nag
If everyone is okay with it, I will revert that change in develop and then cherry pick it to release/1.7.0 branch. Please do comment. Regards Nabarun Nag On Wed, Sep 5, 2018 at 9:30 AM Dan Smith wrote: > +1 to yank it and rework the fix. > > Gester's change helps, but it just means

Re: [DISCUSS] Apache Geode 1.7.0 release branch created

2018-09-04 Thread Nabarun Nag
Boorlagadda > wrote: > > > So the issue is that it takes longer to start than previous releases? > > Also, is this wait time only when using Gfsh to create gateway-receiver? > > > > On Tue, Sep 4, 2018 at 4:03 PM Nabarun Nag wrote: > > > > > C

Re: [DISCUSS] Apache Geode 1.7.0 release branch created

2018-09-04 Thread Nabarun Nag
--member=server1 5. create gateway-receiver --member=server2 `This gets stuck for 2 minutes` Is the 2 minute wait time acceptable? Should we document it? When we revert GEODE-5591, this issue does not happen. Regards Nabarun Nag On Tue, Sep 4, 2018 at 10:50 AM Nabarun Nag wrote: > Status Upd

Re: [DISCUSS] Apache Geode 1.7.0 release branch created

2018-09-04 Thread Nabarun Nag
Houghton] GEODE-5280 - [xiaojian zhou & Biju Kunjummen] These tickets have commits into develop but they are still open with fix version as 1.8.0 Regards Nabarun Nag On Fri, Aug 31, 2018 at 3:38 PM Dale Emery wrote: > I have resolved GEODE-5254 > > Dale > > > On Aug 31, 201

Re: [DISCUSS] Apache Geode 1.7.0 release branch created

2018-08-31 Thread Nabarun Nag
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 > c

Re: [DISCUSS] Apache Geode 1.7.0 release branch created

2018-08-31 Thread Nabarun Nag
mmen] GEODE-5254 - [Dale Emery] GEODE-4794 - [Sai] GEODE-5594 - [Sai] Regards Nabarun Nag On Fri, Aug 31, 2018 at 3:18 PM Nabarun Nag wrote: > > 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. > > Changin

Re: [DISCUSS] Apache Geode 1.7.0 release branch created

2018-08-31 Thread Nabarun Nag
Regards Nabarun Nag On Fri, Aug 31, 2018 at 2:20 PM Nabarun Nag wrote: > 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 F

Re: [DISCUSS] Apache Geode 1.7.0 release branch created

2018-08-31 Thread Nabarun Nag
d delete windows jobs from the > branch > > before we create the pipeline for 1.7. > > > > Apologies for holding up the release. > > > > Sai. > > > > On Fri, Aug 31, 2018, 10:23 AM Nabarun Nag wrote: > > > > > I am waiting on the documentation

Re: [DISCUSS] Apache Geode 1.7.0 release branch created

2018-08-31 Thread Nabarun Nag
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?

Re: [DISCUSS] Apache Geode 1.7.0 release branch created

2018-08-29 Thread Nabarun Nag
Please continue marking fixed versions as 1.7.0 till the release branch is ready. The following tickets' fixed versions have been changed to 1.7.0 from 1.8.0 GEODE-5579 GEODE-5646 GEODE-5648 Regards Nabarun Nag On Wed, Aug 29, 2018 at 2:20 PM Nabarun Nag wrote: > Thank you Sai, > We ar

Re: [DISCUSS] Apache Geode 1.7.0 release branch created

2018-08-29 Thread Nabarun Nag
Thank you Sai, We are also waiting on documentation to be updated to reflect the changes made by these resolved JIRAs. Once that is completed, I believe that we will be ready for the new branch. Regards Nabarun Nag On Wed, Aug 29, 2018 at 11:45 AM Sai Boorlagadda wrote: > I have merged GE

Re: [DISCUSS] Apache Geode 1.7.0 release branch created

2018-08-28 Thread Nabarun Nag
Hi Juan, GEODE-5618 as PR#2360 has been merged in to develop. The new branch has not yet been created hence this fix will be in 1.7.0 Regards Nabarun Nag On Tue, Aug 28, 2018 at 12:33 AM Juan José Ramos wrote: > Hello team, > > Can we also include GEODE-5618 in the next release?.

Re: [DISCUSS] Apache Geode 1.7.0 release branch created

2018-08-27 Thread Nabarun Nag
I completely agree. Once the branch is created, it will undergo all compatibility and upgrade tests. The commit that you have mentioned will be reverted in 1.7.0, as well as any related commits Regards Nabarun Nag On Mon, Aug 27, 2018 at 1:34 PM Bruce Schuchardt wrote: > I don't think i

Re: [DISCUSS] Apache Geode 1.7.0 release branch created

2018-08-27 Thread Nabarun Nag
270 GEODE-5269 GEODE-5267 GEODE-5265 GEODE-5255 GEODE-5249 GEODE-5237 GEODE-5223 GEODE-5220 GEODE-5186 GEODE-5157 GEODE-4965 GEODE-4791 GEODE-4726 GEODE-4614 GEODE-4593 GEODE-4336 GEODE-3530 GEODE-3505 GEODE-1866 GEODE-1357 On Mon, Aug 27, 2018 at 12:11 PM Nabarun Nag wrote: > @Bruce those c

Re: [DISCUSS] Apache Geode 1.7.0 release branch created

2018-08-27 Thread Nabarun Nag
@Bruce those changes were done when 1.7.0 release process was in-progress, and a release branch was already created. But we stopped that process mid way. This happened in May 2018. We are planning to rebase the 1.7.0 brach with the current develop pretty soon. Regards Nabarun On Mon, Aug 27, 2018

Re: [DISCUSS] Apache Geode 1.7.0 release branch created

2018-08-27 Thread Nabarun Nag
I am about to change the fixed version in GEODE JIRAs to 1.7.0 for those tickets which are marked closed or resolved with 1.8.0 as the fix version. Please do let me know if there are any concerns. The new release branch has not been created yet. Regards Nabarun Nag On Mon, Aug 27, 2018 at 10:17

Re: [DISCUSS] Apache Geode 1.7.0 release branch created

2018-08-24 Thread Nabarun Nag
I will be rebasing the release branch with develop, to bring in all the improvements/ enhancements that went in in the past few months. I am waiting on the tickets mentioned in this thread to be closed to start on a fresh release branch. Regards Nabarun Nag On Fri, Aug 24, 2018 at 12:20 PM

Re: [DISCUSS] Apache Geode 1.7.0 release branch created

2018-08-21 Thread Nabarun Nag
I will wait for a day to give all developers sometime to commit any new fixes into develop that is needed in 1.7.0. Please do let me know if there is any concern. Regards Nabarun Nag On Tue, Aug 21, 2018 at 12:42 PM Nabarun Nag wrote: > Yeah , I can continue with the release manager tasks.

  1   2   >