Re: Simple Java Client

[Mark Bretl]

A little late to the party...a great thread for discussing options and
there is nothing 'simple' about it ;)

I agree with Jake to follow closer to industry protocols and standards
rather than creating our own. If we want to grow and sustain the Geode
community, adding 'features' which integrate with other communities seems
to be a viable approach.

--Mark

On Wed, Apr 26, 2017 at 5:51 PM, Michael William Dodge 
wrote:

> I like the idea of a separate code base (including repo) for separate
> problem domains. I think trying to fit a new API inside or parallel to the
> existing API has too high of a likelihood of confusion.
>
> Sarge
>
> > On 26 Apr, 2017, at 16:52, Bruce Schuchardt 
> wrote:
> >
> > I don't think we should mix the old client code with a new API.  We
> should keep the new client code separate from the server.  Maybe even in a
> different repo, as I think Fred suggested.
> >
> > Le 4/26/2017 à 3:12 PM, Kirk Lund a écrit :
> >> If we want to add a new API then I suggest we create new API packages
> and
> >> leave the "cache" package as the old deprecated API for backwards
> >> compatibility.
> >>
> >> The new APIs and implementation could be separated into different geode
> >> modules and packages (something like what follows):
> >>
> >> org.apache.geode.api -- the main rich API (geode-api module and jar)
> >> org.apache.geode.api.client -- the new thin client API (geode-api-client
> >> module and jar)
> >> org.apache.geode.core -- the main implementation of api (geode-core
> module
> >> and jar which also currently contains the old API)
> >>
> >> On Wed, Apr 26, 2017 at 9:41 AM, William Markito Oliveira <
> >> william.mark...@gmail.com> wrote:
> >>
> >>> This is an awesome discussion and Jake's hitting all the right notes
> about
> >>> why JCache is a good idea! I've fought that fight in the past and lost
> it
> >>> but I'm happy to see it coming back...
> >>>
> >>> What's really nice about Geode is that the functionalities and
> capabilities
> >>> are all there, they're just not that well exposed, known by others or
> >>> obscured by some decisions that doesn't apply anymore.
> >>>
> >>> It's the same conversation about monitoring and statistics...  All the
> >>> capability is there with JMX and Stats, but using an unknown custom
> format
> >>> or tool to display that data makes it not very appealing for OSS and
> >>> enterprise users that need workarounds and hacks to integrate with
> common
> >>> monitoring tools.
> >>>
> >>> Refactoring API Client APIs, documentation and implementation of a new
> >>> Protocol, Reactive APIs, better integration with standard monitoring
> tools
> >>> -  Sounds like good points for a 2.0 roadmap IMHO.
> >>>
> >>>
> >>> On Wed, Apr 26, 2017 at 10:28 AM, Jacob Barrett 
> >>> wrote:
> >>>
>  Wes,
> 
>  Those are almost all administrative commands and have no place on the
>  client API. They belong on an administrative API or as I'm arguing a
> >>> series
>  of MBeans/JMX as it is already an established standard.
> 
>  -Jake
> 
>  On Wed, Apr 26, 2017 at 8:09 AM Wes Williams 
> >>> wrote:
> > Now we're getting some precision. Let's talk about the "raw" Geode
> > proprietary bad ass API!  Would that "raw" Geode proprietary bad ass
> >>> API
> > "raw"
> > Geode proprietary bad ass API that we're talking about be centered
> >>> around
> > the commands found here:
> >
> > https://github.com/apache/geode/tree/rel/v1.1.1/geode-
>  core/src/main/java/org/apache/geode/management/internal/cli/commands
> > Or somewhere else?
> >
> > *Wes Williams | Pivotal Advisory **Data Engineer*
> > 781.606.0325
> > http://pivotal.io/big-data/pivotal-gemfire
> >
> > On Tue, Apr 25, 2017 at 11:41 PM, Jacob Barrett  >
> > wrote:
> >
> >> Java and its community have standards for all of these issue so why
> >> re-invent the wheel. The market doesn't want proprietary anymore,
> >>> they
> > want
> >> standards and mobility.
> >>
> >> Configuration of the server should happen through MBeans. You can
> >>> wrap
> > that
> >> in gfsh for command line, REST for remote web based admin, use
> >>> JConsole
> > or
> >> any other number of JMX based enterprise management tools. By using
> > MBeans
> >> the server can easily expose new discovered services without the
> need
>  to
> >> code specific gfsh commands, REST interfaces or APIs. There is no
>  reason
> > my
> >> SDG can't be retooled to "discover" the configuration from these
> >>> MBeans
> > as
> >> well rather than having to be touched every time we add or change
> >> something. There are tools and books already written that
> >>> implementors
> > can
> >> consult on MBeans. There isn't anything out there on gfsh commands.
> >>
> >> 

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

[Mark Bretl]

I have added an exclude for any machines with the 'couchdb' label and
restarted the nightly build.

--Mark

On Thu, Apr 27, 2017 at 1:05 PM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> See 
>
> --
> Started by timer
> [EnvInject] - Loading node environment variables.
> Building remotely on couchdb-macos1 (couchdb) in workspace <
> https://builds.apache.org/job/Geode-nightly/ws/>
> java.io.IOException: Failed to mkdirs:  job/Geode-nightly/ws/>
> at hudson.FilePath.mkdirs(FilePath.java:1169)
> at hudson.model.AbstractProject.checkout(AbstractProject.java:
> 1276)
> at hudson.model.AbstractBuild$AbstractBuildExecution.
> defaultCheckout(AbstractBuild.java:604)
> at jenkins.scm.SCMCheckoutStrategy.checkout(
> SCMCheckoutStrategy.java:86)
> at hudson.model.AbstractBuild$AbstractBuildExecution.run(
> AbstractBuild.java:529)
> at hudson.model.Run.execute(Run.java:1728)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
> at hudson.model.ResourceController.execute(
> ResourceController.java:98)
> at hudson.model.Executor.run(Executor.java:404)
> Retrying after 10 seconds
> java.io.IOException: Failed to mkdirs:  job/Geode-nightly/ws/>
> at hudson.FilePath.mkdirs(FilePath.java:1169)
> at hudson.model.AbstractProject.checkout(AbstractProject.java:
> 1276)
> at hudson.model.AbstractBuild$AbstractBuildExecution.
> defaultCheckout(AbstractBuild.java:604)
> at jenkins.scm.SCMCheckoutStrategy.checkout(
> SCMCheckoutStrategy.java:86)
> at hudson.model.AbstractBuild$AbstractBuildExecution.run(
> AbstractBuild.java:529)
> at hudson.model.Run.execute(Run.java:1728)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
> at hudson.model.ResourceController.execute(
> ResourceController.java:98)
> at hudson.model.Executor.run(Executor.java:404)
> Retrying after 10 seconds
> java.io.IOException: Failed to mkdirs:  job/Geode-nightly/ws/>
> at hudson.FilePath.mkdirs(FilePath.java:1169)
> at hudson.model.AbstractProject.checkout(AbstractProject.java:
> 1276)
> at hudson.model.AbstractBuild$AbstractBuildExecution.
> defaultCheckout(AbstractBuild.java:604)
> at jenkins.scm.SCMCheckoutStrategy.checkout(
> SCMCheckoutStrategy.java:86)
> at hudson.model.AbstractBuild$AbstractBuildExecution.run(
> AbstractBuild.java:529)
> at hudson.model.Run.execute(Run.java:1728)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
> at hudson.model.ResourceController.execute(
> ResourceController.java:98)
> at hudson.model.Executor.run(Executor.java:404)
> Archiving artifacts
> ERROR: Build step failed with exception
>  does not exist.
> at org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(
> AbstractFileSet.java:483)
> at org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(
> AbstractFileSet.java:460)
> at hudson.tasks.ArtifactArchiver$ListFiles.invoke(
> ArtifactArchiver.java:292)
> at hudson.tasks.ArtifactArchiver$ListFiles.invoke(
> ArtifactArchiver.java:272)
> at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2731)
> at hudson.remoting.UserRequest.perform(UserRequest.java:153)
> at hudson.remoting.UserRequest.perform(UserRequest.java:50)
> at hudson.remoting.Request$2.run(Request.java:336)
> at hudson.remoting.InterceptingExecutorService$1.call(
> InterceptingExecutorService.java:68)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> at hudson.remoting.Engine$1$1.run(Engine.java:94)
> at java.lang.Thread.run(Thread.java:745)
> at ..remote call to Channel to /91.65.50.62(Native Method)
> at hudson.remoting.Channel.attachCallSiteStackTrace(
> Channel.java:1537)
> at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
> at hudson.remoting.Channel.call(Channel.java:822)
> at hudson.FilePath.act(FilePath.java:985)
> at hudson.FilePath.act(FilePath.java:974)
> at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:
> 237)
> at hudson.tasks.BuildStepCompatibilityLayer.perform(
> BuildStepCompatibilityLayer.java:78)
> at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.
> java:20)
> at hudson.model.AbstractBuild$AbstractBuildExecution.
> perform(AbstractBuild.java:779)
> at 

Fwd: ASF Board Report for Geode - Initial Reminder for May 2017

[Mark Bretl]

Hi Everyone,

Amazing how three months goes by so fast! We are approaching six months
since our TLP graduation and its time for another board report.

Do we have any volunteers to create a draft? No need to be a PMC member
either, anyone can be involved with writing the report. There is a template
on the Geode wiki [1].

Best regards,

--Mark

[1]:
https://cwiki.apache.org/confluence/display/GEODE/ASF+Board+Report+Template


-- Forwarded message --
From: Brett Porter <br...@apache.org>
Date: Wed, Apr 26, 2017 at 6:16 AM
Subject: ASF Board Report for Geode - Initial Reminder for May 2017
To: Mark Bretl <mbr...@apache.org>
Cc: priv...@geode.apache.org


This email was sent on behalf of the ASF Board.  It is an initial reminder
to
give you plenty of time to prepare the report.

According to board records, you are listed as the chair of a committee that
is
due to submit a report this month. [1] [2]

The meeting is scheduled for Wed, 17 May 2017 at 10:30 PDT and the deadline
for
submitting your report is 1 full week prior to that (Wed May 10th)!

Meeting times in other time zones:

  https://timeanddate.com/s/38ta

Please submit your report with sufficient time to allow the board members
to review and digest. Again, the very latest you should submit your report
is 1 full week (7days) prior to the board meeting (Wed May 10th).

If you feel that an error has been made, please consult [1] and if there
is still an issue then contact the board directly.

As always, PMC chairs are welcome to attend the board meeting.

Thanks,
The ASF Board

[1] - https://svn.apache.org/repos/private/committers/board/
committee-info.txt
[2] - https://svn.apache.org/repos/private/committers/board/calendar.txt
[3] - https://svn.apache.org/repos/private/committers/board/templates
[4] - https://reporter.apache.org/

Re: Request For Geode Wiki Admin Karma

[Mark Bretl]

Thanks Dan! Much appreciated.

--Mark

On Wed, Apr 19, 2017 at 12:09 PM, Dan Smith <dsm...@pivotal.io> wrote:

> Hi Mark,
>
> I just made you a space admin on the wiki!
>
> -Dan
>
> On Wed, Apr 19, 2017 at 11:58 AM, Mark Bretl <mbr...@apache.org> wrote:
>
> > Ping.
> >
> > --Mark
> >
> > On Thu, Mar 30, 2017 at 3:51 PM, Mark Bretl <mbr...@apache.org> wrote:
> >
> > > Hi,
> > >
> > > I would like to follow Kirk's request with one of my own for Admin
> Karma
> > > on the Geode Wiki. Username is mbretl.
> > >
> > > Best Regards,
> > >
> > > --Mark
> > >
> >
>

Re: Request For Geode Wiki Admin Karma

[Mark Bretl]

Ping.

--Mark

On Thu, Mar 30, 2017 at 3:51 PM, Mark Bretl <mbr...@apache.org> wrote:

> Hi,
>
> I would like to follow Kirk's request with one of my own for Admin Karma
> on the Geode Wiki. Username is mbretl.
>
> Best Regards,
>
> --Mark
>

Re: Jenkins karma (was Re: Blacklist asf904 for Geode nightly job)

[Mark Bretl]

Hi Anthony,

Look at that I do have karma for adding people to Jenkins. I have added you
to Jenkins.

Please let me know if you have any issues.

--Mark

On Mon, Apr 10, 2017 at 9:59 AM, William Markito Oliveira <
william.mark...@gmail.com> wrote:

> Hi Anthony,
>
> My karma is also limited, sorry.  I believe only Roman (or infra) can
> change that...
>
> On Mon, Apr 10, 2017 at 11:46 AM, Anthony Baker  wrote:
>
> > Anyone?
> >
> > > On Apr 7, 2017, at 11:32 AM, Anthony Baker  wrote:
> > >
> > > I would like Jenkins karma so I can explore running our tests from
> > within a docker container.  William / Mark / Roman can you help me out?
> > >
> > > Thanks,
> > > Anthony
> > >
> > >
> > >> On Mar 21, 2017, at 3:14 PM, Anthony Baker  wrote:
> > >>
> > >> Would be very nice to run our jenkins jobs from a docker container to
> > avoid these environmental quirks.
> > >>
> > >> Anthony
> >
> >
>
>
> --
> ~/William
>

Please Remember To Use Community Accessible Tools And References

[Mark Bretl]

Friendly reminder to those in the community to use community accessible
references when checking in code or on the discussion lists.

Recently, I have noticed a small increase in non-Geode references in JIRA
tickets, reviews, and Git comments. Its not that you are not able to use
them, it makes it harder for our integration services to work efficiently
when they do not use a 'GEODE' prefix.

Best regards,

--Mark

Re: Review Request 58213: GEODE-2749: don't ignore bin/ because we have bin/ in src

[Mark Bretl]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/58213/#review171148
---


Ship it!




I missed geode-assembly/src/main/dist/bin/ in my initial review. Thanks for the 
update Kirk.

- Mark Bretl


On April 5, 2017, 10:19 a.m., Kirk Lund wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/58213/
> ---
> 
> (Updated April 5, 2017, 10:19 a.m.)
> 
> 
> Review request for geode, Anthony Baker, Avinash Dongre, Mark Bretl, and Udo 
> Kohlmeyer.
> 
> 
> Bugs: GEODE-2749
> https://issues.apache.org/jira/browse/GEODE-2749
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-2749: don't ignore bin/ because we have bin/ in src
> 
> $ find . -name 'bin'
> ./extensions/geode-modules-assembly/release/session/bin <-- contains 
> modify_war script
> ./extensions/geode-modules-tomcat8/bin  <-- empty?
> ./geode-assembly/src/main/dist/bin  <-- contains our gfsh 
> scripts
> 
> 
> Diffs
> -
> 
>   .gitignore 31d5996b833bb3a32a0e2480e94335d5fa05a914 
>   gradle/rat.gradle 7bea470ae681492c61a76315ecad09a53c3f43fe 
> 
> 
> Diff: https://reviews.apache.org/r/58213/diff/1/
> 
> 
> Testing
> ---
> 
> precheckin in progress
> 
> 
> Thanks,
> 
> Kirk Lund
> 
>

Re: Review Request 58158: GEODE-2749: ignore bin/ and out/ which are commonly created by IDEs

[Mark Bretl]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/58158/#review171015
---


Ship it!




Ship It!

- Mark Bretl


On April 3, 2017, 12:57 p.m., Kirk Lund wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/58158/
> ---
> 
> (Updated April 3, 2017, 12:57 p.m.)
> 
> 
> Review request for geode, Jinmei Liao, Jared Stewart, Ken Howe, and Patrick 
> Rhomberg.
> 
> 
> Bugs: GEODE-2749
> https://issues.apache.org/jira/browse/GEODE-2749
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> I installed new versions of Eclipse and IntelliJ and created geode projects 
> in both using the defaults for IDE output of compiled classes. They created 
> bin/ and out/ which were then failing rat and also showing up as untracked 
> files by git.
> 
> I added both to .gitignore and the ignore list in gradle/rat.gradle and 
> tested with git status and ./gradlew rat.
> 
> 
> Diffs
> -
> 
>   .gitignore 38c813196f5 
>   gradle/rat.gradle c97a9e9dc78 
> 
> 
> Diff: https://reviews.apache.org/r/58158/diff/1/
> 
> 
> Testing
> ---
> 
> precheckin in progress
> 
> 
> Thanks,
> 
> Kirk Lund
> 
>

Re: [VOTE] Apache Geode release - v1.1.1 RC2

[Mark Bretl]

+1 (binding)

- Checked and verified all MD5 and SHA256 hashes
- Executed GFSH from both ZIP and TAR binary distributions
- Verified GFSH version is 1.1.1

--Mark

On Thu, Mar 30, 2017 at 4:52 PM, Anthony Baker  wrote:

> We need more reviews from the community and PMC members.  Please check out
> the release candidate and vote.  Thanks!
>
> Anthony
>
> > On Mar 27, 2017, at 10:18 PM, Anthony Baker  wrote:
> >
> > This is the second release candidate of the release for Apache Geode,
> > version 1.1.1.
> >
> > It fixes the following issues:
> >  https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12318420=12340271
> >
> > *** Please download, test and vote by Thursday, March 30, 2200 hrs US
> > Pacific. ***
> >
> > Note that we are voting upon the source (tag):
> >  rel/v1.1.1.RC2
> >  https://git-wip-us.apache.org/repos/asf?p=geode.git;a=tag;h=
> refs/tags/rel/v1.1.1.RC2
> >
> > Commit ID: e2081044ea0afca1cb38d62c7f34e7363b45ad97
> >
> > Source and binary files:
> >  https://dist.apache.org/repos/dist/dev/geode/1.1.1.RC2/
> >
> > Maven staging repo:
> >  https://repository.apache.org/content/repositories/orgapachegeode-1018
> >
> > Geode's KEYS file containing PGP keys we use to sign the release:
> >  https://github.com/apache/geode/blob/release/1.1.1/KEYS
> >
> > pub  4096R/C72CFB64 2015-10-01
> >Fingerprint=948E 8234 14BE 693A 7F74  ABBE 19DB CAEE C72C FB64
> >
> >
> > Thanks,
> > Anthony
>
>

Request For Geode Wiki Admin Karma

[Mark Bretl]

Hi,

I would like to follow Kirk's request with one of my own for Admin Karma on
the Geode Wiki. Username is mbretl.

Best Regards,

--Mark

[jira] [Commented] (GEODE-2734) Investigate/discuss message encoding

[Mark Bretl (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEODE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15949986#comment-15949986
 ] 

Mark Bretl commented on GEODE-2734:
---

This may be only a task to track the overall discussion, however, please 
remember to have the discuss discussion on the dev mailing list.

Thanks,

--Mark

> Investigate/discuss message encoding
> 
>
> Key: GEODE-2734
> URL: https://issues.apache.org/jira/browse/GEODE-2734
> Project: Geode
>  Issue Type: Sub-task
>  Components: messaging
>Reporter: Brian Baynes
>
> Out of all the great ways to encode messages (Thrift, Protobuf, etc), which 
> should we use here?  Let's discuss and come to consensus.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (GEODE-2738) There are many typos throughout the codebase.

[Mark Bretl (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEODE-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15949979#comment-15949979
 ] 

Mark Bretl commented on GEODE-2738:
---

 [~prhomberg] This is a vague subject and hard to determine the scope of the 
changes. Are you able to narrow the issue?

> There are many typos throughout the codebase.
> -
>
> Key: GEODE-2738
> URL: https://issues.apache.org/jira/browse/GEODE-2738
> Project: Geode
>  Issue Type: Bug
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Trivial
>
> The most pervasive that I've noticed is that "occurred" is spelled with only 
> one R.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

ASF on Slack

[Mark Bretl]

If you have a @apache.org email, you should be able to register.

I have created a #geode channel. Not sure about the use of Slack yet (maybe
an alternative to HipChat?), but might as well give it a try and see where
it goes.

--Mark

-- Forwarded message --
From: John D. Ament 
Date: Wed, Mar 29, 2017 at 6:54 AM
Subject: Slack Invites
To: "gene...@incubator.apache.org" 


All,

Based on the on-going discussions, I decided to move ahead with a single
organization for Slack.  I've opened up registrations to all @apache.org
email addresses.  To get set up, please use https://the-asf.slack.com/signup
to
get your account up and running.

Happy Slacking!

John

Re: New Committer And PMC Member: Ernest Burghardt

[Mark Bretl]

Welcome Ernie!

--Mark

On Mon, Mar 27, 2017 at 9:33 AM, Michael Stolz  wrote:

> Congratulations Ernie!
>
> --
> Mike Stolz
> Principal Engineer, GemFire Product Manager
> Mobile: +1-631-835-4771
>
> On Fri, Mar 24, 2017 at 7:22 PM, Nabarun Nag  wrote:
>
> > Congrats and welcome !!! :)
> >
> > On Fri, Mar 24, 2017 at 3:41 PM Bruce Schuchardt  >
> > wrote:
> >
> > > Welcome to the group Ernie!
> > >
> > > Le 3/24/2017 à 3:03 PM, Anthony Baker a écrit :
> > > > The Apache Geode Project Management Committee has invited Ernest
> > > > Burghardt to be committer on the project and join the Geode PMC. We
> > > > are pleased to announce he has accepted.
> > > >
> > > > Please join me in welcoming Ernie!
> > > >
> > > > Thanks,
> > > >
> > > > Anthony
> > > > On behalf of the Apache Geode PMC
> > >
> > >
> >
>

[jira] [Commented] (GEODE-2715) Move Pulse to its own repo

[Mark Bretl (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEODE-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15941152#comment-15941152
 ] 

Mark Bretl commented on GEODE-2715:
---

This should be discussed on the dev list before any other actions take place

> Move Pulse to its own repo
> --
>
> Key: GEODE-2715
> URL: https://issues.apache.org/jira/browse/GEODE-2715
> Project: Geode
>  Issue Type: Improvement
>  Components: pulse
>Reporter: Swapnil Bawaskar
>
> Pulse should be moved to a separate repository so that it can be 
> independently released. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Export Control for Geode

[Mark Bretl]

HI Anthony,

Sorry for the delay, I have completed steps #1 and #2.

--Mark

On Mon, Mar 6, 2017 at 10:42 AM, Anthony Baker <aba...@pivotal.io> wrote:

> Thanks Mark!  Let me know if you have any questions.
>
> Anthony
>
> > On Mar 6, 2017, at 10:32 AM, Mark Bretl <mbr...@apache.org> wrote:
> >
> > Looks good. Unless there are any other comments/issues, I will start this
> > tomorrow.
> >
> > --Mark
> >
> > On Thu, Mar 2, 2017 at 10:29 PM, Anthony Baker <aba...@apache.org>
> wrote:
> >
> >> After reviewing [1], I think we need to record and report our use of
> >> cryptographic libraries that fall under US export control.
> >>
> >> This means:
> >>
> >> 1) Updating the eccnmatrix.xml [2] in svn and publishing the change [3].
> >> 2) Sending an email [4].
> >> 3) Updating README.md [5].
> >>
> >> Mark, #1 and #2 need to be done by the PMC Chair.  Can you review this
> >> and let me know what you think?  I can tackle #3 after.
> >>
> >> Thanks,
> >> Anthony
> >>
> >> [1] http://www.apache.org/dev/crypto.html
> >> [2] https://gist.github.com/metatype/96da9d928f20d5ae638cc16dd4ee9a85
> >> [3] https://cms.apache.org/www/publish
> >> [4] https://gist.github.com/metatype/24b4462af6319cbf568b63ad3a56464e
> >> [5] https://gist.githubusercontent.com/metatype/
> >> b50b49a4c2a7a99793029b3ea0cde8c3/raw/40aca011a65c12d6fbec73fce60f57
> >> f43323d36f/README.md
> >>
>
>

TSU NOTIFICATION - Encryption

[Mark Bretl]

SUBMISSION TYPE: TSU

SUBMITTED BY: Mark Bretl

SUBMITTED FOR: The Apache Software Foundation

POINT OF CONTACT: Secretary, The Apache Software Foundation

FAX: +1-919-573-9199

MANUFACTURER(S): The Apache Software Foundation, Oracle, The OpenSSL
Project

PRODUCT NAME/MODEL #: Apache Geode

ECCN: 5D002

NOTIFICATION: http://www.apache.org/licenses/exports/

Re: A force push happened to geode-native develop!?!

[Mark Bretl]

+1 For no force push

--Mark

On Wed, Mar 8, 2017 at 3:50 PM, Kevin Duling  wrote:

> +1. Don't turn to the dark side of the --force.
>
> On Mar 8, 2017 3:12 PM, "Dan Smith"  wrote:
>
> > Yeah, shared branches was kinda of a vague term. I am talking about
> > develop, master, and release*.
> >
> > I think in general if you are working on a feature branch with along
> other
> > people, you also shouldn't force push that feature branch, but for the
> > moment the proposal is just to protect develop, master, and release*
> >
> > I agree with should also block push --delete for develop and master.
> >
> > -Dan
> >
> > On Wed, Mar 8, 2017 at 3:04 PM, Jared Stewart 
> wrote:
> >
> > > When I say “shared branches”, I’m thinking of develop, master, and
> > > release-* as mentioned by Dan.
> > >
> > >
> > > > On Mar 8, 2017, at 3:03 PM, Dave Barnes  wrote:
> > > >
> > > >> It also would seem prudent to block 'git push —delete’ on shared
> > > branches
> > > >
> > > > Isn't that how we clean up feature branches?
> > > >
> > > > On Wed, Mar 8, 2017 at 1:55 PM, Jared Stewart 
> > > wrote:
> > > >
> > > >> +1 to blocking force pushes on shared branches.  It also would seem
> > > >> prudent to block 'git push —delete’ on shared branches if that isn’t
> > > >> already blocked.
> > > >>
> > > >>> On Mar 8, 2017, at 1:48 PM, Dan Smith  wrote:
> > > >>>
> > > >>> Karen and I just spent a long time tracking down weird git history
> in
> > > her
> > > >>> checkout to discover that someone did a force push of the
> > geode-native
> > > >>> develop. That's not cool, because it screws over anyone with a copy
> > of
> > > >> the
> > > >>> branch and we potentially lost history.
> > > >>>
> > > >>> I think we need to do two things.
> > > >>>
> > > >>> 1) Block force pushes on any shared branches (develop, master,
> > > >> release-*).
> > > >>> If we are in agreement, I'll file a JIRA with INFRA
> > > >>>
> > > >>> 2) Figure out what to with geode-native develop. It looks like
> there
> > > have
> > > >>> been commits since the force push. Do we keep what is on the branch
> > > now,
> > > >> or
> > > >>> try to put it back to what it was?
> > > >>>
> > > >>> -Dan
> > > >>>
> > > >>>
> > > >>> From: jbarr...@apache.org
> > > >>>
> > > >>> 4:57 PM (20 hours ago)
> > > >>>
> > > >>> to commits
> > > >>> Repository: geode-native
> > > >>> Updated Branches:
> > > >>> refs/heads/develop aff706be2 -> 06e8f39a0 (forced update)
> > > >>
> > > >>
> > >
> > >
> >
>

Re: Export Control for Geode

[Mark Bretl]

Looks good. Unless there are any other comments/issues, I will start this
tomorrow.

--Mark

On Thu, Mar 2, 2017 at 10:29 PM, Anthony Baker  wrote:

> After reviewing [1], I think we need to record and report our use of
> cryptographic libraries that fall under US export control.
>
> This means:
>
> 1) Updating the eccnmatrix.xml [2] in svn and publishing the change [3].
> 2) Sending an email [4].
> 3) Updating README.md [5].
>
> Mark, #1 and #2 need to be done by the PMC Chair.  Can you review this
> and let me know what you think?  I can tackle #3 after.
>
> Thanks,
> Anthony
>
> [1] http://www.apache.org/dev/crypto.html
> [2] https://gist.github.com/metatype/96da9d928f20d5ae638cc16dd4ee9a85
> [3] https://cms.apache.org/www/publish
> [4] https://gist.github.com/metatype/24b4462af6319cbf568b63ad3a56464e
> [5] https://gist.githubusercontent.com/metatype/
> b50b49a4c2a7a99793029b3ea0cde8c3/raw/40aca011a65c12d6fbec73fce60f57
> f43323d36f/README.md
>

Re: Review Request 57171: GEODE-2461: remove json4s-ast_2.10 as explicit dependency

[Mark Bretl]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/57171/#review167372
---


Ship it!




Ship It!

- Mark Bretl


On Feb. 28, 2017, 2:17 p.m., Kirk Lund wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/57171/
> ---
> 
> (Updated Feb. 28, 2017, 2:17 p.m.)
> 
> 
> Review request for geode, Anthony Baker, Jinmei Liao, Jared Stewart, Mark 
> Bretl, Udo Kohlmeyer, and Dan Smith.
> 
> 
> Bugs: GEODE-2461
> https://issues.apache.org/jira/browse/GEODE-2461
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> Remove explicit dependency on json4s-ast_2.10.
> 
> I couldn't find anything that actually uses json4s-ast_2.10, directly or 
> transitively, so I've removed it completely.
> 
> 
> Diffs
> -
> 
>   geode-assembly/src/test/resources/expected_jars.txt 
> a9a5a792a4e4aafb9b191cd3bf89d54fe559bc75 
>   geode-web-api/build.gradle 8b22bd8de174ddad47f4acbd0da75614a060da99 
>   gradle/dependency-versions.properties 
> be828af14826ff63adee18717de063d87e2f1c6c 
> 
> 
> Diff: https://reviews.apache.org/r/57171/diff/1/
> 
> 
> Testing
> ---
> 
> precheckin passed
> 
> 
> Thanks,
> 
> Kirk Lund
> 
>

Re: Review Request 57175: GEODE-4160: upgrade mortbay-jetty-servlet-api dependency

[Mark Bretl]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/57175/#review167371
---


Ship it!




Ship It!

- Mark Bretl


On Feb. 28, 2017, 5:39 p.m., Kirk Lund wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/57175/
> ---
> 
> (Updated Feb. 28, 2017, 5:39 p.m.)
> 
> 
> Review request for geode, Anthony Baker, Jinmei Liao, Jared Stewart, Kevin 
> Duling, Ken Howe, and Mark Bretl.
> 
> 
> Bugs: GEODE-4160
> https://issues.apache.org/jira/browse/GEODE-4160
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> Upgrade mortbay-jetty-servlet-api dependency
> 
> This is the last upgrade on GEODE-4160 ticket.
> 
> 
> Diffs
> -
> 
>   gradle/dependency-versions.properties aca65fa 
> 
> 
> Diff: https://reviews.apache.org/r/57175/diff/1/
> 
> 
> Testing
> ---
> 
> precheckin in progress
> uiTest passes
> 
> 
> Thanks,
> 
> Kirk Lund
> 
>

Re: apache-geode/lib/ra.jar

[Mark Bretl]

Hi Kirk,

ra.jar gets built from geode-core, here is the build task:

task raJar (type: Jar, dependsOn: classes) {
  description 'Assembles the jar archive that contains the JCA classes'
  from sourceSets.jca.output
  exclude 'org/apache/geode/ra/**'
  archiveName 'ra.jar'
}

I see no reason why it shouldn't have a 'geode' prefix, probably an oversight.

--Mark


On Tue, Feb 28, 2017 at 3:11 PM, Kirk Lund  wrote:

> Does anyone know why "apache-geode/lib/ra.jar" doesn't have a geode- prefix
> and release numbers in the jar name? This is the only unidentified jar in
> the Apache Geode lib directory, and I think we should change this to be
> named like the other jars if possible. It seems to contain JCA classes from
> geode-core.
>
> /Users/klund/dev/geode/geode-
> assembly/build/install/apache-geode/lib [512]$ jar -tvf ra.jar
>  0 Tue Feb 28 14:22:20 PST 2017 META-INF/
>131 Tue Feb 28 14:22:20 PST 2017 META-INF/MANIFEST.MF
>  21685 Mon Feb 27 15:55:04 PST 2017 META-INF/LICENSE
>574 Mon Feb 27 15:55:04 PST 2017 META-INF/NOTICE
>  0 Tue Feb 28 14:19:26 PST 2017 org/
>  0 Tue Feb 28 14:19:26 PST 2017 org/apache/
>  0 Tue Feb 28 14:19:26 PST 2017 org/apache/geode/
>  0 Tue Feb 28 14:19:26 PST 2017 org/apache/geode/internal/
>  0 Tue Feb 28 14:19:26 PST 2017 org/apache/geode/internal/ra/
>   1688 Tue Feb 28 14:19:26 PST 2017 org/apache/geode/internal/ra/
> GFConnectionFactoryImpl.class
>   1343 Tue Feb 28 14:19:26 PST 2017 org/apache/geode/internal/ra/
> GFConnectionImpl.class
>  0 Tue Feb 28 14:19:26 PST 2017 org/apache/geode/internal/ra/spi/
>   4940 Tue Feb 28 14:19:26 PST 2017 org/apache/geode/internal/ra/
> spi/JCALocalTransaction.class
>   7795 Tue Feb 28 14:19:26 PST 2017 org/apache/geode/internal/ra/
> spi/JCAManagedConnection.class
>   3451 Tue Feb 28 14:19:26 PST 2017 org/apache/geode/internal/ra/spi/
> JCAManagedConnectionFactory.class
>   1089 Tue Feb 28 14:19:26 PST 2017 org/apache/geode/internal/ra/spi/
> JCAManagedConnectionMetaData.class
>

Re: Build failed in Jenkins: Geode-nightly #762 - adongre, please read

[Mark Bretl]

There is an AWS outage right now, not sure if that is affecting the Gradle
plugin site...

--Mark

On Tue, Feb 28, 2017 at 10:53 AM, Bruce Schuchardt 
wrote:

> I deleted my gradle cache & am also having trouble downloading things
>
>:buildSrc:build UP-TO-DATE
>
>FAILURE: Build failed with an exception.
>
>* What went wrong:
>A problem occurred configuring root project 'geode'.
> > Could not resolve all dependencies for configuration ':classpath'.
>> Could not resolve
>gradle.plugin.org.nosphere.apache:creadur-rat-gradle:0.2.0.
>  Required by:
>  :geode:unspecified
>   > Could not resolve
>gradle.plugin.org.nosphere.apache:creadur-rat-gradle:0.2.0.
>  > Could not get resource
>'https://plugins.gradle.org/m2/gradle/plugin/org/nosphere/a
> pache/creadur-rat-gradle/0.2.0/creadur-rat-gradle-0.2.0.pom'.
> > Could not GET
>'https://plugins.gradle.org/m2/gradle/plugin/org/nosphere/a
> pache/creadur-rat-gradle/0.2.0/creadur-rat-gradle-0.2.0.pom'.
>Received status code 503 from server: Service Unavailable
>etc.
>
> I'm getting 503s on everything but the initial gradle download.
>
>
> Le 2/28/2017 à 10:40 AM, Avinash Dongre a écrit :
>
>> I am getting following error while running precheckin.
>>
>> * Where:
>> Build file '/home/ampool/private/geode/java/geode/geode-old-versions/bu
>> ild.gradle'
>> line: 58
>>
>> * What went wrong:
>> Execution failed for task ':geode-old-versions:createGeo
>> deClasspathsFile'.
>>
>>> Could not resolve all dependencies for configuration
>>> ':geode-old-versions:
>>>
>> test110Runtime'.
>> > Could not download geode-cq.jar (org.apache.geode:geode-cq:1.1.0)
>>> Could not get resource 'https://repo1.maven.org/
>> maven2/org/apache/geode/geode-cq/1.1.0/geode-cq-1.1.0.jar'.
>>   > Could not GET 'https://repo1.maven.org/
>> maven2/org/apache/geode/geode-cq/1.1.0/geode-cq-1.1.0.jar'. Received
>> status
>> code 503 from server: Connection timed out
>>
>>
>>
>> On Tue, Feb 28, 2017 at 11:06 PM, Avinash Dongre 
>> wrote:
>>
>> It is my mistake.
>>>
>>> I will revert back my changes for this Test and raise a PR.
>>>
>>> Thanks
>>> Avinash
>>>
>>>
>>> On Tue, Feb 28, 2017 at 10:26 PM, Bruce Schuchardt <
>>> bschucha...@pivotal.io
>>>
 wrote:
 ClientServerMiscBCDUnitTest is failing due to adongre's commit
 yesterday.  A parameterized test was added to a superclass, causing
 conflict with the subclass's parameterization of all the superclass's
 methods


 java.lang.Exception: Method testProxyRegionClientServerOp should have no
 parameters

  at org.junit.runners.model.FrameworkMethod.validatePublicVoidNo
 Arg(FrameworkMethod.java:76)
  at org.junit.runners.ParentRunner.validatePublicVoidNoArgMethod
 s(ParentRunner.java:155)
  at org.junit.runners.BlockJUnit4ClassRunner.validateTestMethods
 (BlockJUnit4ClassRunner.java:208)
  at org.junit.runners.BlockJUnit4ClassRunner.validateInstanceMet
 hods(BlockJUnit4ClassRunner.java:188)
  at org.junit.runners.BlockJUnit4ClassRunner.collectInitializati
 onErrors(BlockJUnit4ClassRunner.java:128)
  at org.junit.runners.ParentRunner.validate(ParentRunner.java:416)
  at org.junit.runners.ParentRunner.(ParentRunner.java:84)
  at org.junit.runners.BlockJUnit4ClassRunner.(BlockJUnit4C
 lassRunner.java:65)
  at org.junit.runners.parameterized.BlockJUnit4ClassRunnerWithPa
 rameters.(BlockJUnit4ClassRunnerWithParameters.java:27)
  at org.apache.geode.test.junit.runners.CategoryWithParameterize
 dRunner.(CategoryWithParameterizedRunner.java:29)
  at org.apache.geode.test.junit.runners.CategoryWithParameterize
 dRunnerFactory.createRunnerForTestWithParameters(CategoryWit
 hParameterizedRunnerFactory.java:40)
  at org.junit.runners.Parameterized.createRunnersForParameters(P
 arameterized.java:313)
  at org.junit.runners.Parameterized.(Parameterized.java:248)
  at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
 Method)
  at sun.reflect.NativeConstructorAccessorImpl.newInstance(Native
 ConstructorAccessorImpl.java:62)
  at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(De
 legatingConstructorAccessorImpl.java:45)
  at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
  at org.junit.internal.builders.AnnotatedBuilder.buildRunner(Ann
 otatedBuilder.java:104)
  at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(
 AnnotatedBuilder.java:86)
  at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(Run
 nerBuilder.java:59)
  at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.r
 unnerForClass(AllDefaultPossibilitiesBuilder.java:26)
  at 

Re: Review Request 57050: GEODE-2461: remove unnecessary explicit dependencies

[Mark Bretl]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/57050/#review166762
---


Ship it!




Ship It!

- Mark Bretl


On Feb. 24, 2017, 1:37 p.m., Kirk Lund wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/57050/
> ---
> 
> (Updated Feb. 24, 2017, 1:37 p.m.)
> 
> 
> Review request for geode, Anthony Baker, Jinmei Liao, Jared Stewart, Kevin 
> Duling, Ken Howe, Mark Bretl, and Dan Smith.
> 
> 
> Bugs: GEODE-2461
> https://issues.apache.org/jira/browse/GEODE-2461
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-2461: remove unnecessary explicit dependencies
> 
> * activation - transitive via javax.mail-api
> * annotations - unused
> * cdi-api - unused
> * classmate - transitive via springfox (swagger)
> * hadoop - unused
> * hbase - unused
> * hibernate - unused
> * hibernate-commons-annotations - unused
> * hsqldb - unused
> * jline - transtive via spring-shell
> * jsr305 - unused
> * paranamer - transitive via jackson-module-paranamer
> * quartz - unused
> * scala - transitive via jackson-module-scala_2.10
>  
> Add explicit testCompile dependency for guava to geode-core so that tests 
> using guava API in both geode-junit and geode-core are using the same 
> versions.
> 
> 
> Diffs
> -
> 
>   geode-assembly/build.gradle 3452141b030e12a5dd0bbb130b6a6a47707b7cef 
>   geode-core/build.gradle 8eba6d4e8f9c6b021b214171bac5e360a0c86e7a 
>   geode-web-api/build.gradle 9c491a0d9250dfe0aa089f61a8e4148acdeec5a3 
>   gradle/dependency-versions.properties 
> 5153f0b1bde2cec3d54354b5075ba069cfbf1ab6 
> 
> Diff: https://reviews.apache.org/r/57050/diff/
> 
> 
> Testing
> ---
> 
> precheckin passed (100% green)
> 
> 
> Thanks,
> 
> Kirk Lund
> 
>

Re: Please blacklist asf91

[Mark Bretl]

Hi Kirk,

I have removed asf91 (which is really H19) and H20 from the node list. It
looks like H19 and H20 are website publishing nodes and not supposed to be
used for builds.

Hopefully this should get some better results,

--Mark

On Fri, Feb 24, 2017 at 8:56 AM, Kirk Lund  wrote:

> UniversalMembershipListenerAdapterDUnitTest  always fails on asf91 but
> the test is correct. It looks like asf91 has incorrect DNS
> configuration.
>

Re: [Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #481 has FAILED

[Mark Bretl]

John,

It looks like this is failing because it can't find the
geode-*-1.1.0-SNAPSHOT.jars. As 1.1.0 has been released, we have removed
these jars. Next version is currently 1.2.0(-SNAPSHOT).

Would you or someone else be able to update this job?

Thanks,

--Mark

On Thu, Feb 23, 2017 at 11:51 AM, Spring CI  wrote:

>
> ---
> Spring Data GemFire > Nightly-ApacheGeode > #481 failed.
> ---
> This was manually triggered by Trevor Marshall.
> No failed tests found, a possible compilation error.
>
> https://build.spring.io/browse/SGF-NAG-481/
>
> -
> Currently Responsible
> -
>
> No one is responsible for fixing this build.
>
>
>
> --
> Failing Jobs
> --
>   - Default Job (Default Stage): No tests found.
>
>
>
>
> --
> This message is automatically generated by Atlassian Bamboo

Re: Review Request 56934: GEODE-2460: update dependency versions

[Mark Bretl]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56934/#review166382
---



Have new versions been checked for any license changes?
Also, I think Anthony has an outstanding pull request for updating the Spring 
Framework version.

- Mark Bretl


On Feb. 22, 2017, 9:09 a.m., Kirk Lund wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/56934/
> ---
> 
> (Updated Feb. 22, 2017, 9:09 a.m.)
> 
> 
> Review request for geode, Anthony Baker, Jinmei Liao, Jared Stewart, Kevin 
> Duling, Ken Howe, and Mark Bretl.
> 
> 
> Bugs: GEODE-2460
> https://issues.apache.org/jira/browse/GEODE-2460
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> -asm.version = 5.1
> +asm.version = 5.2
> 
> -fastutil.version = 7.0.13
> +fastutil.version = 7.1.0
> 
> -httpclient.version = 4.5.2
> +httpclient.version = 4.5.3
> 
> -netty-all.version = 4.1.7.Final
> -open-json.version = 1.7
> +netty-all.version = 4.1.8.Final
> +open-json.version = 1.8
> 
> -slf4j-api.version = 1.7.22
> +slf4j-api.version = 1.7.23
> 
> -spring-hateoas.version = 0.21.0.RELEASE
> +spring-hateoas.version = 0.23.0.RELEASE
> 
> -spring-ldap-core.version = 2.1.0.RELEASE
> -spring-security.version = 4.1.3.RELEASE
> -spring-tx.version = 4.3.2.RELEASE
> -springframework.version = 4.3.2.RELEASE
> +spring-ldap-core.version = 2.3.1.RELEASE
> +spring-security.version = 4.2.1.RELEASE
> +spring-tx.version = 4.3.6.RELEASE
> +springframework.version = 4.3.6.RELEASE
> 
> -springfox.version=2.6.0
> +springfox.version=2.6.1
> 
> I tried to update selenium.version from 3.0.1 to 3.1.0 but it results in 
> uiTest failures so I backed that out and will file a separate Jira ticket for 
> updating Selenium.
> 
> 
> Diffs
> -
> 
>   gradle/dependency-versions.properties 12a76b4 
> 
> Diff: https://reviews.apache.org/r/56934/diff/
> 
> 
> Testing
> ---
> 
> precheckin passed 100% green
> 
> 
> Thanks,
> 
> Kirk Lund
> 
>

Voting Process

[Mark Bretl]

Hi,

Now that we are a top-level project, we need to make sure votes are counted
correctly, according to the Apache Voting Process [1]. For this past
release vote, we only had PMC votes, however, that could change in the
future as we would like to encourage community feedback. In the future, i
think we should clarify binding vs non-binding votes on the vote result
thread.

Best regards,

--Mark

[1] http://apache.org/foundation/voting.html

-- Forwarded message --
From: Hitesh Khamesra 
Date: Tue, Feb 14, 2017 at 11:12 AM
Subject: [RESULT][VOTE] RC2: Apache Geode 1.1.0 release
To: Geode 



The vote passes with 6 +1 and 2 +0 votes:

Jinmei Liao  +1
Udo Kohlmeyer+1
William Markito  +1
Dan Smith+1
Xiaojian Zhou+1
Anthony Baker+1

Kenneth Howe +0
Karen Miller +0

Mail thread: http://mail-archives.apache.org/mod_mbox/incubator-geode-
dev/201702.mbox/%3C1656177403.1540917.1486673726802%40mail.yahoo.com%3E

Thanks.Dan & Hitesh

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

[Mark Bretl]

Hi Galen,

I am able to the console log [1], test report summary [2], and artifacts
[3] without logging in. Which 'build report' are you trying to view?

--Mark

[1] https://builds.apache.org/job/Geode-nightly/749/console
[2] https://builds.apache.org/job/Geode-nightly/749/testReport/
[3] https://builds.apache.org/job/Geode-nightly/749/artifact/

On Wed, Feb 15, 2017 at 9:04 AM, Galen M O'Sullivan 
wrote:

> I don't seem to have access to see the build report. Is that restricted to
> committers only?
>
> Thanks,
> Galen
>
> On Wed, Feb 15, 2017 at 8:08 AM, Apache Jenkins Server <
> jenk...@builds.apache.org> wrote:
>
> > See 
> >
> > Changes:
> >
> > [kmiller] GEODE-2479 Remove docs reference to gemstone.com package
> >
> > [jiliao] GEODE-2474: mark NetstatDUnitTest as flaky
> >
> > [jiliao] refactor ServerStarterRule and LocatorStarterRule so that they
> > can be
> >
> > [gzhou] GEODE-2471: fix the race condition in test code.
> >
> > --
> > [...truncated 713 lines...]
> > :geode-cq:build
> > :geode-cq:distributedTest
> > :geode-cq:flakyTest
> > :geode-cq:integrationTest
> > :geode-json:assemble
> > :geode-json:compileTestJava UP-TO-DATE
> > :geode-json:processTestResources UP-TO-DATE
> > :geode-json:testClasses UP-TO-DATE
> > :geode-json:checkMissedTests UP-TO-DATE
> > :geode-json:spotlessJavaCheck
> > :geode-json:spotlessCheck
> > :geode-json:test UP-TO-DATE
> > :geode-json:check
> > :geode-json:build
> > :geode-json:distributedTest UP-TO-DATE
> > :geode-json:flakyTest UP-TO-DATE
> > :geode-json:integrationTest UP-TO-DATE
> > :geode-junit:javadoc
> > :geode-junit:javadocJar
> > :geode-junit:sourcesJar
> > :geode-junit:signArchives SKIPPED
> > :geode-junit:assemble
> > :geode-junit:compileTestJava
> > :geode-junit:processTestResources UP-TO-DATE
> > :geode-junit:testClasses
> > :geode-junit:checkMissedTests
> > :geode-junit:spotlessJavaCheck
> > :geode-junit:spotlessCheck
> > :geode-junit:test
> > :geode-junit:check
> > :geode-junit:build
> > :geode-junit:distributedTest
> > :geode-junit:flakyTest
> > :geode-junit:integrationTest
> > :geode-lucene:assemble
> > :geode-lucene:compileTestJava
> > Download https://repo1.maven.org/maven2/org/apache/lucene/
> > lucene-test-framework/6.4.1/lucene-test-framework-6.4.1.pom
> > Download https://repo1.maven.org/maven2/org/apache/lucene/
> > lucene-codecs/6.4.1/lucene-codecs-6.4.1.pom
> > Download https://repo1.maven.org/maven2/com/carrotsearch/
> > randomizedtesting/randomizedtesting-runner/2.4.
> > 0/randomizedtesting-runner-2.4.0.pom
> > Download https://repo1.maven.org/maven2/com/carrotsearch/
> > randomizedtesting/randomizedtesting-parent/2.4.
> > 0/randomizedtesting-parent-2.4.0.pom
> > Download https://repo1.maven.org/maven2/org/apache/lucene/
> > lucene-test-framework/6.4.1/lucene-test-framework-6.4.1.jar
> > Download https://repo1.maven.org/maven2/org/apache/lucene/
> > lucene-codecs/6.4.1/lucene-codecs-6.4.1.jar
> > Download https://repo1.maven.org/maven2/com/carrotsearch/
> > randomizedtesting/randomizedtesting-runner/2.4.
> > 0/randomizedtesting-runner-2.4.0.jar
> > Note: Some input files use or override a deprecated API.
> > Note: Recompile with -Xlint:deprecation for details.
> > Note: Some input files use unchecked or unsafe operations.
> > Note: Recompile with -Xlint:unchecked for details.
> > :geode-lucene:processTestResources
> > :geode-lucene:testClasses
> > :geode-lucene:checkMissedTests
> > :geode-lucene:spotlessJavaCheck
> > :geode-lucene:spotlessCheck
> > :geode-lucene:test
> > :geode-lucene:check
> > :geode-lucene:build
> > :geode-lucene:distributedTest
> > :geode-lucene:flakyTest
> > :geode-lucene:integrationTest
> > :geode-old-client-support:assemble
> > :geode-old-client-support:compileTestJava
> > :geode-old-client-support:processTestResources UP-TO-DATE
> > :geode-old-client-support:testClasses
> > :geode-old-client-support:checkMissedTests
> > :geode-old-client-support:spotlessJavaCheck
> > :geode-old-client-support:spotlessCheck
> > :geode-old-client-support:test
> > :geode-old-client-support:check
> > :geode-old-client-support:build
> > :geode-old-client-support:distributedTest
> > :geode-old-client-support:flakyTest
> > :geode-old-client-support:integrationTest
> > :geode-old-versions:javadoc UP-TO-DATE
> > :geode-old-versions:javadocJar
> > :geode-old-versions:sourcesJar
> > :geode-old-versions:signArchives SKIPPED
> > :geode-old-versions:assemble
> > :geode-old-versions:compileTestJava UP-TO-DATE
> > :geode-old-versions:processTestResources UP-TO-DATE
> > :geode-old-versions:testClasses UP-TO-DATE
> > :geode-old-versions:checkMissedTests UP-TO-DATE
> > :geode-old-versions:spotlessJavaCheck
> > :geode-old-versions:spotlessCheck
> > :geode-old-versions:test UP-TO-DATE
> > :geode-old-versions:check
> > :geode-old-versions:build
> > :geode-old-versions:distributedTest UP-TO-DATE
> > :geode-old-versions:flakyTest 

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

[Mark Bretl]

Hi Galen,

I am able to the console log [1], test report summary [2], and artifacts
[3] without logging in. Which 'build report' are you trying to view?

--Mark

[1] https://builds.apache.org/job/Geode-nightly/749/console
[2] https://builds.apache.org/job/Geode-nightly/749/testReport/
[3] https://builds.apache.org/job/Geode-nightly/749/artifact/

On Wed, Feb 15, 2017 at 9:04 AM, Galen M O'Sullivan 
wrote:

> I don't seem to have access to see the build report. Is that restricted to
> committers only?
>
> Thanks,
> Galen
>
> On Wed, Feb 15, 2017 at 8:08 AM, Apache Jenkins Server <
> jenk...@builds.apache.org> wrote:
>
> > See 
> >
> > Changes:
> >
> > [kmiller] GEODE-2479 Remove docs reference to gemstone.com package
> >
> > [jiliao] GEODE-2474: mark NetstatDUnitTest as flaky
> >
> > [jiliao] refactor ServerStarterRule and LocatorStarterRule so that they
> > can be
> >
> > [gzhou] GEODE-2471: fix the race condition in test code.
> >
> > --
> > [...truncated 713 lines...]
> > :geode-cq:build
> > :geode-cq:distributedTest
> > :geode-cq:flakyTest
> > :geode-cq:integrationTest
> > :geode-json:assemble
> > :geode-json:compileTestJava UP-TO-DATE
> > :geode-json:processTestResources UP-TO-DATE
> > :geode-json:testClasses UP-TO-DATE
> > :geode-json:checkMissedTests UP-TO-DATE
> > :geode-json:spotlessJavaCheck
> > :geode-json:spotlessCheck
> > :geode-json:test UP-TO-DATE
> > :geode-json:check
> > :geode-json:build
> > :geode-json:distributedTest UP-TO-DATE
> > :geode-json:flakyTest UP-TO-DATE
> > :geode-json:integrationTest UP-TO-DATE
> > :geode-junit:javadoc
> > :geode-junit:javadocJar
> > :geode-junit:sourcesJar
> > :geode-junit:signArchives SKIPPED
> > :geode-junit:assemble
> > :geode-junit:compileTestJava
> > :geode-junit:processTestResources UP-TO-DATE
> > :geode-junit:testClasses
> > :geode-junit:checkMissedTests
> > :geode-junit:spotlessJavaCheck
> > :geode-junit:spotlessCheck
> > :geode-junit:test
> > :geode-junit:check
> > :geode-junit:build
> > :geode-junit:distributedTest
> > :geode-junit:flakyTest
> > :geode-junit:integrationTest
> > :geode-lucene:assemble
> > :geode-lucene:compileTestJava
> > Download https://repo1.maven.org/maven2/org/apache/lucene/
> > lucene-test-framework/6.4.1/lucene-test-framework-6.4.1.pom
> > Download https://repo1.maven.org/maven2/org/apache/lucene/
> > lucene-codecs/6.4.1/lucene-codecs-6.4.1.pom
> > Download https://repo1.maven.org/maven2/com/carrotsearch/
> > randomizedtesting/randomizedtesting-runner/2.4.
> > 0/randomizedtesting-runner-2.4.0.pom
> > Download https://repo1.maven.org/maven2/com/carrotsearch/
> > randomizedtesting/randomizedtesting-parent/2.4.
> > 0/randomizedtesting-parent-2.4.0.pom
> > Download https://repo1.maven.org/maven2/org/apache/lucene/
> > lucene-test-framework/6.4.1/lucene-test-framework-6.4.1.jar
> > Download https://repo1.maven.org/maven2/org/apache/lucene/
> > lucene-codecs/6.4.1/lucene-codecs-6.4.1.jar
> > Download https://repo1.maven.org/maven2/com/carrotsearch/
> > randomizedtesting/randomizedtesting-runner/2.4.
> > 0/randomizedtesting-runner-2.4.0.jar
> > Note: Some input files use or override a deprecated API.
> > Note: Recompile with -Xlint:deprecation for details.
> > Note: Some input files use unchecked or unsafe operations.
> > Note: Recompile with -Xlint:unchecked for details.
> > :geode-lucene:processTestResources
> > :geode-lucene:testClasses
> > :geode-lucene:checkMissedTests
> > :geode-lucene:spotlessJavaCheck
> > :geode-lucene:spotlessCheck
> > :geode-lucene:test
> > :geode-lucene:check
> > :geode-lucene:build
> > :geode-lucene:distributedTest
> > :geode-lucene:flakyTest
> > :geode-lucene:integrationTest
> > :geode-old-client-support:assemble
> > :geode-old-client-support:compileTestJava
> > :geode-old-client-support:processTestResources UP-TO-DATE
> > :geode-old-client-support:testClasses
> > :geode-old-client-support:checkMissedTests
> > :geode-old-client-support:spotlessJavaCheck
> > :geode-old-client-support:spotlessCheck
> > :geode-old-client-support:test
> > :geode-old-client-support:check
> > :geode-old-client-support:build
> > :geode-old-client-support:distributedTest
> > :geode-old-client-support:flakyTest
> > :geode-old-client-support:integrationTest
> > :geode-old-versions:javadoc UP-TO-DATE
> > :geode-old-versions:javadocJar
> > :geode-old-versions:sourcesJar
> > :geode-old-versions:signArchives SKIPPED
> > :geode-old-versions:assemble
> > :geode-old-versions:compileTestJava UP-TO-DATE
> > :geode-old-versions:processTestResources UP-TO-DATE
> > :geode-old-versions:testClasses UP-TO-DATE
> > :geode-old-versions:checkMissedTests UP-TO-DATE
> > :geode-old-versions:spotlessJavaCheck
> > :geode-old-versions:spotlessCheck
> > :geode-old-versions:test UP-TO-DATE
> > :geode-old-versions:check
> > :geode-old-versions:build
> > :geode-old-versions:distributedTest UP-TO-DATE
> > :geode-old-versions:flakyTest 

Re: Automating docker builds for geode-native

[Mark Bretl]

+1

On Fri, Feb 10, 2017 at 1:14 PM, Michael William Dodge 
wrote:

> I think this would be a good idea as configuring a machine for building
> can be a barrier to entry for people wishing to contribute.
>
> Sarge
>
> > On 10 Feb, 2017, at 12:29, Anthony Baker  wrote:
> >
> > The geode-native build, like most c++ projects, requires a fairly
> specific toolchain.  Now that we have a docker build environment [1], I’d
> like to ask INFRA to automate the creation and publishing of docker images
> for geode-native.  This can be done by integrating GitHub / DockerHub [2].
> Note that the docker image would *only* be for build purposes and would not
> contain source or binaries from geode-native.  By publishing our build
> toolchain in a docker image:
> >
> > 1) it makes contributing easier
> > 2) it makes our travis-ci builds faster (currently at ~30min)
> > 3) it paves the way to create a nightly Jenkins job for geode-native
> >
> > I suggest publishing this image under the apache namespace [3] as
> geode-native-build.  Thoughts?
> >
> > Anthony
> >
> > [1] https://github.com/apache/geode-native/blob/develop/
> docker/Dockerfile
> > [2] https://issues.apache.org/jira/browse/INFRA-11584?jql=
> project%20%3D%20INFRA%20AND%20text%20~%20docker
> > [3] https://hub.docker.com/u/apache/
>
>

Re: Review Request 56520: GEODE-2460: update dependency versions

[Mark Bretl]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56520/#review165255
---


Ship it!




Ship It!

- Mark Bretl


On Feb. 10, 2017, 3:39 p.m., Kirk Lund wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/56520/
> ---
> 
> (Updated Feb. 10, 2017, 3:39 p.m.)
> 
> 
> Review request for geode, Anthony Baker, anilkumar gingade, Bruce Schuchardt, 
> Dave Barnes, Darrel Schneider, Hitesh Khamesra, Jacob Barrett, Jens Deppe, 
> Jinmei Liao, Joey McAllister, Jared Stewart, Karen Miller, Kevin Duling, Udo 
> Kohlmeyer, and Dan Smith.
> 
> 
> Bugs: GEODE-2460
> https://issues.apache.org/jira/browse/GEODE-2460
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-2460: update dependency versions
> 
> Update several dependencies so that geode develop uses the latest version.
> 
> These changes fully pass precheckin. Please let me know which dependencies 
> should NOT be updated for any reason and I'll retest with a list of 
> dependencies that it's ok to update and file appropriate Jira ticket(s).
> 
> If you see any dependencies changed in the diff that require me to run any 
> tests not in precheckin, please let me know either in review or direct 
> message.
> 
> [EDIT: I just added the following list categories by test vs main]
> 
> Update the following dependency versions defined in
> gradle/dependency-versions.properties.
> 
> Update major versions (compile test only):
> 
> * org.apache.bcel:bcel:6.0
> 
> Update minor versions (distributed in release):
> 
> * commons-beanutils:1.9.3 
> * commons-fileupload:1.3.2 
> * commons-io:2.5 
> * commons-lang:2.6
> * commons-logging:1.2
> * commons-modeler:2.0.1
> * fastutil:7.0.13
> * guava:21.0
> * jansi:1.14
> * javax.mail-api:1.4.7
> * jline:2.14.3
> * jopt-simple:5.0.3
> * log4j-api:2.7
> * log4j-core:2.7
> * log4j-jcl:2.7
> * log4j-jul:2.7
> * log4j-slf4j-impl:2.7
> * netty-all:4.1.7.Final
> * shiro-core:1.3.2
> * slf4j-api:1.7.22
> 
> Update minor versions (compile tests and main):
> 
> * assertj-core:3.6.2
> * cglib:cglib:3.2.4
> * commons-configuration:1.10
> * derby:10.13.1.1
> * google-gson:2.8.0
> * httpclient:4.5.2
> * httpcore:4.4.6
> * hsqldb:2.3.4
> * javassist:3.21.0-GA
> * jedis:2.9.0
> * JUnitParams:1.0.6
> * mockrunner:1.1.2
> * mortbay-jetty-servlet-api:2.5.20110712
> * phantomjsdriver:1.3.0
> * powermock-core:1.6.6
> * powermock-module-junit4:1.6.6
> * powermock-api-mockito:1.6.6
> * selenium-api:3.0.1
> * selenium-remote-driver:3.0.1
> * selenium-support:3.0.1
> * spymemcached:2.12.2
> * system-rules:1.16.1
> * tomcat-catalina:7.0.73 (tomcat7)
> * tomcat-coyote:7.0.73 (tomcat7)
> * tomcat-juli:7.0.73 (tomcat7)
> * tomcat-catalina:8.5.9 (tomcat8)
> * tomcat-coyote:8.5.9 (tomcat8)
> * tomcat-juli:8.5.9 (tomcat8)
> 
> 
> Diffs
> -
> 
>   geode-assembly/src/main/dist/LICENSE 
> 601ba81005a11e4038eff5a19b61771b1ca9e121 
>   geode-docs/managing/logging/configuring_log4j2.html.md.erb 
> 06b5c56a79804596977d531312b63743c7ba0d30 
>   
> geode-site/website/content/docs/guide/10/managing/logging/configuring_log4j2.html
>  b02422b104cfcea14a34522d35fcbe0e391d8db7 
>   gradle/dependency-versions.properties 
> a0b291e55220e303b1608dbe5f3eb4cf3e510e4b 
> 
> Diff: https://reviews.apache.org/r/56520/diff/
> 
> 
> Testing
> ---
> 
> precheckin passed
> uiTest passed
> 
> 
> Thanks,
> 
> Kirk Lund
> 
>

Re: Volunteer For Creating February Board Report

[Mark Bretl]

Thanks Dave!

--Mark

On Thu, Feb 2, 2017 at 2:11 PM, Dave Barnes <dbar...@pivotal.io> wrote:

> I'll volunteer for February.
>
> On Thu, Feb 2, 2017 at 10:50 AM, Mark Bretl <mbr...@apache.org> wrote:
>
> > Hi,
> >
> > Its that time again for us to create a board report for the February, the
> > 15th, board meeting, are there any volunteers for creating a draft?
> >
> > Initial report should be submitted next wednesday, February 8th. We can
> > edit the report until Friday the 10th, which then it is customary for
> board
> > members to start reviewing reports.
> >
> > Template report can be found at:
> > https://cwiki.apache.org/confluence/display/GEODE/ASF+
> > Board+Report+Template
> >
> > Best Regards,
> >
> > --Mark
> >
>

Re: JIRA access request

[Mark Bretl]

Hi Ernie,

I have added you to the Geode project. Thanks for joining!

--Mark

On Fri, Feb 3, 2017 at 2:08 PM, Ernest Burghardt 
wrote:

> Hello,
>
> May I please be added to Contributor on the Geode JIRA?
>
> Thanks in advance,
> Ernie
>

Re: geode git commit: GEODE-2421: Adding packer portion of making a VS2015 dev AMI

[Mark Bretl]

Hi,

How does/will this help the community?

--Mark

On Thu, Feb 2, 2017 at 2:25 PM,  wrote:

> Repository: geode
> Updated Branches:
>   refs/heads/next-gen-native-client-software-grant e79c4072b -> 340f2fca8
>
>
> GEODE-2421: Adding packer portion of making a VS2015 dev AMI
>
> This closes #384
>
>
> Project: http://git-wip-us.apache.org/repos/asf/geode/repo
> Commit: http://git-wip-us.apache.org/repos/asf/geode/commit/340f2fca
> Tree: http://git-wip-us.apache.org/repos/asf/geode/tree/340f2fca
> Diff: http://git-wip-us.apache.org/repos/asf/geode/diff/340f2fca
>
> Branch: refs/heads/next-gen-native-client-software-grant
> Commit: 340f2fca80d9388155ed0911712f9a830211b32b
> Parents: e79c407
> Author: Ernest Burghardt 
> Authored: Thu Feb 2 14:03:10 2017 -0800
> Committer: Dan Smith 
> Committed: Thu Feb 2 14:24:20 2017 -0800
>
> --
>  packer/windows-2012-vs-2015.json | 64 +++
>  packer/windows/install-vs-2015-community.ps1 |  9 
>  2 files changed, 73 insertions(+)
> --
>
>
> http://git-wip-us.apache.org/repos/asf/geode/blob/340f2fca/p
> acker/windows-2012-vs-2015.json
> --
> diff --git a/packer/windows-2012-vs-2015.json
> b/packer/windows-2012-vs-2015.json
> new file mode 100644
> index 000..da82b94
> --- /dev/null
> +++ b/packer/windows-2012-vs-2015.json
> @@ -0,0 +1,64 @@
> +{
> +  "variables":{
> +"region":"us-west-2",
> +"source_ami":"ami-ac5395cc",
> +"source_image_name":"X.vmx",
> +"image_name":"windows-2012-vs-2015"
> +  },
> +  "builders":[
> +{
> +  "type":"amazon-ebs",
> +  "instance_type":"t2.large",
> +  "ami_name":"native-{{user `version`}}-{{user `image_name`}}
> {{timestamp}}",
> +  "access_key":"{{user `aws_access_key`}}",
> +  "secret_key":"{{user `aws_secret_key`}}",
> +  "region":"{{user `region`}}",
> +  "source_ami":"{{user `source_ami`}}",
> +  "subnet_id":"{{user `subnet_id`}}",
> +  "vpc_id":"{{user `vpc_id`}}",
> +  "tags":{
> +"team":"native",
> +"version":"{{user `version`}}",
> +"source_ami":"{{user `source_ami`}}"
> +  },
> +  "communicator":"winrm",
> +  "winrm_username":"Administrator",
> +  "launch_block_device_mappings":[
> +{
> +  "device_name":"/dev/sda1",
> +  "delete_on_termination":true,
> +  "volume_size":60
> +}
> +  ]
> +}
> +  ],
> +  "provisioners":[
> +{
> +  "pause_before":"30s",
> +  "type":"file",
> +  "source":"windows/Packer.psm1",
> +  "destination":"Documents/WindowsPowerShell/Modules/Packer/
> Packer.psm1"
> +},
> +{
> +  "type":"powershell",
> +  "scripts":[
> +"windows/install-vs-2015-community.ps1"
> +  ]
> +},
> +{
> +  "type":"powershell",
> +  "scripts":[
> +"windows/cleanup.ps1"
> +  ]
> +},
> +{
> +  "type":"powershell",
> +  "scripts":[
> +"windows/setup-ec2config.ps1"
> +  ],
> +  "only":[
> +"amazon-ebs"
> +  ]
> +}
> +  ]
> +}
>
> http://git-wip-us.apache.org/repos/asf/geode/blob/340f2fca/p
> acker/windows/install-vs-2015-community.ps1
> --
> diff --git a/packer/windows/install-vs-2015-community.ps1
> b/packer/windows/install-vs-2015-community.ps1
> new file mode 100644
> index 000..c175410
> --- /dev/null
> +++ b/packer/windows/install-vs-2015-community.ps1
> @@ -0,0 +1,9 @@
> +# TODO AdminDeploy.xml
> +# vs_community.exe /AdminFile C:\Users\Administrator\AdminDeployment.xml
> /Log setup.log /Passive
> +Set-PSDebug -Trace 0
> +
> +Import-Module Packer
> +
> +$log = "vs_community.log"
> +
> +choco install visualstudio2015community -confirm
>
>

Re: The next release (v1.1.0)

[Mark Bretl]

Do we think we can get these done and get a release before the next board
meeting (2/15)? I think it would be an excellent point on our report.

Best Regards,

--Mark

On Tue, Jan 24, 2017 at 12:09 PM, Hitesh Khamesra <
hitesh...@yahoo.com.invalid> wrote:

> Update: Three more ticket for first release candidate..
>
> GEODE-2300 Document default names for start locator/server
> GEODE-2353 Verify no clear-text passwords in documentation
> GEODE-2282 Provide ability to sort field while creating pdxType for jSON
> document(Need to document system property)
>
> Thanks.HItesh
>
>
>
>   From: Hitesh Khamesra 
>  To: "dev@geode.apache.org" 
>  Sent: Monday, January 16, 2017 12:35 PM
>  Subject: Re: The next release (v1.1.0)
>
> Update: We are waiting on following tickets for first release candidate.
>
> 1.  GEODE-2296 GetFunctionAttribute command is throwing an Anonymouse User
> Exception
> 2.  GEODE-2277 client cache fails to deserialize a PdxInstance due to
> InternalGemFireError
> 3.  GEODE-2031 Host documentation for releases
> 4.  GEODE-1965 Create backward-compatibility unit test framework
>
> Thanks.HItesh
>
>   From: Anthony Baker 
>  To: dev@geode.apache.org
>  Sent: Monday, January 9, 2017 9:49 AM
>  Subject: Re: The next release (v1.1.0)
>
> Updates:
>
> 1) I did a first round of changes on GEODE-2142, should be enough for
> v1.1.0.
> 2) Any volunteers to look at GEODE-2031 or GEODE-1965?
> 3) Are there other open issues that should be included in the release?
> 4) Last call for a release manager…  :-)
>
> Thanks,
> Anthony
>
>
> > On Jan 6, 2017, at 10:13 AM, Anthony Baker  wrote:
> >
> > Our last release was on October 25.  I think we’re past due for another
> one!  We’ve had lots of great contributions since 1.0.0-incubating and now
> that we’re are a top-level project we can drop the “-incubating” qualifier.
> >
> > I reviewed our open JIRA issues and would like to include the following
> in the release:
> >
> > GEODE-2142 - JSON license incompatibility
> > We can update the NOTICE files and leave the JSON dependency alone
> (as long as we do another release before April 30).
> >
> > GEODE-1965 - backwards compatibility tests
> > I’d like to make sure we haven’t broken anything since our last
> release.
> >
> > GEODE-2031 - versioned documentation
> > Seems relatively straightforward?
> >
> > The remaining issues that are tagged with v1.1.0 [1] could be pushed to
> a following release IMO.  Thoughts?
> >
> > Regarding the release manager, I can do the dirty work if no one else
> wants to volunteer :-)
> >
> > Anthony
> >
> > [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20G
> EODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20%
> 3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%
> 20DESC%2C%20created%20ASC
> >
> >> On Nov 21, 2016, at 9:26 AM, Anthony Baker  wrote:
> >>
> >> Now that graduation is done (!!), we need to organize our next
> release.  I propose we focus on completing the transition to TLP and
> cleaning up “incubating" references.  The sequence would look something
> like this:
> >>
> >> 1) Transition the git repo, mailing lists, etc.
> >> 2) Update incubating references in source, docs, website, wiki, …
> >> 3) Do a release.
> >>
> >> Thoughts?
> >>
> >> We need a release manager.  Any volunteers?
> >>
> >> Also, we need to rename the JIRA version from 1.1.0-incubating to
> 1.1.0.  Can someone with JIRA karma help?
> >>
> >> Anthony
> >>
> >
>
>
>
>
>
>

Re: Review Request 55393: GEODE-2260 Remove geode-examples from geode repo and geode build

[Mark Bretl]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/55393/#review161776
---


Ship it!




Ship It!

- Mark Bretl


On Jan. 10, 2017, 2:39 p.m., Karen Miller wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/55393/
> ---
> 
> (Updated Jan. 10, 2017, 2:39 p.m.)
> 
> 
> Review request for geode, Anthony Baker, William Markito, Mark Bretl, and Dan 
> Smith.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-2260 Remove geode-examples from geode repo and geode build
> 
> 
> Diffs
> -
> 
>   build.gradle c9915358bd7b7071ddae9f8c058b2388db5a415b 
>   geode-assembly/build.gradle dba5dc768a0b4829aff17c4143e8da3b87106319 
>   geode-examples/.gitignore b1001a6575698224615e5d4b6ff804e9c4506d0a 
>   geode-examples/README.md 62666035ab1bde5f9d5548e887e0133f006c2ef9 
>   geode-examples/build.gradle 1e638bc2f18f5aed2ba007e60e7b8e48711383b9 
>   geode-examples/gradle.properties c1739aff2825d87e10717f877cc4a12f4101c6c1 
>   geode-examples/gradle/wrapper/gradle-wrapper.jar 
> 2c6137b87896c8f70315ae454e00a969ef5f6019 
>   geode-examples/gradle/wrapper/gradle-wrapper.properties 
> 6132c99fbc50c6921e25432874c31a55382ef8fc 
>   geode-examples/gradlew 9d82f78915133e1c35a6ea51252590fb38efac2f 
>   geode-examples/gradlew.bat 5f192121eb4f5b109f22fa96a6246eb39e749ed6 
>   geode-examples/replicated/.gitignore 
> b858ea877b065d2420484a484d649f98054c9cc0 
>   geode-examples/replicated/README.md 
> ea923ddc76b3143bc288daf615e2c6a02e84447d 
>   geode-examples/replicated/build.gradle 
> 52283ecef776b3f6a484bdc6e7cc3cdc5b1ffe29 
>   geode-examples/replicated/scripts/.gitignore 
> 32f8870d0e0514786c159a18c9bcc6b62ac48956 
>   geode-examples/replicated/scripts/pidkiller.sh 
> ecf8f2d6911121f12df29d69dbbde7c0a67b5ced 
>   geode-examples/replicated/scripts/setEnv.sh 
> e9e860e271f523d4818f13b73de5df64897c19ed 
>   geode-examples/replicated/scripts/startAll.sh 
> 2b08f197191ced868481462752b91cbe7d6e45b6 
>   geode-examples/replicated/scripts/stopAll.sh 
> a6364a861395e8e2077ff63f27946eee616e0b6b 
>   
> geode-examples/replicated/src/main/java/org/apache/geode/examples/replicated/BaseClient.java
>  3e656f6a5b86b226db3611559eae13f92bf76b38 
>   
> geode-examples/replicated/src/main/java/org/apache/geode/examples/replicated/Consumer.java
>  7954bb57b7a86bfe4baf8ba3b9798d713f71830e 
>   
> geode-examples/replicated/src/main/java/org/apache/geode/examples/replicated/Producer.java
>  79d5dfecb2c21a09a9f926d505d466490e18c0b6 
>   
> geode-examples/replicated/src/test/java/org/apache/geode/examples/replicated/ConsumerTest.java
>  2fab5087c0ce41dfeb57d2c97113165051d84096 
>   
> geode-examples/replicated/src/test/java/org/apache/geode/examples/replicated/ProducerTest.java
>  9b4a2511bf27b83dbcd5552a5ed46ac2d85c1163 
>   
> geode-examples/replicated/src/test/java/org/apache/geode/examples/replicated/ReplicatedTest.java
>  ab84485f8cd26a7da246fb59dc7856c79d1bcca2 
>   geode-examples/settings.gradle 432a8ebc38f85e7e3e6c8b7d71328b90bc1356e4 
>   
> geode-examples/utils/src/main/java/org/apache/geode/example/utils/ShellUtil.java
>  c5290b826ab40df4474e714e2a4d298e9f10e7f5 
> 
> Diff: https://reviews.apache.org/r/55393/diff/
> 
> 
> Testing
> ---
> 
> Ran
> `./gradlew precheckin -xdistributedTest -xintegrationTest -xflakyTest`
> to verify that a geode-examples directory is not included in the source 
> distribution.
> 
> Ran
> `./gradlew build -Dskip.tests=true`
> to verify no errors in the build (without tests).
> 
> Ran
> `./gradlew tasks`
> to observe that there were no tasks involving Examples.
> 
> 
> Thanks,
> 
> Karen Miller
> 
>

Re: Native Client Directory Structure

[Mark Bretl]

Jake,

Having all the clients in the repository is nice, however, has there been
thought to have them in their own repository? Now that we are a TLP, we do
have that capability, as seen with the 'geode-examples' repository.

--Mark

On Mon, Jan 16, 2017 at 10:38 AM, Udo Kohlmeyer 
wrote:

> -1 "geode-native" directory name
>
> +1 "geode-client" directory name
>
> Maybe the directories for the different clients are by language, so we
> omit the "geode" prefix i.e
>
> geode-client/
>c++,
>net
>java
>python
>
>
> If clients are in their own project, then the clients can be independently
> versioned of the server code. imo, there should be no need for them to be
> in lock-stead with the server code.
>
> --Udo
>
>
>
> On 1/16/17 08:52, Jacob Barrett wrote:
>
>> Let's try this again. Using the +1 mechanism for a multipart email is
>> tough
>> so please include a comment on which part you are +1ing.
>>
>> Also, I want to revise my suggestion to just call the directory
>> 'geode-native' rather than 'geode-nativeclient'. Simply because I am lazy
>> and don't want to type the extra 6 letters all the time.
>>
>> -Jake
>>
>> On Mon, Jan 16, 2017 at 8:26 AM Jacob Barrett 
>> wrote:
>>
>> One of the first things necessary to get NC merged into the the develop
>>> branch is understanding where it will go under the current geode project
>>> structure.
>>>
>>> The quick and obvious solution is adding a 'geode-nativeclient`
>>> subproject
>>> and relocating all the NC sources into that directory.
>>>
>>> Given that NC consists of two semi-distinct clients, C++ and .NET, it may
>>> also make sense to organize more of a hierarchy. Consider:
>>> geode-client/
>>>  geode++
>>>  geode.net
>>> (or some other more creative names)
>>> Keep in mind that today the .NET client is very tightly coupled with the
>>> C++ client, so you can't build .NET without first building C++.
>>>
>>> My suggestion would be to do the quick and easy now and as we continue to
>>> refine and refactor and hopefully write the .NET in pure CLI we make that
>>> move them. Perhaps by that time there will be a pure Java client to
>>> include
>>> in that structure.
>>>
>>> Thoughts?
>>>
>>>
>>> -Jake
>>>
>>>
>>>
>

Re: Hosted API docs update?

[Mark Bretl]

Latest development javadocs built with the nightly build and are available
at
https://builds.apache.org/view/G/view/Geode/job/Geode-nightly/lastSuccessfulBuild/artifact/geode-assembly/build/install/apache-geode/javadoc/

--Mark

On Fri, Jan 13, 2017 at 11:31 AM, Dave Barnes  wrote:

> @Anthony Thanks for the pointer, but I guess I need a little more detail.
> When I look at the javadocs in my Geode source repo, I find a set at
> geode-assembly/build/javadocs that's labeled 1.1.0-SNAPSHOT.
> I went to the Geode website Releases page to download the binary
> distribution (http://geode.apache.org/releases/). It offers v
> 1.0.0-incubating.
>
>
>
> On Fri, Jan 13, 2017 at 11:01 AM, Sai Boorlagadda <
> sai.boorlaga...@gmail.com
> > wrote:
>
> > +1 to link API docs to release page.
> >
> > On Fri, Jan 13, 2017 at 10:42 AM, Anthony Baker 
> wrote:
> >
> > > +1
> > >
> > > I’d would like to link the docs + javadocs from the release page,
> similar
> > > to what we do for the release archives.
> > >
> > > Anthony
> > >
> > >
> > > > On Jan 13, 2017, at 10:39 AM, Joey McAllister <
> jmcallis...@pivotal.io>
> > > wrote:
> > > >
> > > > Do we also want to archive the API
> > > > documentation, so the Apache Geode 1.0 APIs are still available when
> we
> > > > push Apache Geode 1.1?
> > >
> > >
> >
>

Re: ASF Board Report for Geode - Initial Reminder for January 2017

[Mark Bretl]

Thanks for your help Anthony.

I will go ahead and submit this report with the modification we have a new
(Hitesh) release manager for the 1.1.0 release.

If anyone has additional changes, we can edit the report until Friday,
which is when all project reports begin to be reviewed.

One more month and we will be on quarterly reporting...

--Mark

On Mon, Jan 9, 2017 at 10:07 AM, Mark Bretl <asf.mbr...@gmail.com> wrote:

> Thanks Anthony for the initial status.
>
> Here are the stats for the month:
>
> ## Mailing list activity:
>
>  - dev@geode.apache.org:
>
>  - 154 subscribers (down -4 in the last 3 months):
>  - 3117 emails sent to list (1573 in previous quarter)
>
>  - iss...@geode.apache.org:
>
>  - 55 subscribers (up 0 in the last 3 months):
>  - 1983 emails sent to list (2807 in previous quarter)
>
>  - u...@geode.apache.org:
>
>  - 201 subscribers (up 16 in the last 3 months):
>  - 301 emails sent to list (161 in previous quarter)
>
>
> ## JIRA activity:
>
>  - 298 JIRA tickets created in the last 3 months
>  - 264 JIRA tickets closed/resolved in the last 3 months
>
> --Mark
>
> On Mon, Jan 9, 2017 at 9:43 AM, Anthony Baker <aba...@pivotal.io> wrote:
>
>> Mark, can you add in the subscriber numbers so we can be ready to submit
>> the report by Wed Jan 11?
>>
>> Thanks,
>> Anthony
>>
>> > On Jan 5, 2017, at 2:08 PM, Anthony Baker <aba...@pivotal.io> wrote:
>> >
>> > I volunteered!
>> >
>> > Here’s a rough draft, please review and comment:
>> >
>> > ## Description:
>> > - Apache Geode provides a database-like consistency model, reliable
>> transaction processing and a shared-nothing architecture to maintain very
>> low latency performance with high concurrency processing.
>> >
>> > ## Issues:
>> > - There are no issues requiring board attention at this time.
>> >
>> > ## Activity:
>> > - New proposal on improving JSON serialization and extending the
>> serialization framework to allow other libraries to be used.
>> > - Example code is moving to a new repo to make it easier for end users
>> to acquire and run the examples.
>> > - Lots of discussion around product configuration and how it ought to
>> work
>> >
>> > ## Health report:
>> > - We have received contributions from 10 new community members (more
>> than 30 code submissions as well as email and JIRA’s).
>> > - In December we saw the mailing list activity on dev@geode more than
>> double compared to the previous month.
>> > - We’re continuing to work on attracting new contributors and making it
>> easier to participate in the community.
>> > - We need to nominate a release manager for v1.1.0 and issue our next
>> release.
>> >
>> > ## PMC changes:
>> > - TBD
>> >
>> > ## Committer base changes:
>> > - TBD
>> >
>> > ## Releases:
>> > - Last release was 1.0.0-incubating issued on October 25, 2016.
>> >
>> > ## Mailing list activity:
>> > - dev@geode.apache.org <mailto:dev@geode.apache.org>:
>> >- PMC Chair to provide subscriber details
>> >- 1493 emails sent to list (591 in previous month)
>> > - iss...@geode.apache.org <mailto:iss...@geode.apache.org>:
>> >- PMC Chair to provide subscriber details
>> >- 694 emails sent to list (765 in previous month)
>> > - u...@geode.apache.org <mailto:u...@geode.apache.org>:
>> >- PMC Chair to provide subscriber details
>> >- 146 emails sent to list (52 in previous month)
>> >
>> > ## JIRA activity:
>> > - PMC Chair is able to provide statistics
>> >
>> >
>> > Anthony
>> >
>> >
>> >> On Jan 4, 2017, at 9:31 AM, Anthony Baker <aba...@pivotal.io > aba...@pivotal.io>> wrote:
>> >>
>> >> Any volunteers to write the Jan report?  Given that it needs to be
>> submitted by 1/11 we need a draft posted for review in the next few days.
>> >>
>> >> Anthony
>> >>
>> >>
>> >>> Begin forwarded message:
>> >>>
>> >>> From: Brett Porter <br...@apache.org <mailto:br...@apache.org>>
>> >>> Subject: ASF Board Report for Geode - Initial Reminder for January
>> 2017
>> >>> Date: December 27, 2016 at 1:53:30 PM PST
>> >>> To: Mark Bretl <mbr...@apache.org <mailto:mbr...@apache.org>>
>> >>> Cc: priv...@geode.apache.org &

Re: ASF Board Report for Geode - Initial Reminder for January 2017

[Mark Bretl]

Thanks Anthony for the initial status.

Here are the stats for the month:

## Mailing list activity:

 - dev@geode.apache.org:

 - 154 subscribers (down -4 in the last 3 months):
 - 3117 emails sent to list (1573 in previous quarter)

 - iss...@geode.apache.org:

 - 55 subscribers (up 0 in the last 3 months):
 - 1983 emails sent to list (2807 in previous quarter)

 - u...@geode.apache.org:

 - 201 subscribers (up 16 in the last 3 months):
 - 301 emails sent to list (161 in previous quarter)


## JIRA activity:

 - 298 JIRA tickets created in the last 3 months
 - 264 JIRA tickets closed/resolved in the last 3 months

--Mark

On Mon, Jan 9, 2017 at 9:43 AM, Anthony Baker <aba...@pivotal.io> wrote:

> Mark, can you add in the subscriber numbers so we can be ready to submit
> the report by Wed Jan 11?
>
> Thanks,
> Anthony
>
> > On Jan 5, 2017, at 2:08 PM, Anthony Baker <aba...@pivotal.io> wrote:
> >
> > I volunteered!
> >
> > Here’s a rough draft, please review and comment:
> >
> > ## Description:
> > - Apache Geode provides a database-like consistency model, reliable
> transaction processing and a shared-nothing architecture to maintain very
> low latency performance with high concurrency processing.
> >
> > ## Issues:
> > - There are no issues requiring board attention at this time.
> >
> > ## Activity:
> > - New proposal on improving JSON serialization and extending the
> serialization framework to allow other libraries to be used.
> > - Example code is moving to a new repo to make it easier for end users
> to acquire and run the examples.
> > - Lots of discussion around product configuration and how it ought to
> work
> >
> > ## Health report:
> > - We have received contributions from 10 new community members (more
> than 30 code submissions as well as email and JIRA’s).
> > - In December we saw the mailing list activity on dev@geode more than
> double compared to the previous month.
> > - We’re continuing to work on attracting new contributors and making it
> easier to participate in the community.
> > - We need to nominate a release manager for v1.1.0 and issue our next
> release.
> >
> > ## PMC changes:
> > - TBD
> >
> > ## Committer base changes:
> > - TBD
> >
> > ## Releases:
> > - Last release was 1.0.0-incubating issued on October 25, 2016.
> >
> > ## Mailing list activity:
> > - dev@geode.apache.org <mailto:dev@geode.apache.org>:
> >- PMC Chair to provide subscriber details
> >- 1493 emails sent to list (591 in previous month)
> > - iss...@geode.apache.org <mailto:iss...@geode.apache.org>:
> >- PMC Chair to provide subscriber details
> >- 694 emails sent to list (765 in previous month)
> > - u...@geode.apache.org <mailto:u...@geode.apache.org>:
> >- PMC Chair to provide subscriber details
> >- 146 emails sent to list (52 in previous month)
> >
> > ## JIRA activity:
> > - PMC Chair is able to provide statistics
> >
> >
> > Anthony
> >
> >
> >> On Jan 4, 2017, at 9:31 AM, Anthony Baker <aba...@pivotal.io  aba...@pivotal.io>> wrote:
> >>
> >> Any volunteers to write the Jan report?  Given that it needs to be
> submitted by 1/11 we need a draft posted for review in the next few days.
> >>
> >> Anthony
> >>
> >>
> >>> Begin forwarded message:
> >>>
> >>> From: Brett Porter <br...@apache.org <mailto:br...@apache.org>>
> >>> Subject: ASF Board Report for Geode - Initial Reminder for January 2017
> >>> Date: December 27, 2016 at 1:53:30 PM PST
> >>> To: Mark Bretl <mbr...@apache.org <mailto:mbr...@apache.org>>
> >>> Cc: priv...@geode.apache.org <mailto:priv...@geode.apache.org>
> >>> Reply-To: priv...@geode.apache.org <mailto:priv...@geode.apache.org>
> >>>
> >>> This email was sent on behalf of the ASF Board.  It is an initial
> reminder to
> >>> give you plenty of time to prepare the report.
> >>>
> >>> According to board records, you are listed as the chair of a committee
> that is
> >>> due to submit a report this month. [1] [2]
> >>>
> >>> The meeting is scheduled for Wed, 18 Jan 2017 at 10:30 PST and the
> deadline for
> >>> submitting your report is 1 full week prior to that (Wed Jan 11th)!
> >>>
> >>> Meeting times in other time zones:
> >>>
> >>>  http://timeanddate.com/s/34r0 <http://timeanddate.com/s/34r0>
> >

Re: Review Request 55280: GEODE-2142: Remove JSON from pulse

[Mark Bretl]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/55280/#review160793
---


Ship it!




Will there be another changeset to remove the code from geode-json sub-project 
as well?

- Mark Bretl


On Jan. 6, 2017, 1:09 p.m., Anthony Baker wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/55280/
> ---
> 
> (Updated Jan. 6, 2017, 1:09 p.m.)
> 
> 
> Review request for geode, Jinmei Liao, Kirk Lund, and Mark Bretl.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-2142: Add JSON usage to NOTICE 
> 
> GEODE-2142: Remove JSON dependency from pulse
> 
> Remove the Cat-X licensed JSON software from geode-pulse and replace
> it with the friendly open-json replacement.  See
> https://github.com/tdunning/open-json.
> 
> Update copyright date in NOTICE
> 
> 
> Diffs
> -
> 
>   NOTICE 4801b2aedf4f254c85cba9f27d2f99d2ca2e046b 
>   geode-assembly/src/main/dist/NOTICE 
> 83d0f3313a01881c9c651077036c17f962cd38b9 
>   geode-pulse/build.gradle 94f26f7a4106ea085ba1bc9a7001967f6b47a863 
>   
> geode-pulse/src/main/java/org/apache/geode/tools/pulse/internal/json/CDL.java 
> 6243f8f599342dbdf00d3b541dfeca9da5def508 
>   
> geode-pulse/src/main/java/org/apache/geode/tools/pulse/internal/json/Cookie.java
>  1a0fa6fb7c1edd8b81bd4513ea6786a8ba4ba59c 
>   
> geode-pulse/src/main/java/org/apache/geode/tools/pulse/internal/json/CookieList.java
>  99498f500fec9d85a30b610564c706731a55ed68 
>   
> geode-pulse/src/main/java/org/apache/geode/tools/pulse/internal/json/HTTP.java
>  234d2bddc483f71503f84886be949f2b93a7ddd6 
>   
> geode-pulse/src/main/java/org/apache/geode/tools/pulse/internal/json/HTTPTokener.java
>  09b68d872f492f65cff14a02997dbae657027992 
>   
> geode-pulse/src/main/java/org/apache/geode/tools/pulse/internal/json/JSONArray.java
>  0db27363e51eaa4e7d40724ea82ed29975df46c4 
>   
> geode-pulse/src/main/java/org/apache/geode/tools/pulse/internal/json/JSONException.java
>  fbd8866cd59817b588b84ae3bceb6e39f49fa8e2 
>   
> geode-pulse/src/main/java/org/apache/geode/tools/pulse/internal/json/JSONML.java
>  fc19ca549da14441c8895bce56d46bf880b13c90 
>   
> geode-pulse/src/main/java/org/apache/geode/tools/pulse/internal/json/JSONObject.java
>  13f2ccad8c24a346ef8eb20cd195f5bf53211eeb 
>   
> geode-pulse/src/main/java/org/apache/geode/tools/pulse/internal/json/JSONString.java
>  45585c75dbe5c0dd50359117713e078263dfb7b3 
>   
> geode-pulse/src/main/java/org/apache/geode/tools/pulse/internal/json/JSONStringer.java
>  8c5ff0826d5f6ad998d39ee73ef4a255e5fc0423 
>   
> geode-pulse/src/main/java/org/apache/geode/tools/pulse/internal/json/JSONTokener.java
>  0f4b7ee8f017c1f561f954dab1e409236d382bf2 
>   
> geode-pulse/src/main/java/org/apache/geode/tools/pulse/internal/json/JSONWriter.java
>  dea900ab240b9a1b25079dec43c1e775e7caef76 
>   geode-pulse/src/main/java/org/apache/geode/tools/pulse/internal/json/README 
> 2d7cdcf8a0ccdd29e0b1a3337da4338a51649bce 
>   
> geode-pulse/src/main/java/org/apache/geode/tools/pulse/internal/json/XML.java 
> 25675f89b6d2e22fced09dd366b18753f28b3ab7 
>   
> geode-pulse/src/main/java/org/apache/geode/tools/pulse/internal/json/XMLTokener.java
>  ff81731e11b49b649b92580fd169440c734a1006 
>   geode-pulse/src/main/webapp/META-INF/NOTICE 
> 706eda265cf0b54c73d01df85c0a79bde9082d8a 
>   
> geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/junit/BaseServiceTest.java
>  ccc147d1533142d54c8c7378c935da8f5e3234f5 
>   
> geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/junit/ClusterSelectedRegionServiceTest.java
>  77e6dd89340c59f7c15363a1d878ca3b6165d90a 
>   
> geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/junit/ClusterSelectedRegionsMemberServiceTest.java
>  512cfc78e811a3234f170b243cf3983a96fc4788 
>   
> geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/junit/MemberGatewayHubServiceTest.java
>  980a772a6a43a60befe3f4cec2c898b3e62ad038 
>   geode-web-api/src/main/webapp/META-INF/NOTICE 
> 21082b6de4fbd7ba4ec4bcb61e9e1bfda5ac162a 
>   geode-web/src/main/webapp/META-INF/NOTICE 
> 8c6e1d7faf3188599305f44c44318f6e6cfd00e6 
>   gradle/dependency-versions.properties 
> 828b0882d0813919e699d1ec83c7ba9c59f0220e 
> 
> Diff: https://reviews.apache.org/r/55280/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Anthony Baker
> 
>

Re: User permissions for Galen O'Sullivan

[Mark Bretl]

Welcome Galen!

Looking forward to seeing more contributions!

--Mark

On Thu, Jan 5, 2017 at 4:48 PM, Kirk Lund <kl...@apache.org> wrote:

> Welcome Galen!
>
>
> On Thu, Jan 5, 2017 at 2:00 PM, Galen M O'Sullivan <gosulli...@pivotal.io>
> wrote:
>
> > Thanks, Mark! I suppose I'll add a brief introduction:
> >
> > Hi, I'm Galen O'Sullivan. I joined Pivotal fairly recently. I've
> previously
> > worked at New Relic and Coherent Logix. In my free time I've been playing
> > with Rust and the Ergodox (though not at the same time). I think it's
> > pretty awesome that I can get paid to work on open source software.
> >
> > Cheers!
> >
> > Galen
> >
> > On Thu, Jan 5, 2017 at 12:03 PM, Anthony Baker <aba...@pivotal.io>
> wrote:
> >
> > > Thanks Mark.  I updated [1] with this process note.
> > >
> > > Anthony
> > >
> > > [1] https://cwiki.apache.org/confluence/display/GEODE/
> Developer+Workflow
> > >
> > > > On Jan 5, 2017, at 11:39 AM, Mark Bretl <mbr...@apache.org> wrote:
> > > >
> > > > Hi Udo (and Galen),
> > > >
> > > > I have added Galen to the Geode project in JIRA.
> > > >
> > > > For future reference, we highly encourage new contributors to ask for
> > > > themselves as a way of introducing themselves to the community. I
> think
> > > we
> > > > should add this 'instruction' to the Community page on the site [1]
> > > >
> > > > --Mark
> > > >
> > > > [1] http://geode.apache.org/community/
> > > >
> > > > On Thu, Jan 5, 2017 at 11:19 AM, Udo Kohlmeyer <
> ukohlme...@pivotal.io>
> > > > wrote:
> > > >
> > > >> Hi there,
> > > >>
> > > >> Can someone with the relevant powers and permissions add Galen
> > > O'Sullivan
> > > >> as a contributor in Apache Jira?
> > > >>
> > > >> --Udo
> > > >>
> > > >>
> > >
> > >
> >
>

Re: User permissions for Galen O'Sullivan

[Mark Bretl]

Hi Udo (and Galen),

I have added Galen to the Geode project in JIRA.

For future reference, we highly encourage new contributors to ask for
themselves as a way of introducing themselves to the community. I think we
should add this 'instruction' to the Community page on the site [1]

--Mark

[1] http://geode.apache.org/community/

On Thu, Jan 5, 2017 at 11:19 AM, Udo Kohlmeyer 
wrote:

> Hi there,
>
> Can someone with the relevant powers and permissions add Galen O'Sullivan
> as a contributor in Apache Jira?
>
> --Udo
>
>

Fwd: geode git commit: GEODE-2243: Adjust path of spotless formatter

[Mark Bretl]

Jens,

Please revert this commit. I feel like the JIRA issue, GEODE-2243, was done
with separate specific environment in mind and not done for the
community. This does not work for standard Geode development environment...

Unable to apply step Eclipse Formatter to src/main/java/org/apache/geode
/rest/internal/web/util/ValidationUtils.java: Eclipse formatter file
'/Users/mbretl/bldz/open/etc/eclipse-java-google-style.xml' does not exist.

--Mark
-- Forwarded message --
From: 
Date: Wed, Dec 21, 2016 at 2:53 PM
Subject: geode git commit: GEODE-2243: Adjust path of spotless formatter
To: comm...@geode.apache.org


Repository: geode
Updated Branches:
  refs/heads/develop eba189bb1 -> c1998d739


GEODE-2243: Adjust path of spotless formatter

- This allows projects which depend on Geode to use Geode's formatter

Signed-off-by: Scott Jewell 


Project: http://git-wip-us.apache.org/repos/asf/geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/geode/commit/c1998d73
Tree: http://git-wip-us.apache.org/repos/asf/geode/tree/c1998d73
Diff: http://git-wip-us.apache.org/repos/asf/geode/diff/c1998d73

Branch: refs/heads/develop
Commit: c1998d7398b837ee1e699bfd1952719443045d71
Parents: eba189b
Author: Jens Deppe 
Authored: Wed Dec 21 14:52:11 2016 -0800
Committer: Jens Deppe 
Committed: Wed Dec 21 14:53:25 2016 -0800

--
 build.gradle | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
--


http://git-wip-us.apache.org/repos/asf/geode/blob/c1998d73/build.gradle
--
diff --git a/build.gradle b/build.gradle
index 360310f..d788250 100755
--- a/build.gradle
+++ b/build.gradle
@@ -91,7 +91,7 @@ subprojects {
   spotless {
 lineEndings = 'unix';
 java {
-  eclipseFormatFile "${rootProject.projectDir}/etc
/eclipse-java-google-style.xml"
+  eclipseFormatFile "${rootProject.projectDir}/../
open/etc/eclipse-java-google-style.xml"
 }
   }
 }

[jira] [Commented] (GEODE-2232) Rename GemFireConfigException

[Mark Bretl (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEODE-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15768352#comment-15768352
 ] 

Mark Bretl commented on GEODE-2232:
---

I would vote for removing product names from class names as well. I think the 
addition of product names came from the history and the 'sharing' of code 
between products.
 
This seems to be a bigger topic and should be discussed on the dev list.

> Rename GemFireConfigException
> -
>
> Key: GEODE-2232
> URL: https://issues.apache.org/jira/browse/GEODE-2232
> Project: Geode
>  Issue Type: Improvement
>  Components: docs, general
>Reporter: Dor
>Assignee: Bruce Schuchardt
> Fix For: 1.1.0
>
>
> All GemFire*Exception classes should be refactor renamed to have Geode as a 
> prefix instead.
> For example:
>GemFireConfigException - Should be GeodeConfigException.
>GemFireException Should be GeodeException.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-165) Add build support for generating antlr classes from grammar

[Mark Bretl (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Bretl updated GEODE-165:
-
Assignee: Avinash Dongre  (was: Mark Bretl)

> Add build support for generating antlr classes from grammar
> ---
>
> Key: GEODE-165
> URL: https://issues.apache.org/jira/browse/GEODE-165
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Dan Smith
>Assignee: Avinash Dongre
>
> The OQL engine currently uses antlr to generate some parsing classes from 
> gemfire-core/src/main/java/com/gemstone/gemfire/cache/query/internal/parse/oql.g
> These are the generated classes. They are currently checked into the source.
> OQLLexer.java
> OQLLexerTokenTypes.java
> OQLLexerTokenTypes.txt
> OQLParser.java
> They can be generated manually by running antlr.Tool on the provided grammar.
> cd gemfire-core/src/main/java/com/gemstone/gemfire/cache/query/internal/parse/
> java -cp antlr.jar antlr.Tool oql.g
> We should add support to the gradle build to generate these classes.
> In my opinion we should also remove the checked in classes. With gradle we 
> can configure things so that the gradle eclipse target will generate these 
> classes and make them available to the IDE as well. Look at 
> gemfire-core/build.gradle for how we do this with the version properties file:
> sourceSets {
>   main {
> output.dir(generatedResources, builtBy: 'createVersionPropertiesFile')
>   }
> }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: New GEODE Jira tickets

[Mark Bretl]

I will gladly +1 Unassigned and will change it since I don't see it
affecting anyone but me :)

--Mark

On Fri, Dec 16, 2016 at 3:33 PM, Kirk Lund <kl...@apache.org> wrote:

> New GEODE Jira tickets are automatically assigned to Mark Bretl. Do we
> want that or should they be unassigned by default?
>
>

Re: [DRAFT] Geode Board Report for December 2016

[Mark Bretl]

Thanks Dan!

Report has been submitted.

--Mark

On Tue, Dec 13, 2016 at 10:48 AM, Dan Smith  wrote:

> Updated draft below with feedback from Mark and Anthony incorporated.
>
> -Dan
>
>
> ## Description:
>  - Apache Geode provides a database-like consistency model, reliable
>transaction processing and a shared-nothing architecture to maintain
>very low latency performance with high concurrency.
>
> ## Issues:
>  - No issues requiring board attention at this time
>
> ## Activity:
>  - Graduated from the incubator November 21, 2016!
>  - Released our first non-milestone release, 1.0.0-incubating.
>  - Transitioned project resources from incubator to TLP namespace.
>  - Started discussions about our first release as a TLP.
>  - Jinmei Liao presented a talk at apachecon Europe: "Implementing
> Security in Apache Geode Using Apache Shiro."
>
> ## Health report:
>  - Geode is still seeing active development. With our first
> non-milestone release we're hoping to settle into a more regular
> release cadence. We're still working to attract more contributors from
> outside of Pivotal and since graduation we're seeing more
> contributions coming in from other sources which is a good sign.
>
> ## PMC changes:
>
>  - No PMC changes since the last report to the incubator board.
>
> ## Committer base changes:
>
>  - Ken Howe joined as a committer Nov 15th.
>
> ## Releases:
>
>  - 1.0.0-incubating October 25, 2016
>  - 1.0.0-incubating.M3 August 23, 2016
>  - 1.0.0-incubating.M2 April 22, 2016
>  - 1.0.0-incubating.M1 Feb 8, 2016
>
> ## Mailing list activity:
>
>  - dev@geode.apache.org:
>
> - 154 subscribers (down -3 in the last 3 months):
> - 2258 emails sent to list (1529 in previous quarter)
>
>  - iss...@geode.apache.org:
>
> - 55 subscribers (up 0 in the last 3 months):
> - 2977 emails sent to list (2751 in previous quarter)
>
>  - u...@geode.apache.org:
>
> - 194 subscribers (up 13 in the last 3 months):
> - 187 emails sent to list (157 in previous quarter)
>
> ## JIRA activity:
>
>  - 320 JIRA tickets created in the last 3 months
>  - 279 JIRA tickets closed/resolved in the last 3 months
>

Re: [DRAFT] Geode Board Report for December 2016

[Mark Bretl]

Mail and JIRA stats:

## Mailing list activity:

 - dev@geode.apache.org:

- 154 subscribers (down -3 in the last 3 months):
- 2258 emails sent to list (1529 in previous quarter)

 - iss...@geode.apache.org:

- 55 subscribers (up 0 in the last 3 months):
- 2977 emails sent to list (2751 in previous quarter)

 - u...@geode.apache.org:

- 194 subscribers (up 13 in the last 3 months):
- 187 emails sent to list (157 in previous quarter)



## JIRA activity:

 - 320 JIRA tickets created in the last 3 months
 - 279 JIRA tickets closed/resolved in the last 3 months


--Mark

On Mon, Dec 12, 2016 at 1:17 PM, Anthony Baker  wrote:

> I think under Activity:
>
> “Transitioned project resources from incubator to TLP namespace."
>
> Anthony
>
> > On Dec 12, 2016, at 11:47 AM, Dan Smith  wrote:
> >
> > Any feedback on this one? Mark, I think you're the one that needs to
> > provide the statistics and submit this to the board. If there are no
> > comments by tomorrow I'd say go ahead and submit it.
> >
> > -Dan
> >
> > On Thu, Dec 8, 2016 at 5:20 PM, Dan Smith  wrote:
> >> Here's a draft of our report to the board for December. Please review
> >> and give your feedback. Did anyone else do a talk since our last
> >> report (written Oct 5th)? I know Jinmei presented at ApacheCon.
> >>
> >> -Dan
> >>
> >> ## Description:
> >> - Apache Geode provides a database-like consistency model, reliable
> >>   transaction processing and a shared-nothing architecture to maintain
> >>   very low latency performance with high concurrency.
> >>
> >> ## Issues:
> >> - No issues requiring board attention at this time
> >>
> >> ## Activity:
> >> - Graduated from the incubator November 21, 2016!
> >> - Released our first non-milestone release, 1.0.0-incubating
> >> - Started discussions about our first release as a TLP
> >> - Jinmei Liao presented a talk at apachecon Europe: "Implementing
> >> Security in Apache Geode Using Apache Shiro"
> >>
> >> ## Health report:
> >> - Geode is still seeing active development. With our first
> >> non-milestone release we're hoping to settle into a more regular
> >> release cadence. We're still working to attract more contributors from
> >> outside of Pivotal and since graduation we're seeing more
> >> contributions coming in from other sources which is a good sign.
> >>
> >> ## PMC changes:
> >>
> >> - No PMC changes since the last report to the incubator board.
> >>
> >> ## Committer base changes:
> >>
> >> - Ken Howe joined as a committer Nov 15th
> >>
> >> ## Releases:
> >>
> >> - 1.0.0-incubating October 25, 2016
> >> - 1.0.0-incubating.M3 August 23, 2016
> >> - 1.0.0-incubating.M2 April 22, 2016
> >> - 1.0.0-incubating.M1 Feb 8, 2016
> >>
> >> ## Mailing list activity:
> >>
> >> - PMC Chair is able to provide statistics
> >>
> >> ## JIRA activity:
> >>
> >> - PMC Chair is able to provide statistics
>
>

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

[Mark Bretl]

Are these Concourse runs available to the community?

--Mark
On Sun, Dec 11, 2016 at 12:38 PM Jinmei Liao  wrote:

> This build failed probably because of our change of some of the cluster
>
> config code. Those are not failing in concourse though. Will look into this
>
> more.
>
>
>
> On Sat, Dec 10, 2016 at 7:48 AM, Apache Jenkins Server <
>
> jenk...@builds.apache.org> wrote:
>
>
>
> > See 
>
> >
>
> > Changes:
>
> >
>
> > [adongre] GEODE-1984: Fix Issue Make GatewaySender destroy a public API
>
> >
>
> > [adongre] GEODE-1984: Addressed review comments, Removed copy pasted
>
> > repeating
>
> >
>
> > [jiliao] [GEODE-2196] Add test for Cluster Config. Refactor
>
> >
>
> > [upthewaterspout] GEODE-2186: Changing the gateway status to only looking
>
> > running status
>
> >
>
> > [abaker] Update website release references to remove incubator
>
> >
>
> > [bschuchardt] GEODE-2193 a member is kicked out immediately after joining
>
> >
>
> > --
>
> > [...truncated 1616 lines...]
>
> > :geode-cq:compileTestJavaNote: Some input files use or override a
>
> > deprecated API.
>
> > Note: Recompile with -Xlint:deprecation for details.
>
> > Note: Some input files use unchecked or unsafe operations.
>
> > Note: Recompile with -Xlint:unchecked for details.
>
> >
>
> > :geode-cq:processTestResources
>
> > :geode-cq:testClasses
>
> > :geode-cq:checkMissedTests
>
> > :geode-cq:spotlessJavaCheck
>
> > :geode-cq:spotlessCheck
>
> > :geode-cq:test
>
> > :geode-cq:check
>
> > :geode-cq:build
>
> > :geode-cq:distributedTest
>
> > :geode-cq:flakyTest
>
> > :geode-cq:integrationTest
>
> > :geode-json:assemble
>
> > :geode-json:compileTestJava UP-TO-DATE
>
> > :geode-json:processTestResources UP-TO-DATE
>
> > :geode-json:testClasses UP-TO-DATE
>
> > :geode-json:checkMissedTests UP-TO-DATE
>
> > :geode-json:spotlessJavaCheck
>
> > :geode-json:spotlessCheck
>
> > :geode-json:test UP-TO-DATE
>
> > :geode-json:check
>
> > :geode-json:build
>
> > :geode-json:distributedTest UP-TO-DATE
>
> > :geode-json:flakyTest UP-TO-DATE
>
> > :geode-json:integrationTest UP-TO-DATE
>
> > :geode-junit:javadoc
>
> > :geode-junit:javadocJar
>
> > :geode-junit:sourcesJar
>
> > :geode-junit:signArchives SKIPPED
>
> > :geode-junit:assemble
>
> > :geode-junit:compileTestJava
>
> > :geode-junit:processTestResources UP-TO-DATE
>
> > :geode-junit:testClasses
>
> > :geode-junit:checkMissedTests
>
> > :geode-junit:spotlessJavaCheck
>
> > :geode-junit:spotlessCheck
>
> > :geode-junit:test
>
> > :geode-junit:check
>
> > :geode-junit:build
>
> > :geode-junit:distributedTest
>
> > :geode-junit:flakyTest
>
> > :geode-junit:integrationTest
>
> > :geode-lucene:assemble
>
> > :geode-lucene:compileTestJavaNote: Some input files use or override a
>
> > deprecated API.
>
> > Note: Recompile with -Xlint:deprecation for details.
>
> > Note: Some input files use unchecked or unsafe operations.
>
> > Note: Recompile with -Xlint:unchecked for details.
>
> >
>
> > :geode-lucene:processTestResources
>
> > :geode-lucene:testClasses
>
> > :geode-lucene:checkMissedTests
>
> > :geode-lucene:spotlessJavaCheck
>
> > :geode-lucene:spotlessCheck
>
> > :geode-lucene:test
>
> > :geode-lucene:check
>
> > :geode-lucene:build
>
> > :geode-lucene:distributedTest
>
> > :geode-lucene:flakyTest
>
> > :geode-lucene:integrationTest
>
> > :geode-old-client-support:assemble
>
> > :geode-old-client-support:compileTestJava
>
> > :geode-old-client-support:processTestResources UP-TO-DATE
>
> > :geode-old-client-support:testClasses
>
> > :geode-old-client-support:checkMissedTests
>
> > :geode-old-client-support:spotlessJavaCheck
>
> > :geode-old-client-support:spotlessCheck
>
> > :geode-old-client-support:test
>
> > :geode-old-client-support:check
>
> > :geode-old-client-support:build
>
> > :geode-old-client-support:distributedTest
>
> > :geode-old-client-support:flakyTest
>
> > :geode-old-client-support:integrationTest
>
> > :geode-pulse:assemble
>
> > :geode-pulse:compileTestJavaNote: 
> > job/Geode-nightly/ws/geode-pulse/src/test/java/org/
>
> > apache/geode/tools/pulse/tests/ui/PulseBase.java> uses or overrides a
>
> > deprecated API.
>
> > Note: Recompile with -Xlint:deprecation for details.
>
> > Note: Some input files use unchecked or unsafe operations.
>
> > Note: Recompile with -Xlint:unchecked for details.
>
> >
>
> > :geode-pulse:processTestResources
>
> > :geode-pulse:testClasses
>
> > :geode-pulse:checkMissedTests
>
> > :geode-pulse:spotlessJavaCheck
>
> > :geode-pulse:spotlessCheck
>
> > :geode-pulse:test
>
> > :geode-pulse:check
>
> > :geode-pulse:build
>
> > :geode-pulse:distributedTest
>
> > :geode-pulse:flakyTest
>
> > :geode-pulse:integrationTest
>
> > :geode-rebalancer:assemble
>
> > :geode-rebalancer:compileTestJava
>
> > :geode-rebalancer:processTestResources UP-TO-DATE
>
> > :geode-rebalancer:testClasses
>
> > 

Re: Matching Unix Committer List And Website Committer List

[Mark Bretl]

I have added the rest of the committers from the original list which I
could, it shows up correctly in Whimsy but not in the Phonebook yet. There
are people on the website list which do not have Apache IDs, so there is
still some difference between the two lists.

If we don't want to manage two lists, I would suggest since the Apache list
is the official list anyone who wants to be listed as a member of the Geode
community, have an Apache ID and be added to the Committers list, even if
they do not commit 'code'.

Thoughts?

--Mark



On Tue, Dec 6, 2016 at 1:53 PM, Mark Bretl <mbr...@apache.org> wrote:

> Note: Moved to Dev list...
>
> Hey Dave,
>
> I am working on adding committers back to the official unix group, which
> Whimsy is using. The website will always be a secondary source, however, we
> could link to the phonebook instead of listing directly on the website.
> Since Whimsy requires credentials, I don't think that would be good choice
>
> I am working on re-adding committers which are missing from the TLP
> transition.
>
> --Mark
>
> [1] http://people.apache.org/phonebook.html?unix=geode
>
> On Tue, Dec 6, 2016 at 1:33 PM, Dave Barnes <dbar...@pivotal.io> wrote:
>
>> The whimsy committers roster differs from the Geode website's Community
>> list of committers. Is the website list obsolete, or would there be value
>> in updating it to match the whimsy list? (Adopting a 2-list policy incurs
>> some overhead going forward..)
>>
>
>

Re: Top-Level Project Tasks Completed

[Mark Bretl]

Ticket for GitHub link is fixed.
 https://issues.apache.org/jira/browse/INFRA-13052

--Mark

On Tue, Dec 6, 2016 at 3:04 PM, Mark Bretl <asf.mbr...@gmail.com> wrote:

> Ticket for ReviewBoard has now been fixed.
> https://issues.apache.org/jira/browse/INFRA-13054
>
> Ticket for JIRA is being worked on now.
> https://issues.apache.org/jira/browse/INFRA-13055
>
> --Mark
>
> On Tue, Dec 6, 2016 at 2:00 PM, Anthony Baker <aba...@pivotal.io> wrote:
>
>> Excellent! Thanks for your help getting through this transition Mark!
>>
>> Anthony
>>
>> > On Dec 6, 2016, at 1:56 PM, Mark Bretl <asf.mbr...@gmail.com> wrote:
>> >
>> > Hey Anthony,
>> >
>> > Thanks for checking these issues. Here are my updates:
>> >
>> > 1) There is an INFRA ticket, https://issues.apache.org/jira
>> /browse/INFRA-13052 <https://issues.apache.org/jira/browse/INFRA-13052>
>> > 2) I will create a ticket
>> > 3) I can create a ticket as well.
>> >
>> > --Mark
>>
>>
>

Re: Top-Level Project Tasks Completed

[Mark Bretl]

Ticket for ReviewBoard has now been fixed.
https://issues.apache.org/jira/browse/INFRA-13054

Ticket for JIRA is being worked on now.
https://issues.apache.org/jira/browse/INFRA-13055

--Mark

On Tue, Dec 6, 2016 at 2:00 PM, Anthony Baker <aba...@pivotal.io> wrote:

> Excellent! Thanks for your help getting through this transition Mark!
>
> Anthony
>
> > On Dec 6, 2016, at 1:56 PM, Mark Bretl <asf.mbr...@gmail.com> wrote:
> >
> > Hey Anthony,
> >
> > Thanks for checking these issues. Here are my updates:
> >
> > 1) There is an INFRA ticket, https://issues.apache.org/
> jira/browse/INFRA-13052 <https://issues.apache.org/jira/browse/INFRA-13052
> >
> > 2) I will create a ticket
> > 3) I can create a ticket as well.
> >
> > --Mark
>
>

Matching Unix Committer List And Website Committer List

[Mark Bretl]

Note: Moved to Dev list...

Hey Dave,

I am working on adding committers back to the official unix group, which
Whimsy is using. The website will always be a secondary source, however, we
could link to the phonebook instead of listing directly on the website.
Since Whimsy requires credentials, I don't think that would be good choice

I am working on re-adding committers which are missing from the TLP
transition.

--Mark

[1] http://people.apache.org/phonebook.html?unix=geode

On Tue, Dec 6, 2016 at 1:33 PM, Dave Barnes  wrote:

> The whimsy committers roster differs from the Geode website's Community
> list of committers. Is the website list obsolete, or would there be value
> in updating it to match the whimsy list? (Adopting a 2-list policy incurs
> some overhead going forward..)
>

Re: Top-Level Project Tasks Completed

[Mark Bretl]

Hi Dor,

Changes to the website and other Incubator branded material are being
tracked as issue GEODE-2156 [1] and will be made in the near future.

Best Regards,

--Mark

[1] https://issues.apache.org/jira/plugins/servlet/mobile#issue/GEODE-2156

On Mon, Dec 5, 2016 at 10:54 PM Dor Ben Dov <dor.ben-...@amdocs.com> wrote:

> Gregory,
>
> On the bottom of the page geode.apache.org there is still a sign that
> it's an incubation, are you going to remove this ?
>
>
>
> Regards,
>
> Dor
>
>
>
> -Original Message-
>
> From: Gregory Chase [mailto:gch...@pivotal.io]
>
> Sent: יום ג 06 דצמבר 2016 06:17
>
> To: dev@geode.apache.org
>
> Cc: us...@geode.apache.org
>
> Subject: Re: Top-Level Project Tasks Completed
>
>
>
> Yay! Congrats!
>
>
>
> On Mon, Dec 5, 2016 at 5:11 PM, Mark Bretl <mbr...@apache.org> wrote:
>
>
>
> > Hi Everyone,
>
> >
>
> > The Apache INFRA team has completed the Top-Level Project for Apache
> Geode.
>
> >
>
> > Summary of Changes:
>
> > - Website is https://geode.apache.org/
>
> > - Mailing lists (dev, users, private) now have suffix of '@
>
> > geode.apache.org'
>
> > - GitHub URL is now https://github.com/apache/geode (It has error of
>
> > 404 now, but should resolve in about 7 hours)
>
> >
>
> > If you have any issues, please email the Dev list at
>
> > 'dev@geode.apache.org '
>
> > so we can investigate.
>
> >
>
> > Thanks to everyone for their patience. Now, let's move forward with
>
> > growing this community and completing another release!
>
> >
>
> > Best Regards,
>
> >
>
> > Mark Bretl
>
> > V.P. Apache Geode
>
> >
>
>
>
>
>
>
>
> --
>
> Greg Chase
>
>
>
> Global Head, Big Data Communities
>
> http://www.pivotal.io/big-data
>
>
>
> Pivotal Software
>
> http://www.pivotal.io/
>
>
>
> 650-215-0477
>
> @GregChase
>
> Blog: http://geekmarketing.biz/
>
>
>
> 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
>
>

Re: Review Request 54321: GEODE-2156 Remove incubating references

[Mark Bretl]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54321/#review158049
---


Ship it!




Ship It!

- Mark Bretl


On Dec. 3, 2016, 8:33 a.m., Anthony Baker wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54321/
> ---
> 
> (Updated Dec. 3, 2016, 8:33 a.m.)
> 
> 
> Review request for geode, Dave Barnes, Dick Cavender, Joey McAllister, Karen 
> Miller, Mark Bretl, and Dan Smith.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> - Remove DISCLAIMER files
> - Remove "(incubating)" from project name references
> - Remove .incubator from website references
> 
> GEODE-2156: Update mailing list references
> 
> 
> GEODE-2156: Remove incubating references from the website
> 
> 
> GEODE-2156: Update repo references
> 
> 
> GEODE-2156: Fix documentation link
> 
> 
> GEODE-2156: Cleaned up nav bar links
> 
> 
> GEODE-2156: Replace incubator egg with ASF feather logo
> 
> 
> Diffs
> -
> 
>   .travis.yml e61cde51b8bee2667a6c2b1ab49c69ea20b440fe 
>   BUILDING.md 5e1e7933c59ea66211cf290191ab1f8cef8b2afd 
>   DISCLAIMER PRE-CREATION 
>   NOTICE 4801b2aedf4f254c85cba9f27d2f99d2ca2e046b 
>   README.md 955d45f4f5dd4b95f84dd89d7fcf1108678c5ae8 
>   dev-tools/docker/base/Dockerfile 1cce0ddb0d29c9e188d27481c82123e357c5b685 
>   dev-tools/docker/compile/Dockerfile 
> 6ae343a70eccf7cc4b303228118cee0b8579e79a 
>   dev-tools/docker/docs/Dockerfile 8ce7397efb584ceb3ef032d26f13795e328971fc 
>   docker/Dockerfile a42b47a3328dfff981786ce113f927888e45763a 
>   geode-assembly/src/main/dist/DISCLAIMER PRE-CREATION 
>   geode-assembly/src/main/dist/NOTICE 
> 83d0f3313a01881c9c651077036c17f962cd38b9 
>   geode-book/README.md d69354bce6fa684d635b1c03643638c7dee33251 
>   geode-book/config.yml bbc8ccc2bdffdc5a16134993ebd0683ba71e6d11 
>   geode-book/redirects.rb 81f27c834f78a5b188bb5556bfc93645fbe73262 
>   
> geode-core/src/main/java/org/apache/geode/cache/partition/PartitionListenerAdapter.java
>  b56cdf3547811cbae0b3716b83c4d2fe56b51541 
>   
> geode-core/src/main/java/org/apache/geode/internal/i18n/LocalizedStrings.java 
> 59231232bb85df22e3ca30b1bec338ef0ae033cb 
>   geode-docs/about_geode.html.md.erb 0d7f9b8d9ebe80d8b6a904e584fb76ba9fa6e66b 
>   geode-docs/getting_started/installation/install_standalone.html.md.erb 
> 9a1987e0de5b5f821d0dfc55a113e39fe80f65db 
>   geode-examples/README.md 62666035ab1bde5f9d5548e887e0133f006c2ef9 
>   geode-pulse/src/main/webapp/DataBrowser.html 
> a01df6b280decf8acd96ff6ad2f7a494a53ae682 
>   geode-pulse/src/main/webapp/Login.html 
> f093e38082a1b58a81ba936582599d28e3d2e585 
>   geode-pulse/src/main/webapp/META-INF/NOTICE 
> 706eda265cf0b54c73d01df85c0a79bde9082d8a 
>   geode-pulse/src/main/webapp/MemberDetails.html 
> bc946da8b175d23d9eba529663e1bb86c036079b 
>   geode-pulse/src/main/webapp/QueryStatistics.html 
> 543e003a0b0c447e3fe8d8e6e44d0329a168b029 
>   geode-pulse/src/main/webapp/clusterDetail.html 
> b1fc1e0a24821e40bd08a62ad53b0324102ac03c 
>   geode-pulse/src/main/webapp/regionDetail.html 
> 711ef31bd6f22636420cccd20308b4f7ac7cc769 
>   geode-site/website/README.md 56b6aeb4ab34359ffd771ce21609c3f403397dd5 
>   geode-site/website/content/community/index.html 
> 34e085c77e8803bfe7e6ac621b2b149f8c46b653 
>   geode-site/website/content/docs/index.html 
> 0a475f95b3425624b8478ca4ce55c946140b4cb3 
>   geode-site/website/content/img/asf_logo.png PRE-CREATION 
>   geode-site/website/content/img/egg-logo.png 
> 2169a2a36c49c42a2e771c0b785787eb4784d870 
>   geode-site/website/content/index.html 
> 55311d77aafa7e9065e27130b8662987b90e2563 
>   geode-site/website/content/releases/index.html 
> de0335d6bc0edd299edf44b28cdddf7f33fa15c1 
>   geode-site/website/layouts/footer.html 
> 4877109cbd3599dff81d4d5d69a6ab1c9c73d982 
>   geode-site/website/layouts/header.html 
> 618d33d43506ed6a75326998193af224c2ba6a05 
>   geode-spark-connector/doc/2_quick.md 
> 8c2fe4cf61a20fdd930cfd61e0c5df2ed505e456 
>   geode-web-api/src/main/webapp/META-INF/NOTICE 
> 21082b6de4fbd7ba4ec4bcb61e9e1bfda5ac162a 
>   geode-web/src/main/webapp/META-INF/NOTICE 
> 8c6e1d7faf3188599305f44c44318f6e6cfd00e6 
>   gradle.properties 164d482161b59534fd91bc14c7773140fbec279e 
>   gradle/publish.gradle af5ee13a2eb6f6532a0e7c73bfb2591dfde60b30 
>   gradle/sonar.gradle 32f18834b054436d29f1b4ca52c145c35b808c60 
> 
> Diff: https://reviews.apache.org/r/54321/diff/
> 
> 
> Testing
> ---
> 
> I'm holding this until the infrastructure changes are ready.
> 
> 
> Thanks,
> 
> Anthony Baker
> 
>

Re: TLP Transition Changes Coming

[Mark Bretl]

As stated last week, INFRA will be working on the TLP tasks today and I
have been notified they will be starting within the hour.

Best Regards,

--Mark



On Fri, Dec 2, 2016 at 12:44 PM, Joey McAllister 
wrote:

> +1
>
> On Fri, Dec 2, 2016 at 12:12 PM Kenneth Howe  wrote:
>
> > +1
> > > On Dec 2, 2016, at 12:10 PM, Roman Shaposhnik 
> > wrote:
> > >
> > > On Fri, Dec 2, 2016 at 11:53 AM, Dave Barnes 
> wrote:
> > >> As I recall, the committer list on the incubator page was far behind
> the
> > >> list on the product's web page (under "Community").
> > >
> > > I believe I updated it to be a pretty close match right before the
> > discussion
> > > on graduation. At any rate -- I think the answer here is the union of
> two
> > > lists ;-)
> > >
> > > Thanks,
> > > Roman.
> >
> >
>

Volunteer Needed For Creating Monthly Report

[Mark Bretl]

Hi Everyone,

Its that time again where we need to prepare our status report. As we did
with starting in the Incubator, we will be sending monthly reports for the
first three months (December, January, and February) and then we will
report quarterly.

The board meeting this month is on December 21, so we need to submit our
report by December 14. I have created a page on the Wiki for the report
template at [1] to help the volunteer. My hope would be that we can
finalize a draft by this Friday, December 9th, then submit the report early
next week.

Best Regards,

--Mark


[1]
https://cwiki.apache.org/confluence/display/GEODE/ASF+Board+Report+Template

Re: Review Request 54321: GEODE-2156 Remove incubating references

[Mark Bretl]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54321/#review157819
---



We need to add the new Apache Software Foundation logo to our website header.


geode-spark-connector/doc/2_quick.md (line 12)
<https://reviews.apache.org/r/54321/#comment228422>

While we are at changing links, I think this be changed to the new docs URL.


- Mark Bretl


On Dec. 2, 2016, 12:25 p.m., Anthony Baker wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54321/
> ---
> 
> (Updated Dec. 2, 2016, 12:25 p.m.)
> 
> 
> Review request for geode, Dave Barnes, Dick Cavender, Joey McAllister, Karen 
> Miller, Mark Bretl, and Dan Smith.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> - Remove DISCLAIMER files
> - Remove "(incubating)" from project name references
> - Remove .incubator from website references
> 
> Update mailing list references
> 
> Remove incubating references from the website
> 
> Update repo references
> 
> 
> Diffs
> -
> 
>   .travis.yml e61cde51b8bee2667a6c2b1ab49c69ea20b440fe 
>   BUILDING.md 5e1e7933c59ea66211cf290191ab1f8cef8b2afd 
>   DISCLAIMER PRE-CREATION 
>   NOTICE 4801b2aedf4f254c85cba9f27d2f99d2ca2e046b 
>   README.md 955d45f4f5dd4b95f84dd89d7fcf1108678c5ae8 
>   dev-tools/docker/base/Dockerfile 1cce0ddb0d29c9e188d27481c82123e357c5b685 
>   dev-tools/docker/compile/Dockerfile 
> 6ae343a70eccf7cc4b303228118cee0b8579e79a 
>   dev-tools/docker/docs/Dockerfile 8ce7397efb584ceb3ef032d26f13795e328971fc 
>   docker/Dockerfile a42b47a3328dfff981786ce113f927888e45763a 
>   geode-assembly/src/main/dist/DISCLAIMER PRE-CREATION 
>   geode-assembly/src/main/dist/NOTICE 
> 83d0f3313a01881c9c651077036c17f962cd38b9 
>   geode-book/README.md d69354bce6fa684d635b1c03643638c7dee33251 
>   geode-book/config.yml bbc8ccc2bdffdc5a16134993ebd0683ba71e6d11 
>   geode-book/redirects.rb 81f27c834f78a5b188bb5556bfc93645fbe73262 
>   
> geode-core/src/main/java/org/apache/geode/cache/partition/PartitionListenerAdapter.java
>  b56cdf3547811cbae0b3716b83c4d2fe56b51541 
>   
> geode-core/src/main/java/org/apache/geode/internal/i18n/LocalizedStrings.java 
> 59231232bb85df22e3ca30b1bec338ef0ae033cb 
>   geode-docs/about_geode.html.md.erb 0d7f9b8d9ebe80d8b6a904e584fb76ba9fa6e66b 
>   geode-docs/getting_started/installation/install_standalone.html.md.erb 
> 9a1987e0de5b5f821d0dfc55a113e39fe80f65db 
>   geode-examples/README.md 62666035ab1bde5f9d5548e887e0133f006c2ef9 
>   geode-pulse/src/main/webapp/DataBrowser.html 
> a01df6b280decf8acd96ff6ad2f7a494a53ae682 
>   geode-pulse/src/main/webapp/Login.html 
> f093e38082a1b58a81ba936582599d28e3d2e585 
>   geode-pulse/src/main/webapp/META-INF/NOTICE 
> 706eda265cf0b54c73d01df85c0a79bde9082d8a 
>   geode-pulse/src/main/webapp/MemberDetails.html 
> bc946da8b175d23d9eba529663e1bb86c036079b 
>   geode-pulse/src/main/webapp/QueryStatistics.html 
> 543e003a0b0c447e3fe8d8e6e44d0329a168b029 
>   geode-pulse/src/main/webapp/clusterDetail.html 
> b1fc1e0a24821e40bd08a62ad53b0324102ac03c 
>   geode-pulse/src/main/webapp/regionDetail.html 
> 711ef31bd6f22636420cccd20308b4f7ac7cc769 
>   geode-site/website/README.md 56b6aeb4ab34359ffd771ce21609c3f403397dd5 
>   geode-site/website/content/community/index.html 
> 34e085c77e8803bfe7e6ac621b2b149f8c46b653 
>   geode-site/website/content/docs/index.html 
> 0a475f95b3425624b8478ca4ce55c946140b4cb3 
>   geode-site/website/content/index.html 
> 55311d77aafa7e9065e27130b8662987b90e2563 
>   geode-site/website/content/releases/index.html 
> de0335d6bc0edd299edf44b28cdddf7f33fa15c1 
>   geode-site/website/layouts/footer.html 
> 4877109cbd3599dff81d4d5d69a6ab1c9c73d982 
>   geode-site/website/layouts/header.html 
> 618d33d43506ed6a75326998193af224c2ba6a05 
>   geode-spark-connector/doc/2_quick.md 
> 70e1a170dcb0f0c7699c7431a1061e3ab75c2635 
>   geode-web-api/src/main/webapp/META-INF/NOTICE 
> 21082b6de4fbd7ba4ec4bcb61e9e1bfda5ac162a 
>   geode-web/src/main/webapp/META-INF/NOTICE 
> 8c6e1d7faf3188599305f44c44318f6e6cfd00e6 
>   gradle.properties 164d482161b59534fd91bc14c7773140fbec279e 
>   gradle/publish.gradle af5ee13a2eb6f6532a0e7c73bfb2591dfde60b30 
>   gradle/sonar.gradle 32f18834b054436d29f1b4ca52c145c35b808c60 
> 
> Diff: https://reviews.apache.org/r/54321/diff/
> 
> 
> Testing
> ---
> 
> I'm holding this until the infrastructure changes are ready.
> 
> 
> Thanks,
> 
> Anthony Baker
> 
>

Re: TLP Transition Changes Coming

[Mark Bretl]

John, Redirects are in place for the incubator website once hosting is
moved.

Anthony,

Lots of questions and I think have most of the answers...

- Status of items in [1]:
-- All items are completed except for the remaining INFRA transition items.
-- Our reporting schedule after the initial three months is February, May,
August, November.
-- Once the private mail list has been confirmed as migrated, then all
non-PMC members will be removed from the list if they have not been already
- Geode Committer List [2]: It is correct as it was submitted by the
resolution (as only PMC members were defined), however, yes I do agree that
even though people were not added to the PMC they should have retained
committer status.
- Common Tasks [3]: I already created INFRA-12938 as the Common Task
ticket. I added those items from your list which I did not have to that
ticket.
-- Note: I do not see a Geode Sonar project on https://analysis.apache.org,
so we will have to request one later.

How would people like to handle re-adding the initial committers? Should it
be done on an as-needed basis? However, I hope we would not need to vote
them into committers again for Geode.

Does anyone have any history or experience with this issue?

Best Regards,

--Mark

On Thu, Dec 1, 2016 at 9:33 PM, Anthony Baker <aba...@pivotal.io> wrote:

> Also, I think we need additional subtasks on INFRA-12937 for migrating:
>
> - GitHub mirror
> - release folders
> - Travis-CI
> - JIRA
> - ReviewBoard
> - Sonar
>
> See [1] for examples.  LMK if you want me to create the subtasks.
>
> Anthony
>
> [1] https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20INFRA%20AND%20component%20%3D%20%22TLP%20Admin%22%
> 20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC
>
> > On Dec 1, 2016, at 9:09 PM, Anthony Baker <aba...@pivotal.io> wrote:
> >
> > Thanks Mark!  Can you let us know what has been done so far according to
> [1]?
> >
> > I see that p.a.o [2] has been updated, but I’m curious about the
> committer list.  It looks quite different compared to during incubation.
> Is that correct?
> >
> > Anthony
> >
> > [1] http://incubator.apache.org/guides/graduation.html#new-
> project-hand-over
> > [2] https://people.apache.org/committers-by-project.html#geode
> >
> >> On Dec 1, 2016, at 5:23 PM, Mark Bretl <mbr...@apache.org> wrote:
> >>
> >> Hi Everyone,
> >>
> >> I have received notification that the INFRA team will hopefully start
> our
> >> TLP transition tasks either tomorrow, Friday, or Monday.
> >>
> >> These tasks consist of, but not limited to:
> >> mailing list migration
> >> Apache Git URL migration
> >> GitHub URL migration
> >> JIRA/GitHub Bot
> >>
> >> I am sure things might break along the way, so please be patient with
> the
> >> process, and I will try to keep the community up-to-date as possible.
> >>
> >> --Mark
> >
>
>

Re: Please update your podling status page

[Mark Bretl]

Hi John,

I am working on editing the documents in SVN, however, it seems I do not
have permission to check in. Would you be able to help me with that or can
you point me in the right direction?

Best Regards,

--Mark

On Fri, Nov 25, 2016 at 9:05 AM, John D. Ament 
wrote:

> Dear Geode PMC
>
> Congratulations on becoming a top level project.  Please complete your
> incubator graduation steps.  They can be found here:
> http://incubator.apache.org/guides/graduation.html#unincubate
>
> John
>

[ANNOUNCE] Geode Is Now A Top-Level Apache Project

[Mark Bretl]

Hello Everyone,

It is a great honor to announce the Apache Geode project has graduated to a
Top-Level Project (TLP)

The official announcement is on the Apache Blog at:
https://blogs.apache.org/foundation/entry/the_apache_software_foundation_announces102

I would like to thank everyone for their contributions, especially our
mentors during the incubation process, to getting our community to this
milestone.

As VP of Apache Geode, I am here to serve the community. Please let me know
if you have issues or need anything.

More on the technical details of the transition from Incubator to TLP
project in emails to come.

Looking forward to continuing to grow the community,

Mark Bretl
V.P. Apache Geode