Re: [DISCUSS] Graduation

+1! On Wed, Oct 26, 2016 at 12:36 PM, Nabarun Nag wrote: > +1 > On Wed, Oct 26, 2016 at 12:07 PM Mark Bretl wrote: > > > +1 > > > > On Wed, Oct 26, 2016 at 12:04 PM, Ashvin A wrote: > > > > > +1 > > > > > > On Tue, Oct 25, 2016 at 5:25

Re: M3 status?

Are the remaining branding JIRAs planned in M3? I saw gfsh help fixed [1] but others (JMX, REST end-points) are still open. Thanks, Nitin [1] http://issues.apache.org/jira/browse/GEODE-985 On Thu, Jul 7, 2016 at 1:38 PM, William Markito wrote: > Thanks for the update

Re: Donation of Geode Docs [was: Re: What will it take to release geode 1.0?]

>From a technology readiness perspective, hosting the docs on a different (Apache) site should not be too hard; I've built the docs locally and on AWS without any major issues. Irrespective of the hosting location, the content license needs to be fixed - as per the current github repo [1], it

Re: New committer and PPMC Member: Nabarun Nag

Congrats and welcome! On Tue, Jun 14, 2016 at 3:33 PM, Jason Huynh wrote: > Congrats! > > On Tue, Jun 14, 2016 at 3:22 PM, Dave Barnes wrote: > > > Welcome, Nabarun! > > > > On Tue, Jun 14, 2016 at 3:07 PM, Dan Smith > >

Re: What will it take to release geode 1.0?

could start with GEODE-985 unless someone is already working on it. Thanks, Nitin On Wed, May 11, 2016 at 12:33 PM, Anthony Baker <aba...@pivotal.io> wrote: > Thanks Nitin! AFAIK we need new JIRA’s for those issues. > > Anthony > > > On May 11, 2016, at 11:49 AM, Nitin

Re: [ANNOUNCE] Donation of GemFire native client code

Great news indeed!! Now that this code is on its way to be contributed, would it make sense to include node-gemfire driver (BSD license) and manage it as part of Geode? Makes it a fairly compelling stack for javascript developers... Nitin On Thu, May

Re: What will it take to release geode 1.0?

Sorry missed this thread last week. +1 on package-renaming to be picked-up after 1.0 release. However, the community should try to fix any visible Gemfire references. Following are a few I know of: (a) Rename Gemfire to Geode on gfsh commands and help (global replace in CliStrings class; cleaner

Re: M2 release update

+1 Thanks Dan and everyone for contributing towards the release!! Nitin On Fri, Apr 22, 2016 at 11:34 AM, Anilkumar Gingade wrote: > Great... > > Thanks Dan; for being the release manager and successfully getting the > release out...good work... > > -Anil. > > > On Fri,

Re: Review Request 46216: GEODE-1226: Adding a flag to prompt for a password if required

passwords? May want to add logic to abort after a set number of retries. - Nitin Lamba On April 14, 2016, 5:54 p.m., Dan Smith wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache

Comparing maven deps vs lib/ dir

+1 Great progress indeed!! On Tuesday, April 12, 2016, Anthony Baker wrote: > See [1]. Only trouble I had was excluding log4j-slf4j-impl. Without that > I hit a startup error complaining about logging conflicts. > > compile

Re: Jira ticket workflow

+1, I remember Anthony helping with JIRA status updates (Resolved > Closed) after M1 release. Also, we should find-out if JIRA bulk-updates can be enabled for the release manager. Nitin On Tue, Apr 12, 2016 at 10:40 AM, Bruce Schuchardt wrote: > //I think the ticket

Geode - Sonar integartion

A ticket was created for this [1], however, need Geode's build.gradle file on Jenkins to be modified for Sonar... see GEODE-64 [2] For reference, the old infra ticket is INFRA-9616 [3]. @Anthony, @Mark, @Dan: Anybody wants to help here? Don't think I have the right levels of access. Thanks,

Re: [GitHub] incubator-geode pull request: GEODE-1163 Fix branding in Swagger U...

sh your changes to the apache > repository. Use this url and your apache credentials: > > https://git-wip-us.apache.org/repos/asf/incubator-geode.git > > -Dan > > On Fri, Apr 8, 2016 at 7:35 PM, Nitin Lamba <nitin.la...@gmail.com > <javascript:;>> wrote: > &g

Re: [GitHub] incubator-geode pull request: GEODE-1163 Fix branding in Swagger U...

+contributions > > On Fri, Apr 8, 2016 at 3:34 PM, Nitin Lamba <nla...@apache.org> wrote: > > > Any takers for merging this in? Don't think I could as I created the pull > > request :) > > > > Thanks, > > Nitin > > > > On Thu, Apr 7, 2

Re: [discuss] Install Google Analytics for tracking activity on geode.incubator.apache.org

Done [1]. Nitin [1] https://issues.apache.org/jira/browse/INFRA-11619 On Wed, Apr 6, 2016 at 7:05 PM, Roman Shaposhnik <ro...@shaposhnik.org> wrote: > On Wed, Apr 6, 2016 at 5:36 PM, Nitin Lamba <nitin.la...@gmail.com> wrote: > > +1 > > > > Another option (men

Re: New committer and PPMC member: Dave Barnes

Welcome Dave! On Tue, Apr 5, 2016 at 3:15 PM, Jianxia Chen wrote: > Welcome Dave! > > On Tue, Apr 5, 2016 at 2:59 PM, William Markito > wrote: > > > Please welcome Dave Barnes as a new committer to the Geode project and we > > are pleased that he accepted!

Re: [discuss] Install Google Analytics for tracking activity on geode.incubator.apache.org

+1 Another option (mentioned in today's Geode Clubhouse), is to have Geode at http://analysis.apache.org Most of the projects are TLPs but I could find at least one valid Incubator: https://analysis.apache.org/dashboard/index/201547 @rvs, would you know who has the karma to get geode added on

Re: Podling Report Reminder - April 2016

t;> - There are now X subscribers on the dev and X on the user mailing > > lists. > > >> > > >> - Community events: > > >> > > >> - January 2016: > > >> > > >>- FOSDEM 2016 in Brussels: > > >> > &

Re: [GitHub] incubator-geode pull request: GEODE-1163 Fix branding in Swagger U...

I've fixed the email On Monday, April 4, 2016, sbawaska wrote: > Github user sbawaska commented on the pull request: > > > https://github.com/apache/incubator-geode/pull/122#issuecomment-205461981 > > +1 > A minor nitpick, could you please make the support email

Re: Wan

Amdocs policy statement, you may > > review at http://www.amdocs.com/email_disclaimer.asp > > > > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > you may review at http://www.amdocs.com/email_disclaimer.asp > -- *Nitin Lamba* | (763) 360-0539 | www.linkedin.com/in/nitinlamba

JVSD status

Just wanted to know where this is at. Don't see any JIRA activity [1] since mid-Feb though all the subtasks are resolved. Is JVSD working but currently parked on a feature branch [2]? Thanks, Nitin [1] https://issues.apache.org/jira/browse/GEODE-78 [2]

Re: [DISCUSS] M2 issues - what's included and how we're tracking them

+1 for fixed version Typical JIRA workflow would expect the Assignee to put fixed version AFTER the issue is resolved. There's another field 'Target Version' which is used for planning, however, in the interest of simplicity, we can use Fixed Version. As for M2, we already have a lot of new

Re: Can we close GEODE-36 ? (Gfsh renaming)

+1 BTW, love Anthony's backronym[1] for gfsh! Nitin [1] https://en.wikipedia.org/wiki/Backronym From: Kirk Lund Sent: Wednesday, March 16, 2016 8:05 AM To: dev@geode.incubator.apache.org Subject: Re: Can we close GEODE-36 ? (Gfsh

Re: Comparing distributed members IDs for equivalency.

+1 Not sure if my finding is related to this issue but every time I start a locator on my mac without specifying bind address, the Locator and Manager services do not bind to localhost consistently. Following are the steps to reproduce: gfsh> start locator --name=locator ... gfsh> exit Start

Re: RM rotation for releases

+1 Great idea! @Dan, happy to help. I'll update the wiki with some of the e-mails/ learnings too. Nitin On Wed, Mar 16, 2016 at 5:29 PM, Dan Smith wrote: > I can give it a shot for M2. I'll have to lean on Nitin and Anthony to > figure out how things worked in the last

Re: New Committer to Apache Geode: Nitin Lamba

016, at 11:11 AM, Greg Chase <g...@gregchase.com> wrote: > > Please welcome *Nitin Lamba* as a new committer to the Apache Geode > project! > > Nitin has already been an avid contributor to the enhancement of Apache > Geode, most notably serving as the release manager for

Re: In preparation for Apache Geode - looking for topic leads for Geode Features Discussions

Seems there aren't any takers for the low hanging fruit so I will take it! :) Hi Greg: please count me in for helping with the new contributor session. If anyone else is interested, happy to tag-team as well! Thanks, Nitin Sent from Outlook Mobile On Thu, Mar 3, 2016

Re: Scope for M2 release

Please try the link again... From: Nitin Lamba <ni...@ampool.io> Sent: Tuesday, March 1, 2016 3:07 PM To: dev@geode.incubator.apache.org Subject: Re: Scope for M2 release My bad - let me fix the filter and make it

Re: Scope for M2 release

ssions to see it though: JIRA Issues Macro: JIRA project does not exist or you do not have permission to view it. Anthony > On Mar 1, 2016, at 1:51 PM, Nitin Lamba <ni...@ampool.io> wrote: > > OK, I've added a couple of JIRA filters to extract all issues loaded in our &g

Re: Scope for M2 release

check it out and suggest if any specific attributes should be displayed or if the inclusion/ exclusion criteria should be changed. Nitin [1] https://cwiki.apache.org/confluence/display/GEODE/1.0.0-incubating.M2+%28Second%29+Release From: Nitin Lamba <

Re: Scope for M2 release

+1 I had recently updated the wiki page for completed JIRAs. Ideally, we should just have one place to update. Let me quickly research if there's a way to integrate the lists. Nitin From: Kirk Lund Sent: Tuesday, March 1, 2016 11:33

Re: Conributors.md

Hi Dor, >From the e-mail subject, is this question about capturing the list of >contributors on the Geode project? The website has a list of committers on the >community page [1]; perhaps a link to contribution guidelines (wiki) can be >created from there. Nitin [1]

Re: [DISCUSS] Merging of feature/GEODE-917 - renaming artifacts to geode-

+1 Agree with Anthony - all the artifacts in the /lib directory still read 'gemfire-XXX.jar'. If renaming is simple enough, it should be picked-up as part of this change. Nitin From: Anthony Baker Sent: Friday, February 19, 2016

Lucene function added by default

Hi, While starting-up a new geode cluster, I see that a lucene function is registered even before any regions are created. Following are the simple steps to reproduce it: ./bin/gfsh gfsh>start locator --name=Locator gfsh>start server --name=Server1 gfsh>list functions Member | Function

Re: [ANNOUNCE] Apache Geode (incubating) release 1.0.0-incubating.M1

AM Cc: dev@geode.incubator.apache.org Subject: Re: [ANNOUNCE] Apache Geode (incubating) release 1.0.0-incubating.M1 Nitin, thanks for all your work as Release Manager! Great job! Anthony > On Feb 8, 2016, at 10:47 AM, Nitin Lamba <ni...@ampool.io> wrote: > > The Apach

Re: [DISCUSS] Next Release Scope - version 1.0.0-incubating.M2

Then incorporation of WAN and CQ features. > > -- > Mike Stolz > Principal Engineer, GemFire Product Manager > Mobile: 631-835-4771 > > On Fri, Jan 29, 2016 at 12:26 PM, Nitin Lamba <ni...@ampool.io> wrote: > > > Thought of starting a separate thread to discus

Re: Build failed in Jenkins: Geode-nightly #359

dfx -e /caches -e /.gradle -e /wrapper > > > On Wed, Jan 27, 2016 at 6:58 AM, Nitin Lamba <ni...@ampool.io> wrote: > > > There was a bug that generated pulseVersion.properties file in the src > > tree. Dan has put in the fix yesterday and removed the rat ignore. &

[DISCUSS] Next Release Scope - version 1.0.0-incubating.M2

Thought of starting a separate thread to discuss next release scope. So far we have the following suggestions: Dan: - GEODE-823 - remove gemfire-joptsimple, gemfire-json, rename to geode-, other misc issues - GEODE-818 - clean up dependencies - GEODE-572 - generate public javadocs (part of

Re: Broken javadocs

Yes, there is. To re-enable strict javadoc checking in JDK8, you can remove this command line option present in build.gradle today: javadoc { options.addStringOption('Xdoclint:none', '-quiet') } Once it is removed, the build will fail. Last checked, it was generating more than 100

Re: Geode versions in Jira tickets

+1 To avoid the confusion, does it make sense to just delete this tag? Or perhaps rename/ reuse it to 1.1.0-incubating.M1 for the next feature release? We're in a bit of a clean-up mode right now so even though WAN, CQ and Pulse are big feature additions, we're still cleaning-up contributed

[VOTE] RC2: Apache Geode (Incubating) first Milestone release - v1.0.0-incubating.M1

All, This is the second release candidate of the first release for Apache Geode, version 1.0.0-incubating.M1. Thanks to all the community members to drive towards this milestone! It fixes the following issues:

Re: [VOTE] RC2: Apache Geode (Incubating) first Milestone release - v1.0.0-incubating.M1

The link to source tag got messed-up. Correct link below: https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;a=tag;h=refs/tags/rel/v1.0.0-incubating.M1.RC2 Thanks, Nitin From: Nitin Lamba <ni...@ampool.io> Sent: Wednesday, January 27, 2016

Re: Build failed in Jenkins: Geode-nightly #359

There was a bug that generated pulseVersion.properties file in the src tree. Dan has put in the fix yesterday and removed the rat ignore. However, seems the older generated file is still lying around - if you delete that file and clean the workspace, this issue should get fixed. Hope this

Re: Proposal: Move Events to a non-Repo website

+1 for data-driven event calendar! William's suggested solution is available as a jQuery plugin [1]. Nitin [1] http://www.jqueryscript.net/social-media/jQuery-Plugin-To-Display-Google-Calendar-Feeds-On-Your-Website.html From: William Markito

Re: Review Request 42736: GEODE-854: Put pulseversion.properties in generated-resources

Pulse jar is designed to work as a standalone jar so that it can be deployed separately from the locator. The interaction with the rest of the distributed system is through JMX only. Isn't this code change in PulseAppListener creating a 'gemfire-core' dependency so every pulse installation

Re: [VOTE] Apache Geode (Incubating) first Milestone release - v1.0.0-incubating.M1

n 20, 2016 at 1:45 PM, Nitin Lamba <ni...@ampool.io> wrote: > Sure. One benefit of defining subtasks is that subtasks have separate > issue numbers for traceability, and we can track the complete feedback with > a few JIRAs. Other mechanisms of using labels or explicit issue linki

Re: Pulse UI merged to develop

ouldn't even run those uiTest at all since it's excluded from the test tasks. Do open up your PulseUITest.java and see if it has those lines on top of the class: @Ignore @Category(UITest.class) If not, then your source is not up to date? On Fri, Jan 22, 2016 at 10:13 AM, Nitin Lamba <ni.

Re: Pulse UI merged to develop

review request accordingly. Thanks Thanks! Jinmei On Fri, Jan 22, 2016 at 9:07 AM, Nitin Lamba <ni...@ampool.io> wrote: > Thanks Jinmei. > > I tried running Pulse UI tests but ran into few issues, listed below: > > 1. Firefox version has been updated so Selenium jars also requires a n

Review Request 42659: GEODE-12 Update Selenium for latest FireFox (v43.x); Fix tests

v43.0.4 Thanks, Nitin Lamba

Re: Pulse UI merged to develop

Great progress - thanks Jinmei and Jens! Tried to build 'develop' on my machine and started Pulse - launched as expected. How does one launch UITests? I see those tests removed form build.gradle file that were worked on last year. As mentioned, Pivotal/ Gemfire branding on the UI is still not

Re: [VOTE] Apache Geode (Incubating) first Milestone release - v1.0.0-incubating.M1

Sorry have been away from my e-mails. @Roman, Greg, Mike: Yes, first time miss. Didn't see a timing guideline but now we know! It makes sense to wait until Friday, and ask for 72 hrs on the next RC VOTE. @Niall: Thanks a lot for your feedback! NOTICE and LICENSE files was somewhat of a known

Re: Creating a release (was Re: releaseType?)

C72C FB64 > > Source and binary distributions: > https://dist.apache.org/repos/dist/dev/incubator/geode/1.0.0-incubating.M1.RC1/ > > Maven staging repository: > https://repository.apache.org/content/repositories/orgapachegeode-1000/ > > > Thanks to Dan and William for the help! &

[VOTE] Apache Geode (Incubating) first Milestone release - v1.0.0-incubating.M1

This is the first release for Apache Geode, version 1.0.0-incubating.M1. Thanks to all the community members to drive towards this first milestone! It fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318420=12334248 *** Please download, test and

Re: Review Request 42333: GEODE-781: Update maven publishing to include signatures

> On Jan. 15, 2016, 5:46 p.m., Nitin Lamba wrote: > > Just noticed in the repo [1] that even PGP armor (.asc) files have md5 and > > sha1 hashes (*.asc.md5 and *.asc.sha1). Is that intentional? It seems > > something changed last night which is generating these addition

Re: Review Request 42233: GEODE-778: Remove grgit plugin to avoid build failures

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/42233/#review114211 --- Ship it! Ship It! - Nitin Lamba On Jan. 13, 2016, 4:11 a.m

Re: A few recommendations on how to produce our first RC

Thanks Roman, As per the earlier thread (subject: releaseType?) and Spring conventions, it seems that these milestone releases 'M#' come before release candidates 'RC#' and not together M#.RC#. So the expected release progression is: 1.0.0-incubating.M1 1.0.0-incubating.M2 ...

Re: Are we planning to publish Maven artifacts as well?

From: shaposh...@gmail.com <shaposh...@gmail.com> on behalf of Roman Shaposhnik <ro...@shaposhnik.org> Sent: Tuesday, January 12, 2016 10:01 AM To: dev@geode.incubator.apache.org Cc: Nitin Lamba Subject: Re: Are we planning to publish Maven artifacts as well? On Tue, Jan 12, 2016 at 6:15

Re: releaseType?

. Can someone with JIRA privs rename the 1.0.0-alpha1 version to 1.0.0-incubating.M1? Anthony > On Jan 11, 2016, at 11:59 AM, Nitin Lamba <ni...@ampool.io> wrote: > > +1 > > This should be trivial to update within JIRA. > > Anthony: if we have consensus, can you

Re: checksum files for distributions

Generating MD5 from the build script sounds like a great idea. Maybe I'm off here but doesn't the release signing process need stronger digest (SHA512)? More info here [1]. Thanks, Nitin [1] http://www.apache.org/dev/release-signing.html#sha-checksum

Re: releaseType?

suggested would not be published to a public Maven, or an "RC1" which would be published to a public Maven? On Mon, Jan 11, 2016 at 6:54 PM, Nitin Lamba <ni...@ampool.io> wrote: > Great! > > If we're good with the latest versions of NOTICE and LICENSE files, we're > about done wi

Re: releaseType?

t; Here’s my key but I’m not sure if it is sufficiently trusted yet: > > http://pgp.surfnet.nl/pks/lookup?op=vindex=abaker%40apache.org=on > > Anthony > > > On Jan 11, 2016, at 6:54 PM, Nitin Lamba <ni...@ampool.io> wrote: > > Great! > > If we're good with the late

Re: How are we numbering the first release of Apache Geode?

Just to close this - based on the related versioning thread, is the community in agreement with the upcoming release as 1.0.0-incubating.M1? Or do we need a formal vote on this? Thanks, Nitin From: Niall Pemberton Sent:

Re: Source distribution

Pemberton <niall.pember...@gmail.com> wrote: > > On Mon, Jan 4, 2016 at 10:43 PM, Nitin Lamba <ni...@ampool.io> wrote: > >> You're right Anthony - my bad. >> >> I did download the archive but accidentally opened the older tar.gz from >> April, 2015: >&g

Re: Ready for release candidate?

I like Dan's idea thought not sure if this would comply with git flow process or interpreting 'releases' more strictly. Is it possible to have one git branch for the release version (1.0.0) but use tags for different 'stages' alpha1, alpha2, RC, etc? In my mind, alpha1, alpha2, beta, RC are

Re: Source distribution

initial round of work on GEODE-610. I think we need input > and review from our mentors in order to mark it as resolved. If you have > other suggestions for how to continue that please let me know (and many > thanks to Niall for all the IP work!) > > > > I’ll push the DISCLAI

Re: Source distribution

stions for how to continue that please let me know (and many thanks to Niall for all the IP work!) I’ll push the DISCLAIMER changes now. Anthony > On Jan 6, 2016, at 4:52 PM, Nitin Lamba <ni...@ampool.io> wrote: > > The DISCLAIMER language looks accurate from [1]! > > Antho

Re: Assigning JIRA fix version

This would be true in general unless a JIRA has been resolved but the feature is still in a branch. Long-running branches and sub-task JIRAs would probably exhibit this behavior. I'll check JIRA tomorrow to see if I can find any counter examples. Thanks, Nitin

Re: LICENSE and NOTICE

I think Anthony meant 'feature/GEODE-610' branch: https://github.com/apache/incubator-geode/tree/feature/GEODE-610 - Nitin From: Michael Stolz Sent: Monday, January 4, 2016 9:55 AM To: dev@geode.incubator.apache.org Subject: Re:

Re: Source distribution

Thanks Anthony!! This is great progress as the community marches towards the first GEODE release! Besides the missing LICENSE and NOTICE files (you have a separate thread on GEODE-610), I noticed a few things in the src artifact: - The copyright updates are missing - It still has jgroups/ LGPL

Re: New Geode website - Latest changes

+1 Nice work indeed!! From: Udo Kohlmeyer Sent: Tuesday, December 8, 2015 5:34 PM To: dev@geode.incubator.apache.org Subject: Re: New Geode website - Latest changes +1.. Good work... On 9 Dec 2015 9:03 am, "William Markito"

Re: Include templates in the binary distribution?

+1 If these examples can span modules (using core and another module), then having a separate module (geode-examples) makes sense. -Nitin From: Dan Smith Sent: Monday, December 7, 2015 1:55 PM To: geode Subject: Re: Include templates

Re: Review of 1.0.0-alpha1 issues

Thanks Niall, GEODE-627 has been created and added to alpha1 scope. -Nitin From: Niall Pemberton Sent: Wednesday, December 2, 2015 11:36 PM To: dev@geode.incubator.apache.org Subject: Re: Review of 1.0.0-alpha1 issues Hi, It

Re: Geode 1.0.0 (alpha1): Open questions

lpha1): Open questions On Mon, Nov 30, 2015 at 11:36 AM, Nitin Lamba <ni...@ampool.io> wrote: > Wanted to start a thread capturing all the open (mostly process) questions > for the first alpha1 release: > > > - Does ASF have Pivotal's (or EMC's, VMware's, Gemstone's)

Re: Review of 1.0.0-alpha1 issues

Great discussion! So we're certainly cutting an initial (alpha1) release. Depending on its completeness/ quality, we can decide another alpha/ beta/ RC/ etc. @Anil: though I also prefer dot releases, Geode is somewhat different in that it is a mature codebase out of the gate. So maybe it

Geode 1.0.0 (alpha1): Open questions

Wanted to start a thread capturing all the open (mostly process) questions for the first alpha1 release: - Does ASF have Pivotal's (or EMC's, VMware's, Gemstone's) CCLA on file? Who can confirm? This is a legal requirement - Is the alternate (podling) release

Re: Review of 1.0.0-alpha1 issues

+1 I do have a fundamental question about versioning (rather what versions can be taken for voting/ approvals): Can an 'alpha' which has known issues (like GEODE-27 or GEODE-386 for apache namespace, etc) be taken all the way through the PMC process for approvals? Such a release will have to

Re: Review of 1.0.0-alpha1 issues

beta and final 1.0 release... -Anil. On Mon, Nov 30, 2015 at 1:33 PM, Anthony Baker <aba...@pivotal.io> wrote: > > On Nov 30, 2015, at 11:23 AM, Nitin Lamba <ni...@ampool.io> wrote: > > +1 > > I do have a fundamental question about versioning (rather w

Re: License headers on new source files

+1 Maybe it is obvious but having RAT as part of pre-checkin step would be desirable. -Nitin From: Anthony Baker Sent: Wednesday, November 25, 2015 11:41 AM To: dev@geode.incubator.apache.org Subject: Re: License headers on new

Failed test on latest develop branch

Encountered a test failure in the latest develop branch (ran './gradlew build'): :gemfire-core:test com.gemstone.gemfire.internal.AvailablePortJUnitTest > testWildcardAddressBound FAILED java.lang.AssertionError at org.junit.Assert.fail(Assert.java:86) at

Re: Review Request 40425: GEODE-301 Generate pulseversion.properties file from gradle build

omatically generated e-mail. To reply, visit: https://reviews.apache.org/r/40425/#review107428 --- On Nov. 18, 2015, 8:44 p.m., Nitin Lamba wrote: > > --- > This is an automatical

Re: Topic for Dec 17 Geode Clubhouse - what's coming in Apache Geode 1.0 Alpha?

uestions I encountered. Have a good weekend! Nitin From: Gregory Chase <gch...@pivotal.io> Sent: Friday, November 20, 2015 2:40 PM To: Michael Stolz; Nitin Lamba Cc: Dormain Drewitz; dev@geode.incubator.apache.org Subject: Re: Topic for Dec 17 Geode Clubh

Re: Javadoc changes in JDK 8

e, Nov 17, 2015 at 12:45 PM, Dan Smith <dsm...@pivotal.io> wrote: > I added another subtask to this JIRA to separate out the public API from > the internal API. > > -Dan > > On Tue, Nov 17, 2015 at 11:53 AM, Nitin Lamba <ni...@ampool.io> wrote: > >> I see.

Re: Review Request 40425: GEODE-301 Generate pulseversion.properties file from gradle build

/592e89d0-0c7e-4983-874c-cf52c6d4f598__Screen_Shot_2015-11-17_at_7.04.50_PM.png Updated Diff https://reviews.apache.org/media/uploaded/files/2015/11/18/1e81b7e7-249a-48d3-8cbe-de464a85f65f__patch.diff Thanks, Nitin Lamba

Re: Review Request 40425: GEODE-301 Generate pulseversion.properties file from gradle build

On Nov. 18, 2015, 7:50 p.m., Nitin Lamba wrote: > > Thanks for working on this! Thanks for the suggestions! I've resolved all of these. - Nitin --- This is an automatically generated e-mail. To reply, visit: https://reviews.apac

Re: Review Request 40395: GEODE-570 Fix javadoc gradle build command

r/40395/#review106931 --- On Nov. 17, 2015, 8:02 p.m., Nitin Lamba wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/40395/ > -

Review Request 40395: GEODE-570 Fix javadoc gradle build command

: geode Description --- Currently, the javadoc command errors out with JDK 8. The fix is to ignore strict checking. Diffs - build.gradle a186710 Diff: https://reviews.apache.org/r/40395/diff/ Testing --- Tested on local dev setup. Thanks, Nitin Lamba

Javadoc changes in JDK 8

Seems javadoc got a lot stricter with JDK 8: http://blog.joda.org/2014/02/turning-off-doclint-in-jdk-8-javadoc.html Consequently, the geode build errors out completely if you run javadoc. A simple fix should be able to

Re: Javadoc changes in JDK 8

o: dev@geode.incubator.apache.org Subject: Re: Javadoc changes in JDK 8 Related JIRA to 'fix' is GEODE-54, though not very well named. --Mark On Tue, Nov 17, 2015 at 11:40 AM, Nitin Lamba <ni...@ampool.io> wrote: > <http://blog.joda.org/2014/02/turning-off-doclint-in-jdk-8-javadoc.html>Seem

Review Request 40425: GEODE-301 Generate pulseversion.properties file from gradle build

, which will be picked-up with GEODE-511 (Fixing license headers and branding). File Attachments Pulse Screenshot https://reviews.apache.org/media/uploaded/files/2015/11/18/592e89d0-0c7e-4983-874c-cf52c6d4f598__Screen_Shot_2015-11-17_at_7.04.50_PM.png Thanks, Nitin Lamba

Re: Review Request 40395: GEODE-570 Fix javadoc gradle build command

esday, November 17, 2015 1:11 PM To: Dan Smith; Dick Cavender; Mark Bretl Cc: geode; Anthony Baker; Nitin Lamba Subject: Re: Review Request 40395: GEODE-570 Fix javadoc gradle build command This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/40395/ Ship it! W

Re: Geode Definition of Done (DOD)

ithout updated docs, code reformat, java doc updates (if any) -Anil. On Mon, Nov 16, 2015 at 5:02 PM, Nitin Lamba <ni...@ampool.io> wrote: > Captured on the Wiki - see below: > https://cwiki.apache.org/confluence/display/GEODE/Definition+of+Done > > Kirk: > I'm not sur

Re: Upcoming Apache Geode Roundtable on 11/17

dnesday, November 11, 2015 4:58 PM To: dev@geode.incubator.apache.org; Nitin Lamba Cc: u...@geode.incubator.apache.org Subject: Re: Upcoming Apache Geode Roundtable on 11/17 + Nitin specifically :) On Wed, Nov 11, 2015 at 3:59 PM, Amy Welch <awe...@pivotal.io<mailto:awe...@pivotal.io>>

Re: Review Request 39445: GEODE-12/GEODE-304 Fix Pulse tests (WIP)

445/diff/1/?file=1101146#file1101146line293> > > > > We should remove GemXD realated tests completely Removed Gemfire XD tests - see Patch_03 - Nitin --- This is an automatically generated e-mail. To

Re: Review Request 39445: GEODE-12/GEODE-304 Fix Pulse tests (WIP)

> On Oct. 19, 2015, 7:14 p.m., Mark Bretl wrote: > > pulse/build.gradle, line 43 > > <https://reviews.apache.org/r/39445/diff/1/?file=1101140#file1101140line43> > > > > gemfire-core is using version 4.12. Can the version be upgraded from > > 4.10 to

Re: Review Request 39445: GEODE-12/GEODE-304 Fix Pulse tests

Thanks, Nitin Lamba

Re: CI cleanup & squashaton

+1!! From: William Markito Sent: Friday, October 16, 2015 3:07 PM To: dev Subject: CI cleanup & squashaton Hey folks What about dedicate the next week to work specifically on CI and test issues in order to make our builds more

Re: Is REST APIs test coverage missing in geode codebase?

Hi John, Thanks for your note. Comments inline below: From: John Blum <jb...@pivotal.io> Sent: Friday, October 9, 2015 2:12 PM To: Nitin Lamba Cc: dev@geode.incubator.apache.org Subject: Re: Is REST APIs test coverage missing in geode codebase? A

Re: Geode Release 1.0.0

s, etc) in subsequent releases. Things we have to fix, IMO: GEODE-77 GEODE-18 Everything else can get pushed to alpha2. Thoughts? Anthony > On Oct 9, 2015, at 12:09 PM, Nitin Lamba <ni...@ampool.io> wrote: > > Thanks Dan, > > All, > > The A

Re: Is REST APIs test coverage missing in geode codebase?

Hi, Trying to revive this thread after a few months - does the Developer REST APIs have any tests, like those included in Management REST APIs? Also, management REST APIs should ideally be secured for release as it creates a vulnerability on the locator node - starts the REST APIs giving full

Re: Propose changing check to only depend on UnitTest

+1 . Initial dev experience needs to be frictionless... :) From: Bruce Schuchardt Sent: Thursday, October 1, 2015 4:56 PM To: dev@geode.incubator.apache.org Subject: Re: Propose changing check to only depend on UnitTest +1 Le

  1   2   >