Re: [DISCUSS] Graduation

Hi! we're at a final step of formal voting that is now going on over at general@incubator: http://markmail.org/thread/hztte5f6meoluz2v Please consider casting your vote there as well. Thanks, Roman. On Tue, Oct 25, 2016 at 5:25 PM, Roman Shaposhnik <r...@apache.org> wrote

Re: [DISCUSS] Graduation

in on general@incubator. Thanks, Roman. On Tue, Oct 25, 2016 at 5:25 PM, Roman Shaposhnik <r...@apache.org> wrote: > Hi! > > with the 1.0.0-incubating release officially out (huge kudos > to the team!) I think it is time we officially start our graduation > discussion. Pr

Re: Apache policy on files types allowed in source code

On Wed, Nov 2, 2016 at 1:16 PM, Kirk Lund wrote: > I'd like to read up on what's allowed and disallowed regarding file types > in Apache source code. Does anyone have any links to get me started? The only distinction that ASF makes is binaries vs. source files. The source code

Re: [ANNOUNCE] Apache Geode 1.0.0-incubating released

Awesome news! Congrats! Roman. On Tue, Oct 25, 2016 at 3:33 PM, Swapnil Bawaskar wrote: > The Apache Geode team is proud to announce Apache Geode release > 1.0.0-incubating. > > Apache Geode (incubating) is a data management platform that provides a > database-like

[DISCUSS] Graduation

Hi! with the 1.0.0-incubating release officially out (huge kudos to the team!) I think it is time we officially start our graduation discussion. Process-wise graduation consists of drafting a board resolution, getting it approved by the IPMC and finally submitting it to the ASF board's

Re: Hosting the docs (was Re: [VOTE] Release Apache Geode (incubating) 1.0.0-incubating - RC2)

On Mon, Oct 17, 2016 at 10:57 AM, Anthony Baker wrote: > Since the geode docs have now been merged to the develop branch, let’s start > hosting them on http://geode.apache.org. Thoughts? Huge +1! Anything stopping you from pushing the first update and start maintaining it

Re: From Incubation to TLP

On Fri, Sep 30, 2016 at 10:57 PM, Greg Chase wrote: > With the number of hats you have Roman, you can satisfy any diversity > requirement... This may be helpful to fully understand the phenomenon: http://tinyurl.com/origin-of-shaposhnik Thanks, Roman.

Re: From Incubation to TLP

On Thu, Sep 29, 2016 at 12:22 AM, Niall Pemberton wrote: > On Thu, Sep 29, 2016 at 3:33 AM, Anthony Baker wrote: > >> Hi Niall! >> >> Thanks for your really helpful input. I agree that development of an >> active, stable, and diverse community that

Re: [ANNOUNCE] Donation of Geode documentation

On Fri, Sep 30, 2016 at 10:28 AM, Karen Miller wrote: > I'd love to see the docs included in 1.0. Huge +1 to the above! Thanks, Roman.

Re: Publishing of geode javadocs

On Fri, Aug 12, 2016 at 4:51 PM, Dan Smith wrote: > I'm not sure if we're publishing the nightly javadocs anywhere, but you can > build them from source. If you do a ./gradlew build, the external javadocs > are in geode-assembly/build/install/apache-geode/javadoc One solution

Re: Geode website tagged with minor Apache branding issue in audit

IANAD but why not put it into the menu banner on the left? IMHO, this will be a much more visually appealing layout. Thanks, Roman. On Fri, Jul 1, 2016 at 6:14 PM, William Markito wrote: > Thanks Niall for the feedback. > > Would something like this be good enough ?

Re: update website for WAN, CQ and native client

+1 LGTM! On Tue, Jun 21, 2016 at 1:55 PM, Swapnil Bawaskar wrote: > +1 > I am convinced. > Made the change: http://i.imgur.com/41w9yWm.png > > On Tue, Jun 21, 2016 at 11:54 AM, Gregory Chase wrote: > >> I'm +0 to "Multi-site", but like "multi-cluster"

Re: Apache Geode incubation

On Tue, Jun 21, 2016 at 7:39 PM, Niall Pemberton wrote: > On Tue, Jun 21, 2016 at 3:13 PM, Greg Chase wrote: > >> The community is of course thinking about it. That is the point of the >> Incubator program. >> >> However, I imagine we will be asking

Fwd: Low-hanging fruit - Geode

FYI. Thanks, Roman. -- Forwarded message -- From: Paul Merlin Date: Mon, Jun 13, 2016 at 12:54 AM Subject: Re: Low-hanging fruit - Geode To: d...@zest.apache.org Niclas Hedhman a écrit : > Hi, > At ApacheCon I ran into Apache Geode (incubating) people. That

Re: Please review / approve WAN Gateway blog at blogs.apache.org

https://blogs.apache.org/geode/entry/active_active_wan_based_replication On Fri, May 27, 2016 at 8:46 AM, Bruce Schuchardt wrote: > Hi Greg, can you post a link to the article? > > > Le 5/26/2016 à 6:26 PM, Gregory Chase a écrit : >> >> Greetings Mentors and people with

Re: Please review / approve WAN Gateway blog at blogs.apache.org

This looks great to me! Unless some other mentors object -- I'll publish tomorrow morning. Thanks, Roman. On Thu, May 26, 2016 at 6:26 PM, Gregory Chase wrote: > Greetings Mentors and people with special access, > I've posted a blog on Apache RFH on behalf of Bruce Schuchardt

Re: [ANNOUNCE] Donation of GemFire native client code

On Thu, May 19, 2016 at 11:17 AM, Nitin Lamba wrote: > 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?

Re: Geode Portfile for Mac Ports

Awesome work, but please consider calling it apache-geode. Thanks, Roman. On Tue, May 17, 2016 at 1:23 PM, Kevin Duling wrote: > Using the geode.rb file for Homebrew as a template, I was able to build a > Portfile for macports.org. > > Does anyone have any feedback before I

Re: Its been a year....

Hear! Hear! An amazing community journey! Here's to the TLP and world domination! ;-) Thanks, Roman. On Wed, Apr 27, 2016 at 11:31 AM, Anilkumar Gingade wrote: > Hi Geode, > > Thought of sharing this milestone... > > Wow...Its been a year...In last year ApacheCON (Apr

Re: Brew formulae for geode

Great news, but could you please call it apache-geode ? I'm not familiar with brew, but hope it is easy enough to rename the package. Thanks, Roman. On Sat, Apr 23, 2016 at 9:41 PM, Anthony Baker wrote: > If you use the Homebrew [1] package manager on OS X, you can now

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

On Wed, Apr 6, 2016 at 5:36 PM, Nitin Lamba wrote: > +1 > > Another option (mentioned in today's Geode Clubhouse), is to have Geode at > http://analysis.apache.org That'd be pretty sweet! > Most of the projects are TLPs but I could find at least one valid Incubator: >

Re: Podling Report Reminder - April 2016

On Wed, Apr 6, 2016 at 6:14 PM, Swapnil Bawaskar wrote: > Since the report is due today, I went ahead and updated the wiki > https://wiki.apache.org/incubator/April2016. > Let me know if anything needs to change while I can still change it :) Swapnil, this is totally fine

Re: New committer and PPMC member: Dave Barnes

Welcome to the project Dave! Thanks, Roman. 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! > > We appreciate all the patches he has already contributed and are

Re: Podling Report Reminder - April 2016

On Wed, Apr 6, 2016 at 5:22 PM, Swapnil Bawaskar wrote: > I found the following"Shepherd/Mentor notes" for our previous report > : > > For the next report: for me as a mentor (and perhaps for others on IPMC) > it is not

Re: Apache Open Source Mentoring Programme

I'm pretty sure it is open to podlings as well. You will have to keep IPMC in the loop, of course, but other than that -- it should be exactly the same. Thanks, Roman. On Wed, Apr 6, 2016 at 12:22 PM, William Markito wrote: > Can any one of the @mentors chime in on this

Re: [DISCUSS] Mnemonic incubator proposal

Hi Yanping! very interesting proposal indeed! I just wanted to introduce you to the Apache Geode (incubating) dev team and perhaps suggest some potential collaboration on the storage layer. Thanks, Roman, On Sun, Feb 21, 2016 at 11:47 AM, Wang, Yanping wrote: > Hi all >

Fwd: Google Summer of Code 2016 is coming

FYI. Please make sure to follow Ulrich's instructions and label the ideas in JIRA as he's askit to. It is extremely important for us since GSOC has been a really great way to grow (and retain!) new members of the community! I would really encourage at least 2 volunteers from every podling

Re: Apache compatibility with Eclipse license

On Wed, Feb 10, 2016 at 3:27 PM, Dan Smith wrote: > Be clear about which license your talking about - there is both an Eclipse > Public License and Eclipse Distribution License. Junit is licensed under > the Eclipse Public License. > > This page lists the EPL under WEAK

Re: 1.0.0-incubating.M1

First of all -- congrats on your first release -- this is a pretty big milestone! On Mon, Feb 8, 2016 at 9:36 AM, Kirk Lund wrote: > Is a 1.0.0-incubating.M1 release something that we can advertise outside of > the dev@geode list, blog about, etc? Yes, absolutely! Make sure to

NOTICE/LICENSE files updates

Hi! since there's been quite a bit of work around $subj lately, I wanted to share this link that has recently came up in a conversation on general@incubator: http://creadur.apache.org/whisker/ Thanks, Roman.

Re: RC2 is created

Great! Don't forget to restart a VOTE thread. On Wed, Jan 27, 2016 at 11:41 AM, Anthony Baker wrote: > Here are the details: > > Commit: > c26334542fa9e90daff5f58467d6e174b3e0f3e2 > > Tag: > rel/v1.0.0-incubating.M1.RC2 > > Signing key: > pub 4096R/C72CFB64 2015-10-01 >

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

On Mon, Jan 25, 2016 at 11:28 AM, Anthony Baker wrote: > Reviewing the feedback received so far on RC1 we have the following issues to > consider: > > 1) The binary NOTICE files needs additions for Spring and Netty [1]. > 2) The source distributions instructions specify use of

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

On Fri, Jan 22, 2016 at 5:51 PM, Anthony Baker wrote: > I suggest we extend the vote through Monday January 25 at 5pm PST to > clarify this question and any issues related to the binary NOTICE file. Sure. But if you could state your opinion on how the question I asked should

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

On Fri, Jan 22, 2016 at 4:32 PM, Anthony Baker wrote: > Originally, gemfire-json and gemfire-joptsimple were bundled to fix bugs > present in those libs. > There’s an intent to move away from the JSON parser entirely in GEODE-629. > Attached to that bug is a diff of the

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

On Wed, Jan 20, 2016 at 9:23 AM, Michael Stolz wrote: > What caused it to have such a short deadline? Did we do something to cause > it to be so short or is that the default and we just didn't know to > override it somehow? That's a good question for a release manager. Nitin?

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

That's great! Looking forward to a release VOTE. Thanks, Roman. On Tue, Jan 19, 2016 at 12:31 PM, Anthony Baker wrote: > Ok, the release candidate has been created. Here are the details: > > Commit: > e5a7b9aaa82d4c0a04e41febfd515056c4669001 > > Tag: >

Re: documentation's product name and version number

On Wed, Jan 13, 2016 at 5:51 PM, Karen Miller wrote: > Please take a look at the documentation. I believe that we'll comply, as > we use the full product name > directly followed by the version number in prominent places, such as on the > main landing page, and > at the top

Re: Jenkins config update needed

On Sat, Jan 16, 2016 at 9:41 AM, Anthony Baker wrote: > I’ve merged GEODE-781 onto develop which changes the way we publish artifacts > into maven. > Could someone with Jenkins privileges update our Geode-nightly job to change > the build tasks > to execute the

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

On Wed, Jan 13, 2016 at 12:18 PM, Justin Erenkrantz wrote: > Even if the release fails the vote, you shouldn't be reusing that > version again. And that's where the current suggested mode becomes super confusing *unless* we all agree not to use RC designation. Here's a

Re: documentation's product name and version number

On Wed, Jan 13, 2016 at 5:39 PM, Karen Miller wrote: > I've modified the Geode documentation to list 'Apache Geode' Not to nitpick, but we need to make sure (incubating) nomenclature is reasonably visible. You don't have to search-n-replace all of it but including it in a few

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

On Wed, Jan 13, 2016 at 5:48 PM, John Blum wrote: > Also, there is not as much ceremony around the release process, which is > highly automated. Part of it is SMOP frankly (which Anthony is doing very nicely) part of it is infosec considerations (like not allowing robots to

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

On Wed, Jan 13, 2016 at 10:23 AM, Anthony Baker wrote: > Doesn’t uploading artifacts to Maven require credentials? > I assume that issuing a `gradle publish` command will fail. What is the > recommended approach? Just follow the document I sent out and try it. There's no

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

On Tue, Jan 12, 2016 at 6:15 AM, Anthony Baker wrote: > Yes...any reason not to do this? Just wanted to make sure. Nitin, in that case, as an RM you'd have to stage the Maven bits and include the link to the staging repository into the VOTE thread. Just make sure to follow

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

On Tue, Jan 12, 2016 at 11:06 AM, Nitin Lamba wrote: > 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

Re: releaseType?

Seems like our emails have crossed. At this point you need to assemble a few trusted keys (yours, Nitin's, Mark's and perhaps a few other folks' as the minimum set) into a single key file and make it available in SVN tree that manages ASF releases. I suggest opening a GEODE jira asking folks to

Are we planning to publish Maven artifacts as well?

Hi! I'm catching up with a few threads on release mechanics and I just wanted to ask this question explicitly: are we planning to also push binary convenience artifacts of geode into ASF Maven repository (and thus, by extension, to Maven central) as part of the release process? Thanks, Roman.

Re: releaseType?

On Mon, Jan 11, 2016 at 7:25 PM, Nitin Lamba wrote: > Yes, this version is still M1. > > This is for public key server, not the artifacts per se. It is actually for both. A public key server is just a short-hand for somebody to retrieve your keys, however, a PMC managed keyfile

Fwd: Git status update

FYI. Please note that for your first upcoming releases there's an extra requirement for tag naming. Thanks, Roman. -- Forwarded message -- From: David Nalley Date: Sun, Jan 10, 2016 at 10:00 AM Subject: Git status update To: "infrastruct...@apache.org"

A few recommendations on how to produce our first RC

Hi! here's a few recommendation on how to produce your first RC. Basically your MVP of sorts should be the following set of files: archive: geode-1.0.0-incubating.M1-src.tar.gz GPG sig: geode-1.0.0-incubating.M1-src.tar.gz.asc MD5 sum: geode-1.0.0-incubating.M1-src.tar.gz.md5

Re: releaseType?

Note, that in ASF the RCs are NOT published into public Maven repo and are generally not disclosed ouside of the dev. community. Thanks, Roman. On Fri, Jan 8, 2016 at 10:48 AM, John Blum wrote: > For clarification, the "RELEASE" version qualifier is only used for the > final

Re: Open pull requests

On Fri, Jan 8, 2016 at 5:38 PM, William Markito wrote: > Well, if we still have some remaining PR's open that are not being closed > properly by the merges, let's ask asf infra to close them, no big deal. Why bother INFRA? Why not ask originators of PRs to close them?

Re: Propose new committer - Jinmei Liao

On top of great advice from Niall let me remind everybody of two things: 1. Our private@geode subscription stands at 29 right now, compared to many more initial committers 2. If you happen to be on the list of initial committers make sure to subscribe to the private mailing list by

Re: Source distribution

On Wed, Jan 6, 2016 at 8:04 PM, Anthony Baker wrote: > Those dirs only get created on a Jenkins build since Jenkins sets > GRADLE_HOME_DIR to the workspace (I know this has been fixed in > recent Gradle plugins but I can’t tell which version of the plugin ASF is > using). So

Re: Source distribution

On Wed, Jan 6, 2016 at 8:17 PM, Anthony Baker wrote: > Yep. We can exclude those dirs from the source distribution if needed. Great! > Are we using Jenkins to create the release build? That's actually up to you guys. It is totally possible for a RM to just create it by hand

Re: Ready for release candidate?

Let me share what I typically see in high velocity ASF projects (Hadoop, etc.) We *may* be talking about the same thing though ;-) On Wed, Jan 6, 2016 at 8:27 PM, Anthony Baker wrote: > What I’m thinking (but please correct me): > > 1) Create release branch > 2) Do stuff on

Re: January 2016 Report

> >>> > >>> > >>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=92=planning.nodetail >>> > >>> > - Builds now runs Apache RAT for license audit thanks to a Gradle >>> plugin. >>> > (GEODE-608) >>

Re: [GitHub] incubator-geode pull request: Enabling direct reporting on Geode's...

On Mon, Dec 28, 2015 at 4:31 PM, Dave Barnes wrote: > I like having a functional button above the fold. > Is this too easy? That's actually super easy. In fact you don't even need to change the website code -- it happens on the side of customizing your Issue Collector over at

Re: [GitHub] incubator-geode pull request: Enabling direct reporting on Geode's...

On Mon, Dec 28, 2015 at 7:23 PM, William Markito wrote: > +1 So... shall I commit? ;-) Thanks, Roman.

Fwd: [GitHub] incubator-geode pull request: Enabling direct reporting on Geode's...

closes #66 commit 499de3fe4e3f850ecfdc53829f6b46ce8b9e3664 Author: Roman Shaposhnik <r...@apache.org> Date: 2015-12-28T23:57:25Z Enabling direct reporting on Geode's website --- If your project is set up for it, you can reply to this email and have your reply appear on Gi

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

What exactly do you want to debug? In general, we don't give Jenkins admin karma out. Thanks, Roman. On Mon, Dec 14, 2015 at 1:40 PM, Anthony Baker wrote: > Can I get jenkins admin privs? I’m trying to debug this failure. Thanks! > > Anthony > > > On Dec 12, 2015, at 8:16

Re: Include templates in the binary distribution?

On Mon, Dec 7, 2015 at 1:55 PM, Dan Smith wrote: > At the very least, it seems like this code should move somewhere that > indicates it's an example, rather than test code. Maybe we should create a > new gradle module gemfire-examples? Or at least move this to a different >

Re: New Geode website - Latest changes

On Mon, Dec 7, 2015 at 4:47 PM, Dave Barnes wrote: > change "karma" to "good karma". Good point! I guess you know your samsara well ;-) Thanks, Roman.

Re: removing the license from jgroups configuration files

On Sat, Dec 5, 2015 at 7:01 PM, Niall Pemberton <niall.pember...@gmail.com> wrote: > On Sat, Dec 5, 2015 at 1:50 AM, Roman Shaposhnik <ro...@shaposhnik.org> > wrote: > >> On Fri, Dec 4, 2015 at 10:59 AM, Dan Smith <dsm...@pivotal.io> wrote: >> > If it rea

Re: removing the license from jgroups configuration files

On Fri, Dec 4, 2015 at 9:35 AM, Bruce Schuchardt wrote: > Well, we don't have it in the log4j2.xml configuration file so I don't see > why we need it in the JGroups configuration file. I'm afraid that while log4j2.xml configuration file clearly fits the description of

Re: removing the license from jgroups configuration files

On Fri, Dec 4, 2015 at 10:59 AM, Dan Smith wrote: > If it really comes to it, we could optimize the xml files as part of the > build process. So the checked in code would have the comments, formatting, > etc. but the version in the jar would be stripped. I think this is the

Re: removing the license from jgroups configuration files

Is this really that big of a deal? I presume this affects startup only. Thanks, Roman. On Thu, Dec 3, 2015 at 12:09 PM, Bruce Schuchardt wrote: > Would it be OK if I remove the Apache license from the jgroups XML > configuration files? > > There are two of them and one

FOSDEM 2016 - take action by 4th of December 2015

As most of you probably know FOSDEM 2016 (the biggest, 100% free open source developer conference) is right around the corner: https://fosdem.org/2016/ We hope to have an ASF booth and we would love to see as many ASF projects as possible present at various tracks (AKA Developer rooms):

Re: Geode on OSv & Seastar?

On Wed, Nov 25, 2015 at 6:39 AM, James Thornton <ja...@jamesthornton.com> wrote: > Hello - > > Roman Shaposhnik gave a talk on OSv (http://osv.io/) at CF Summit 2014: > > Pivotal - OSv: Probably the Best OS for Cloud Workloads You've Never Heard > Of (CF Summit 2014) &

Re: Final updates to Geode Website - Ready ?

-1 Incubator disclaimer has to be moved to the About the Project section (or otherwise be made more visible). Thanks, Roman. On Wed, Nov 25, 2015 at 8:33 AM, Gregory Chase wrote: > -1 > > I don't see some of the verbiage I had added (and my bad if I failed to > notice this

Re: License headers on new source files

Honestly, I though you guys integrated RAT already. Not that it is a rule or anything, but for any Java-based project the easiest way to entice mentors to review your stuff is to provide RAT integration via the build system. I'd say this is close to a must before our first release. Thanks,

Re: Apache Geode & Yarn

Since Geode is a long-running service, wouldn't it make sense to have Apache Slider (incubating) as an integration point instead of pure Yarn? Thanks, Roman. On Tue, Nov 17, 2015 at 12:05 PM, Ashvin A wrote: > Hi Sandesh, > > If I remember correctly, Geode on YARN has not

Re: Delete feature/GEODE-409?

On Thu, Nov 5, 2015 at 2:46 PM, Ashvin A wrote: > I have merged the branches. But I could not delete branch GEODE-409 > following the instructions on > https://cwiki.apache.org/confluence/display/GEODE/Developer+Workflow > > git push --delete origin feature/GEODE-409 > remote:

Re: Graduation concerns

On Wed, Nov 4, 2015 at 8:26 PM, Niall Pemberton <niall.pember...@gmail.com> wrote: > On Wed, Nov 4, 2015 at 7:13 PM, Roman Shaposhnik <r...@apache.org> wrote: > >> To echo Caleb's post to the HAWQ ML: >> >> In case you haven't been watching the Apache general li

Graduation concerns

To echo Caleb's post to the HAWQ ML: In case you haven't been watching the Apache general list there is an interesting thread on the Apache Sentry project and their graduation from incubator. http://mail-archives.apache.org/mod_mbox/incubator-general/201511.mbox/browser Lots of discussion on

Re: Geode Definition of Done (DOD)

First of all, I'm a huge +1 of having it all written down on a wiki. An additional benefit of that checklist is that then you can use it as a criteria for pulling functionality from feature branches into the 'golden branch'. I've seen this done very successfully in some of the other projects.

Re: Releasing Geode (was Re: September 2015 Report)

On Thu, Sep 10, 2015 at 10:14 PM, Nitin Lamba wrote: > Great suggestions Anthony! > > For starters, can I get PM rights in Geode JIRA? I'll take care of the JIRA karma for you shortly. What's your JIRA ID, btw? > I should then be able to make these changes fairly quickly. >

Re: Releasing Geode (was Re: September 2015 Report)

On Thu, Sep 10, 2015 at 10:01 AM, Ashvin A wrote: > http://www.apache.org/dev/release-publishing.html#release_manager > > *"The common practice at Apache is for a single individual to take > responsibility for the mechanics of a release. That individual is called > the 'release

Fwd: Project Jigsaw: Early-Access Builds available on jdk9.java.net/jigsaw

FYI -- Forwarded message -- From: Rory O'Donnell Date: Wed, Sep 9, 2015 at 10:18 AM Subject: Project Jigsaw: Early-Access Builds available on jdk9.java.net/jigsaw To: ga...@16degrees.com.au, strub...@yahoo.de Cc: rory.odonn...@oracle.com, Dalibor Topic

Re: Releasing Geode (was Re: September 2015 Report)

On Mon, Sep 7, 2015 at 12:39 PM, Anthony Baker wrote: > As Justin mentioned, we need to make progress towards our first Geode release. > If we define that initial release as an alpha-quality artifact that we can > rapidly iterate on, > we can narrow the scope down to just

Re: DRAFT of August report

ation tests now pass on the feature/GEODE-77 branch. > Good progress has also been made on stabilizing CI, by fixing various > intermittent failures in integration tests. > > ** Date of last release:* > >N/A - Just nightly builds. > > *Signed-off-by:* > [ ](geode) Konstantin Boudnik > [ ](geode) Chip Childers > [ ](geode) Justin Erenkrantz > [ ](geode) Jan Iversen > [ ](geode) Chris Mattmann > [ ](geode) William A. Rowe Jr. > [ ](geode) Henry Saputra > [ ](geode) Roman Shaposhnik

Re: GEODE-77 status

On Tue, Aug 25, 2015 at 1:08 PM, Anthony Baker aba...@pivotal.io wrote: The work Bruce mentioned is proceeding on the GEODE-77 feature branch. On that branch the gemfire-jgroups project containing the LGPL source has been removed from the build (settings.gradle) but is still present in the

Re: Getting blog posts posted onto blogs.apache.org/geode

Hi Vincent! turns out your were not part of the original batch of folks who were given permissions to work on the blog: https://issues.apache.org/jira/browse/INFRA-9764 If you want to get credentials feel free to file an INFRA issue (and reference this email thread as a reason you're asking

Re: July Incubator Report

Awesome! I've sent a note to the IPMC. Thanks, Roman. On Mon, Aug 17, 2015 at 1:02 PM, William Markito wmark...@pivotal.io wrote: Folks, since it looks like we should have actually sent our report on July and also to make it easier for everyone to track the project status and numbers, I've

Re: Weird networking behavior on Amazon EC via OSv deployment

On Mon, Aug 17, 2015 at 5:40 PM, Xiaojian Zhou gz...@pivotal.io wrote: This error msg actually is not the root cause of the issue. To avoid the error msg, you can modify sysctl.conf of your instance to add 2 lines: # unicast buffer size net.core.rmem_max = 2096304 net.core.wmem_max = 2096304

Re: So is it time to dump Hipchat and move to Geode conversations to Slack?

Actually as it happens Slack's desire to be an 'email killer' makes it rather unpopular with ASF as I found out. More details here: https://mail-archives.apache.org/mod_mbox/community-dev/201508.mbox/%3C0A45B62D-00FA-4F66-B357-E0240F9E65A1%40gmail.com%3E Thanks, Roman. On Fri, Aug 14,

Re: YCSB driver for Geode

at 2:23 PM, Roman Shaposhnik ro...@shaposhnik.org wrote: On Thu, Aug 13, 2015 at 1:54 PM, William Markito wmark...@pivotal.io wrote: Hi Roman, There is the cache and client-cache xml. http://gemfire.docs.pivotal.io/latest/userguide/reference/topics/elements_ref.html Sure. What I'm

Re: YCSB driver for Geode

On Thu, Aug 13, 2015 at 1:54 PM, William Markito wmark...@pivotal.io wrote: Hi Roman, There is the cache and client-cache xml. http://gemfire.docs.pivotal.io/latest/userguide/reference/topics/elements_ref.html Sure. What I'm asking is: what is the most reasonable content of cache.xml that

Re: YCSB driver for Geode

On Thu, Aug 13, 2015 at 1:07 PM, Jacob Barrett jbarr...@pivotal.io wrote: Do you have a corresponding error message or indicator of it not being compatible? Exception in thread Thread-1 java.lang.IllegalStateException: You must use client-cache in the cache.xml when ClientCacheFactory is used.

Re: YCSB driver for Geode

/ On Thu, Aug 13, 2015 at 1:16 PM, Roman Shaposhnik ro...@shaposhnik.org wrote: On Thu, Aug 13, 2015 at 1:07 PM, Jacob Barrett jbarr...@pivotal.io wrote: Do you have a corresponding error message or indicator of it not being compatible? Exception in thread Thread-1

Re: Request to post Geode security article

the blog site only accepts HTML. For some reason I don't have access to upload or apply images however. Someone else with more access will need to finish this off. -Greg On Wed, Jul 15, 2015 at 5:46 PM, Roman Shaposhnik ro...@shaposhnik.org wrote: On Tue, Jul 14, 2015 at 9:36 AM, Gregory

Re: Request to post Geode security article

On Tue, Jul 14, 2015 at 9:36 AM, Gregory Chase gch...@pivotal.io wrote: As I understand, someone has to post on your behalf now who has access to the blog. I think I am one such somebody, so let me see how to post it for you :) Yup ;-) Let me know if you guys need any help, but at this point

Re: Geode nightly build failures

On Fri, Jul 10, 2015 at 2:03 PM, Dan Smith dsm...@pivotal.io wrote: Looks like the nightly builds are up and running with all of the tests that we added with GEODE-8. There's actually not as much noise as I expected considering the tests are running in a new environment. Yeah! I was going to

Re: Where to place Spark + GemFire connector.

On Tue, Jul 7, 2015 at 10:34 AM, Anilkumar Gingade aging...@pivotal.io wrote: Agree...And thats the point...The connector code needs to catch up with spark release train; if its part of Geode then the Geode releases needs to happen as often as Spark release (along with other planned Geode

Re: Where to place Spark + GemFire connector.

On Tue, Jul 7, 2015 at 11:21 AM, Gregory Chase gch...@pivotal.io wrote: More important than easy to develop is easy to pick up and use. Improving the new user experience is something that needs attention from Geode. How we develop and provide Spark integration needs to take this into

Re: [DISCUSS] Fix / update intoductory training materials and labs for Apache Geode?

I think this could be pretty useful to the project. Please file a JIRA with the details from this email. Thanks, Roman. On Wed, Jul 1, 2015 at 12:43 PM, Gregory Chase gch...@pivotal.io wrote: Greetings Apache Geode committers, I wanted to bring this up for discussion before filing a JIRA. As

Re: [ANNOUNCE] YCSB 0.2.0 Release

Hi Sean! On Tue, Jul 7, 2015 at 8:46 PM, Sean Busbey bus...@cloudera.com wrote: On behalf of the development community, I am pleased to announce the release of YCSB version 0.2.0. Awesome news! * ~5 additional datastore bindings in experimental status (including GemFire) Obviously I'm

Re: Where to place Spark + GemFire connector.

On Thu, Jul 2, 2015 at 5:39 PM, Anthony Baker aba...@pivotal.io wrote: We are wondering wether to have this as part of Geode repo or on separate public GitHub repo? I think the spark connector belongs in the geode community, which implies the geode ASF repo. I think we can address the

Re: Geode podling report for review

Great report indeed! I've just signed off. On Mon, Jul 6, 2015 at 7:32 AM, William A Rowe Jr wr...@rowe-clan.net wrote: On Wed, Jul 1, 2015 at 4:20 PM, Kirk Lund kl...@pivotal.io wrote: Geode [...] Signed-off-by: [+1](geode) William A. Rowe Jr. Shepherd/Mentor notes: Nothing to

Re: Where to place Spark + GemFire connector.

On Mon, Jul 6, 2015 at 3:10 PM, John Blum jb...@pivotal.io wrote: if you unbundle your spark connector from Geode releases how do you know that a given Geode release actually works with it? Because the Spark Connector will depend on (i.e. have been developed and tested with) a specific

[ANNOUNCE] Last code drop from Pivotal (SGA #2)

Hi! Pivotal is happy to announce the donation of remaining geode code that was unable to make into the initial contribution. This will be the last set of geode code donated as a large chunk from Pivotal. At this point all future geode development will be done through the normal apache process.

  1   2   >