Re: Contributing to Geode

2023-09-25 Thread Mark Bretl
Thanks for your contribution, Oliver!

--Mark

On Thu, Sep 21, 2023 at 10:43 AM Sai Boorlagadda 
wrote:

> Oliver,
>
> Thanks a lot for your contribution and nudging us on the email, we aren't
> been active. I will review it soon and get back to you.
>
> Geode is actively seeking contributors and would love to have you and your
> colleagues start contributing.
>
> If it's possible, could you outline what are the top items that your team
> is interested in?
>
> As of now my main focus is to migrate from concourse pipelines into Github
> actions.
>
> Sai
>
> On Thu, Sep 21, 2023, 8:55 AM VERMEULEN Olivier
>  wrote:
>
> > Hello,
> >
> > I would like to start contributing to Geode.
> > I actually already opened a PR a few days ago:
> > https://github.com/apache/geode/pull/7884
> > Can someone approve the workflows and review it ?
> >
> > More globally my company is interested in contributing security and bug
> > fixes.
> > So some of my fellow developers might also want to join.
> > How should we proceed ?
> >
> > Thanks,
> > Olivier
> > ***
> > This e-mail contains information for the intended recipient only. It may
> > contain proprietary material or confidential information. Its content and
> > any attachment hereto are strictly confidential and must not be disclosed
> > to any unauthorized third party. If you are not the intended recipient,
> > please delete this email and any attachment and notify us immediately.
> > Murex cannot guarantee that it is virus free and accepts no
> responsibility
> > for any loss or damage arising from its use. If you have received this
> > e-mail in error please notify immediately the sender and delete the
> > original email received, any attachments and all copies from your system.
> >
>


Re: Update on CI migration

2023-07-19 Thread Mark Bretl
Thanks for the update Sai. Your work is much appreciated!

--Mark

On Wed, Jul 12, 2023 at 9:02 PM Sai Boorlagadda 
wrote:

> I found out that the infra team is working actively on providing larger
> instances for jobs in Github actions. I will resume my work as soon I see
> they have an option.
>
> Other than that I couldn't keep up contributing to this project in the last
> few weeks.
>
> Sai
>


[DRAFT] Geode Board Report For May 2023

2023-05-08 Thread Mark Bretl
Here is the draft of the board report for the month of May 2023, I will
submit to the board on Wednesday, May 10

## Description:
The mission of Apache Geode is the creation and maintenance of software
related
to a data management platform that provides real-time, consistent access to
data-intensive applications throughout widely distributed cloud
architectures.

## Issues:
For the work of moving CI to GitHub Actions, we are waiting on larger VMs
from
Infra for some of the testing pipelines. No ETA has been provided.

## Membership Data:
Apache Geode was founded 2016-11-15 (6 years ago)
There are currently 118 committers and 31 PMC members in this project.
While the total membership of the PMC is 31, there are less than 10 active
members.
The Committer-to-PMC ratio is roughly 4:1.

Community changes, past quarter:
- No new PMC members. Last addition was Calvin Kirs on 2022-11-14.
- No new committers. Last addition was Calvin Kirs on 2022-11-15.

## Project Activity:
1.15.1 was released on 2022-10-10.
Very little activity on mailing lists and source commits the past few
months. We are still working on migrating the Continuous Integration system
over to GitHub actions.

## Community Health:
The pulse is low. Besides the volunteers who have joined the PMC, we have
not had any growth with contributors to the project. Currently we have two
individuals working small amounts, so need to find ways to get the word out
for more individuals to join the community. This was also an issue when the
majority of contributors were from the same company.


Re: Update on DUnit test pipeline on Github actions

2023-05-05 Thread Mark Bretl
Thanks Sai. Since we have our board report this month, I will note it in
there as a blocker to see if we can gain traction.

--Mark

On Thu, May 4, 2023 at 6:42 PM Sai Boorlagadda 
wrote:

> Mark,
>
> There isn't any specific ticket I created for larger VMs. I heard there is
> an initiative within the infra team to sponsor bigger VMs than the free
> tier we use for Github actions, so we have to wait until that initiative
> picks up steam.
>
> On Thu, 4 May 2023 at 13:58, Mark Bretl  wrote:
>
> > Sai,
> >
> > Do you have an INFRA Jira ticket?
> >
> > --Mark
> >
> > On Tue, May 2, 2023 at 9:53 AM Sai Boorlagadda <
> sai.boorlaga...@gmail.com>
> > wrote:
> >
> > > There is no ETA provided.
> > >
> > > Sai
> > >
> > > On Sat, 29 Apr 2023 at 14:47, Kirk Lund  wrote:
> > >
> > > > Did INFRA give any hint as to when they might provide the bigger VMs?
> > > >
> > > > On Mon, Apr 17, 2023 at 8:24 PM Sai Boorlagadda <
> > > sai.boorlaga...@gmail.com
> > > > >
> > > > wrote:
> > > >
> > > > > I went ahead and merged github workflow jobs that tests
> > > > > WAN, CQ, Assembly and Managment distributed tests.
> > > > >
> > > > > Free workers VMs has 2 cores and tuning any sort of
> > > > > parameters isn't speeding up geode-core DUnits.
> > > > >
> > > > > Talking to infra team found that infra is working on providing
> > > > > self-hosted (sponsored by infra) that are much bigger VMs.
> > > > >
> > > > > So until such VMs are available I am going to find if there are any
> > > > > alternate solution.
> > > > >
> > > > > On Thu, 13 Apr 2023 at 15:08, Kirk Lund  wrote:
> > > > >
> > > > > > I see that there is at least one person concerned about DUnit
> tests
> > > > > > requiring longer timeouts. This is the current situation with an
> > > > unknown
> > > > > > number of the DUnit tests. One possibility is to move the worst
> > > > offenders
> > > > > > to a new src set within geode-core and then give that its own job
> > > with
> > > > a
> > > > > > larger timeout. The longer term solution is to fix or even
> rewrite
> > > some
> > > > > of
> > > > > > those tests. Excluding them is also not a viable option as we
> risk
> > > > > > losing important test coverage that way. I agree that some of
> these
> > > > tests
> > > > > > need a lot more help than tweaking overall job timeout values,
> but
> > > > > without
> > > > > > a lot more time commitment from contributors that might not be an
> > > > > > option for some time.
> > > > > >
> > > > > > -Kirk
> > > > > >
> > > > > > On Thu, Apr 13, 2023 at 3:02 PM Kirk Lund 
> > wrote:
> > > > > >
> > > > > > > Is the coreDistributedTests the only dunit job that currently
> > takes
> > > > too
> > > > > > > long? If it is we may want to split that into more than one
> job.
> > > > > > >
> > > > > > > -Kirk
> > > > > > >
> > > > > > > On Wed, Apr 12, 2023 at 7:58 PM Sai Boorlagadda <
> > > > > > sai.boorlaga...@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > >> All,
> > > > > > >>
> > > > > > >> There is an upper bound for job execution time on free workers
> > > (set
> > > > > to 6
> > > > > > >> hours max[1]), which can be configured beyond 6hrs with a
> > > > self-hosted
> > > > > > >> worker. All of our pipeline jobs are using `--max-workers` to
> > > > > > parallelize
> > > > > > >> gradle tasks but `testMaxParallelForks` is left to default
> which
> > > is
> > > > > > (1/4th
> > > > > > >> of the available CPU cores), so primarily due to running only
> a
> > > > single
> > > > > > >> test
> > > > > > >> in each parallel fork geode-core distribution tests are taking
> > > more
> > > > > > than 6
> > > > > > >> hours. Other than finding a solution for core distributed
> tests,
> > > > most
> > > > > > >> DUnit
> > > > > > >> tests are passed[2] by splitting them into individual jobs
> (WAN,
> > > CQ,
> > > > > > >> Lucene, assembly, management).
> > > > > > >>
> > > > > > >> Will reach out to infra team and trying playing with
> > > `--max-workers`
> > > > > to
> > > > > > >> parallelize more tests than having to run parallel tests with
> > in a
> > > > > fork
> > > > > > >> would be options.
> > > > > > >>
> > > > > > >> I am going to wait for few days to get answers from infra team
> > > > before
> > > > > I
> > > > > > >> can
> > > > > > >> create a PR to add at least the passing DUnits.
> > > > > > >>
> > > > > > >> [1]
> > > > > > >>
> > > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
> https://docs.github.com/en/actions/learn-github-actions/usage-limits-billing-and-administration
> > > > > > >> [2] https://github.com/apache/geode/actions/runs/4639012912
> > > > > > >>
> > > > > > >> Sai
> > > > > > >>
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>


Re: Update on DUnit test pipeline on Github actions

2023-05-04 Thread Mark Bretl
Sai,

Do you have an INFRA Jira ticket?

--Mark

On Tue, May 2, 2023 at 9:53 AM Sai Boorlagadda 
wrote:

> There is no ETA provided.
>
> Sai
>
> On Sat, 29 Apr 2023 at 14:47, Kirk Lund  wrote:
>
> > Did INFRA give any hint as to when they might provide the bigger VMs?
> >
> > On Mon, Apr 17, 2023 at 8:24 PM Sai Boorlagadda <
> sai.boorlaga...@gmail.com
> > >
> > wrote:
> >
> > > I went ahead and merged github workflow jobs that tests
> > > WAN, CQ, Assembly and Managment distributed tests.
> > >
> > > Free workers VMs has 2 cores and tuning any sort of
> > > parameters isn't speeding up geode-core DUnits.
> > >
> > > Talking to infra team found that infra is working on providing
> > > self-hosted (sponsored by infra) that are much bigger VMs.
> > >
> > > So until such VMs are available I am going to find if there are any
> > > alternate solution.
> > >
> > > On Thu, 13 Apr 2023 at 15:08, Kirk Lund  wrote:
> > >
> > > > I see that there is at least one person concerned about DUnit tests
> > > > requiring longer timeouts. This is the current situation with an
> > unknown
> > > > number of the DUnit tests. One possibility is to move the worst
> > offenders
> > > > to a new src set within geode-core and then give that its own job
> with
> > a
> > > > larger timeout. The longer term solution is to fix or even rewrite
> some
> > > of
> > > > those tests. Excluding them is also not a viable option as we risk
> > > > losing important test coverage that way. I agree that some of these
> > tests
> > > > need a lot more help than tweaking overall job timeout values, but
> > > without
> > > > a lot more time commitment from contributors that might not be an
> > > > option for some time.
> > > >
> > > > -Kirk
> > > >
> > > > On Thu, Apr 13, 2023 at 3:02 PM Kirk Lund  wrote:
> > > >
> > > > > Is the coreDistributedTests the only dunit job that currently takes
> > too
> > > > > long? If it is we may want to split that into more than one job.
> > > > >
> > > > > -Kirk
> > > > >
> > > > > On Wed, Apr 12, 2023 at 7:58 PM Sai Boorlagadda <
> > > > sai.boorlaga...@gmail.com>
> > > > > wrote:
> > > > >
> > > > >> All,
> > > > >>
> > > > >> There is an upper bound for job execution time on free workers
> (set
> > > to 6
> > > > >> hours max[1]), which can be configured beyond 6hrs with a
> > self-hosted
> > > > >> worker. All of our pipeline jobs are using `--max-workers` to
> > > > parallelize
> > > > >> gradle tasks but `testMaxParallelForks` is left to default which
> is
> > > > (1/4th
> > > > >> of the available CPU cores), so primarily due to running only a
> > single
> > > > >> test
> > > > >> in each parallel fork geode-core distribution tests are taking
> more
> > > > than 6
> > > > >> hours. Other than finding a solution for core distributed tests,
> > most
> > > > >> DUnit
> > > > >> tests are passed[2] by splitting them into individual jobs (WAN,
> CQ,
> > > > >> Lucene, assembly, management).
> > > > >>
> > > > >> Will reach out to infra team and trying playing with
> `--max-workers`
> > > to
> > > > >> parallelize more tests than having to run parallel tests with in a
> > > fork
> > > > >> would be options.
> > > > >>
> > > > >> I am going to wait for few days to get answers from infra team
> > before
> > > I
> > > > >> can
> > > > >> create a PR to add at least the passing DUnits.
> > > > >>
> > > > >> [1]
> > > > >>
> > > > >>
> > > >
> > >
> >
> https://docs.github.com/en/actions/learn-github-actions/usage-limits-billing-and-administration
> > > > >> [2] https://github.com/apache/geode/actions/runs/4639012912
> > > > >>
> > > > >> Sai
> > > > >>
> > > > >
> > > >
> > >
> >
>


Re: [DRAFT] Geode Board Report For February 2023

2023-02-09 Thread Mark Bretl
Hi Roger,

Here the metrics for the quarterly report, which I will add to the report.


   - dev@geode.apache.org had a 5% decrease in traffic in the past quarter
   (198 emails compared to 208)
   - u...@geode.apache.org had a 36% decrease in traffic in the past
   quarter (11 emails compared to 17)
   - 9 issues opened in JIRA, past quarter (-64% change)
   - 4 issues closed in JIRA, past quarter (-88% change)
   - 104 commits in the past quarter (73% increase)
   - 2 code contributors in the past quarter (-85% change)
   - 13 PRs opened on GitHub, past quarter (-71% change)

The 104 commits are almost all based on the CI pipeline migration effort
from Sai.


--Mark

On Wed, Feb 8, 2023 at 9:32 AM Roger Whitcomb 
wrote:

> Hey Mark,
> Thanks for this. Do we have commit and mailing list statistics (I usually
> at least look at them for the Pivot report)? It would help me to assess the
> differences since the last report.
>
> Thanks,
> ~Roger Whitcomb
>
> > On Feb 7, 2023, at 7:33 AM, Mark Bretl  wrote:
> >
> > Please take a look at the board report draft, feedback is welcome. I will
> > be sending this to the board EOD Wednesday. Thanks!
> >
> > --Mark
> >
> > ## Description:
> > The mission of Apache Geode is the creation and maintenance of software
> > related
> > to a data management platform that provides real-time, consistent access
> to
> > data-intensive applications throughout widely distributed cloud
> > architectures.
> >
> > ## Issues:
> > No immediate issues. The PMC now has enough members to keep the project
> > going and out of the attic.
> >
> > ## Membership Data:
> > Apache Geode was founded 2016-11-15 (6 years ago)
> > There are currently 118 committers and 31 PMC members in this project.
> > The Committer-to-PMC ratio is roughly 4:1.
> >
> > Community changes, past quarter:
> > - Calvin Kirs was added to the PMC on 2022-11-14
> > - Roger Lee Whitcomb was added to the PMC on 2022-11-13
> > - Calvin Kirs was added as committer on 2022-11-15
> > - Roger Lee Whitcomb was added as committer on 2022-11-14
> >
> > ## Project Activity:
> > 1.15.1 was released on 2022-10-10.
> >
> > ## Community Health:
> > With the exit of the two corporate sponsors back in November, the
> community
> > is beginning the rebuilding process. There has been good response from
> the
> > Apache Membership to join the project and help through the transition.
> The
> > community is currently focused on transitioning continuous integration
> > tooling from a previously sponsored Concourse CI to GitHub Actions. This
> > migration will also help remove dependencies on sponsored infrastructure
> in
> > the future as well.
>
>


[DRAFT] Geode Board Report For February 2023

2023-02-07 Thread Mark Bretl
Please take a look at the board report draft, feedback is welcome. I will
be sending this to the board EOD Wednesday. Thanks!

--Mark

## Description:
The mission of Apache Geode is the creation and maintenance of software
related
to a data management platform that provides real-time, consistent access to
data-intensive applications throughout widely distributed cloud
architectures.

## Issues:
No immediate issues. The PMC now has enough members to keep the project
going and out of the attic.

## Membership Data:
Apache Geode was founded 2016-11-15 (6 years ago)
There are currently 118 committers and 31 PMC members in this project.
The Committer-to-PMC ratio is roughly 4:1.

Community changes, past quarter:
- Calvin Kirs was added to the PMC on 2022-11-14
- Roger Lee Whitcomb was added to the PMC on 2022-11-13
- Calvin Kirs was added as committer on 2022-11-15
- Roger Lee Whitcomb was added as committer on 2022-11-14

## Project Activity:
1.15.1 was released on 2022-10-10.

## Community Health:
With the exit of the two corporate sponsors back in November, the community
is beginning the rebuilding process. There has been good response from the
Apache Membership to join the project and help through the transition. The
community is currently focused on transitioning continuous integration
tooling from a previously sponsored Concourse CI to GitHub Actions. This
migration will also help remove dependencies on sponsored infrastructure in
the future as well.


Re: Buildbot build failing for a long time

2023-01-26 Thread Mark Bretl
I am not familiar with it and would be in favor to turn it off/delete it
for now.

--Mark

On Mon, Jan 23, 2023 at 11:57 AM Gavin McDonald 
wrote:

>
>
> On 2023/01/23 14:59:56 Sai Boorlagadda wrote:
> > Thanks Gavin,
> >
> > This nightly build has been failing for quite a while. I will see
> > whats going on.
> >
> > Devs, Do we know about this nightly build? Any info on the setup and how
> it
> > is configured?
>
> Your config file lives at:-
>
> https://github.com/apache/infrastructure-bb2/blob/master/geode.py
>
> any changes to it should go live immediately.
>
> I placed the file there as it was transitioned from the old Buildbot
> server to the new.
>
> You can either try and fix it, or delete the file which will remove it
> from the Buildbot config.
>
> Happy to help in any way I can if you feel you would like it fixed.
>
> Gav...
>
> >
> > Sai
> >
> > On Mon, 23 Jan 2023 at 00:58, Gavin McDonald 
> wrote:
> >
> > > Hi All,
> > >
> > > https://ci2.apache.org/#/builders/72
> > >
> > > Has been failing for a long time. can someone investigate please, if
> > > necessary open an INFRA ticket if something is required our end.
> > >
> > > Thanks
> > >
> > > --
> > >
> > > *Gavin McDonald*
> > > Systems Administrator
> > > ASF Infrastructure Team
> > >
> >
>


Re: Bad Practice: Static constant values set by system properties

2023-01-26 Thread Mark Bretl
Thank you for the effort Kirk and Sai!

--Mark

On Sun, Jan 22, 2023 at 7:16 AM Kirk Lund  wrote:

> Sai and I worked together yesterday and fixed almost all of the failing
> unit tests in the new build we're trying to set up. I think we have one
> failure remaining. Most of the failures we fixed turned out to be caused by
> new code that was committed to Geode in 2022 that causes values in static
> constants that are set by system properties breaking later unit tests that
> will only pass if the constant has the default value.
>
> I want to point out that using system properties to set the values in a
> static constant is definitely an anti-pattern or bad practice that should
> be avoided going forward. It pollutes the JVM for later unit tests and
> cannot be unset because constants are defined as final and static.
>
> In the coming weeks, I plan to update the Apache Geode wiki to spell out
> the anti-pattern bad practices that we need to avoid going forward and this
> will definitely be one of them.
>
> Thanks,
> Kirk
>


Re: priority list

2022-11-14 Thread Mark Bretl
Jenkins CI in 2014 was limited to say the least, now Jenkins has actual
pipelines and stages, with parallel functionality, so it will be much
better this time around if we go that route. I think we could go back to
the basics, do a compile build and then add unit/basic/BVT tests on top
without too much trouble. I would say if we can get CI running for the main
Geode project with a compile in Jenkins, it would be a great first step. I
do have quite a bit of Jenkins experience, so I can definitely help out.

--Mark

On Sat, Nov 12, 2022 at 10:24 PM Kirk Lund  wrote:

> Do we know why Geode has such a large CI resource requirement?
>
> I would guess that it was partially due to trying to run as many tests in
> parallel as possible to shorten the feedback cycle. The recent CI pipelines
> were also built on Pivotal's Concourse which seems to promote a greater
> number of smaller CI jobs (or at least that's my impression).
>
> This code base did successfully use a Jenkins CI prior to 2014 even though
> it took more hours to complete than the more recent Concourse CI. I think
> Mark Bretl was involved in that Jenkins CI so he might remember some
> details or tips or even possible challenges to watch out for.
>
> -Kirk
>
> On Sat, Nov 12, 2022 at 4:42 AM Mario Salazar de Torres
>  wrote:
>
> > Hi,
> > About GitHub actions, there are currently some limitations you I pointed
> > out previously in the devlist.
> > Even tho, I was stuck in the process of migrating geode-native CI to GH
> > actions, mostly since I didn't have the necessary permissions.
> > If you want to have further info about GH actions, you can check Apache
> > BUILDS list.
> >
> > And as for Geode repository, considering the number of resources its CI
> > requires, I'd say GH actions is a no go...
> > Also, I think it was Dan Smith, the one that pointed out that Apache has
> a
> > Jenkins instance available, so every Apache project can use its
> resources.
> > My guess is that Apache Jenkins infra would be a better fit for Geode
> > repository. Still, it remains to be seen, since resource requirements on
> > that repository are really high.
> >
> > Sorry I couldn't be of more help, but at least I hope these pointers are
> > useful.
> >
> > /Mario
> >
> > 
> > From: Niall Pemberton 
> > Sent: Saturday, November 12, 2022 10:46 AM
> > To: dev@geode.apache.org 
> > Subject: Re: priority list
> >
> > On Sat, Nov 12, 2022 at 3:24 AM Sai Boorlagadda <
> sai.boorlaga...@gmail.com
> > >
> > wrote:
> >
> > > Hello Devs,
> > >
> > > I would like to understand some of the top priority items that we
> should
> > > focus and spend our time on while we ramp up with new community
> members.
> > >
> > > Any pointers to the scope of the next release or a list of items we
> > should
> > > do as part of this transition. While going through the mailing list
> what
> > > immediately caught my eye is CI/CD migration to Github actions.
> > >
> >
> > I would say the number one priority is getting a CI instance setup. I
> guess
> > you've seen what Mario said about his efforts on GitHub actions?
> >
> > Niall
> >
> >
> > >
> > > Sai
> > >
> >
>


Re: [VOTE] Move geode to the attic

2022-11-03 Thread Mark Bretl
I am in the same line of thinking as Anthony, there is a ton of work here
to keep this moving and there are not enough people to do it. Between the
role call on the PMC list and lack of significant interest on DEV/USER
lists, I do not see it being a successful community at this point in time.
If at some point in the future, there are enough volunteers to bring it
back, they can go through the incubation process again.

Therefore, I am a +1 vote for the attic. :(

--Mark

On Thu, Nov 3, 2022 at 4:27 AM pieter van zyl  wrote:

> I would vote against moving it to the attic
>
> On Wed, Nov 2, 2022 at 10:56 PM Dan Smith  wrote:
>
>> Any last votes on this? My current count:
>>
>> Binding Votes:
>> 1 vote to move to the attic (Xiaojian)
>>
>> Non-binding votes:
>> 2 votes to move to the attic (Donal and Ernie)
>> 1 vote against and an offer to help maintain the project (Rupert)
>>
>> I'll let the dust settle for another day and then close this vote.
>>
>> -Dan
>> --
>> *From:* Xiaojian Zhou 
>> *Sent:* Sunday, October 30, 2022 10:51 PM
>> *To:* u...@geode.apache.org ; dev@geode.apache.org
>> 
>> *Subject:* Re: [VOTE] Move geode to the attic
>>
>> !! External Email
>>
>> Vote to move to attic.
>>
>> Regards
>> Xiaojian Zhou, PMC of geode
>>
>> From: Dan Smith 
>> Date: Friday, October 28, 2022 at 3:15 PM
>> To: u...@geode.apache.org , dev@geode.apache.org <
>> dev@geode.apache.org>
>> Subject: Re: [VOTE] Move geode to the attic
>> There is still an ongoing discussion on the private@geode list, let's go
>> ahead and extend the VOTE deadline until at least Wednesday, November 2.
>>
>> As Anthony mentioned, only PMC member votes actually count. But all
>> community members should feel free to cast their vote and help us reach a
>> consensus. At the moment, I count zero PMC votes for or against this
>> proposal.
>>
>> Thanks,
>> -Dan
>> 
>> From: rup...@webstersystems.co.uk 
>> Sent: Tuesday, October 25, 2022 12:30 PM
>> To: u...@geode.apache.org ; dev@geode.apache.org <
>> dev@geode.apache.org>
>> Subject: RE: [VOTE] Move geode to the attic
>>
>> ‼ External Email
>>
>> Hello, I vote to keep an open source version.
>> Volunteer for PMC.
>> Please ping me.
>> Cheers.
>>
>> -Original Message-
>> From: Anthony Baker 
>> Sent: 25 October 2022 18:38
>> To: dev@geode.apache.org
>> Cc: u...@geode.apache.org
>> Subject: Re: [VOTE] Move geode to the attic
>>
>> I added the user@ list for visibility.
>>
>> I believe the purpose of taking a VOTE here is to look for community
>> consensus on this idea and perhaps find new people interested in carrying
>> the project forward. The votes of the existing PMC members are the ones
>> that count, just like for a release. Quoting from [1]:
>>
>> "There are two expected mechanisms by which a project may enter the
>> Attic. Either the managing Project Management Committee (PMC) decides it
>> would like to move the project, or The Apache Software Foundation's board
>> dissolves the PMC and chooses to move the project.”
>>
>> And
>>
>> "Projects whose PMC are unable to muster 3 votes for a release, who have
>> no active committers or are unable to fulfill their reporting duties to the
>> board are all good candidates for the Attic.”
>>
>> I’m holding my vote for now. I would vote +1 if I don’t see sufficient
>> ability for the PMC to carry the project.
>>
>>
>> Anthony
>>
>> [1]
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fattic.apache.org%2Fdata=05%7C01%7Cdasmith%40vmware.com%7C37d98042d8ef49984ade08dabb0402fe%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638027923164232642%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=gxqKYTayLzJG0r%2B4BT2ZfHjkgPN917aElv3qbsfqwoU%3Dreserved=0
>> 

Re: [DISCUSS] Move geode to the attic

2022-10-18 Thread Mark Bretl
Unfortunately, I do think the attic is a very real possibility.

@John Blum  Officially, I do not think we (Geode) or ASF
have any type of release support policy (I searched but could not find
anything), it is open-source for better or worse. VMware or any other
company can pick up support if they so choose. Would have it been better
for corporate sponsors to give support to a final release and give a proper
send off? Yes, but we are where we are now. As for artifacts, yes they will
live and remain as-is.

--Mark

On Tue, Oct 18, 2022 at 1:47 PM John Blum  wrote:

> How does the VMware’s non-disclosed date commitment factor into this
> equation?
>
> I mean, clearly the Apache Geode 1.15 release has a lifecycle and support
> timeline, even if the community (and a new PMC) does drive the project any
> further?
>
> What happens when CVEs, or critical bugs (involving data loss) are
> uncovered in 1.15, yet? What even is 1.15’s support timeline and overall
> lifecycle? I would have assumed this would minimally have been 1 year from
> the GA of 1.15.0.
>
> Regarding, “Geode maven artifacts would remain available from Maven
> Central.”
>
> This is absolutely critical and necessary for Apache Geode’s ecosystem of
> projects (for example, Spring for Apache Goede, such as Spring Boot and
> Data for Apache Geode) to continue to build and release against Apache
> Geode versions/bits until the end of the ecosystem project’s (e.g. SDG)
> support timeline.
>
> -John
>
>
> From: Owen Nichols 
> Date: Tuesday, October 18, 2022 at 11:50 AM
> To: dev@geode.apache.org 
> Subject: Re: [DISCUSS] Move geode to the attic
> ⚠ External Email
>
> Once moved to the attic, it sounds like:
>
>   *   The geode github repo would become read-only (but remain
> world-readable in perpetuity).
>   *   Geode would no longer be available for download on the geode
> download site or mirrors (but still available in releases tab in github).
>   *   Geode maven artifacts would remain available from mavencentral.
>   *   Geode homebrew formula would no longer be installable.
>   *   Unsure whether apachegeode/geode docker image would remain available?
>   *   Geode confluence wiki would become read-only.
>   *   It sound like the user mailing list may be able to remain active?
>
> Since no further release are possible without at least 3 active PMC
> members to provide the requisite 3 approving PMC votes, the Attic sounds
> like the best possible way to leave things.
>
> From: Dan Smith 
> Date: Tuesday, October 18, 2022 at 11:12 AM
> To: dev@geode.apache.org 
> Subject: [DISCUSS] Move geode to the attic
> ⚠ External Email
>
> Hi folks,
>
> Unfortunately, it is time to consider moving Geode to the Apache attic.
> After VMware's announcement that it will stop contributing to Geode, we've
> tried in the last couple months to recruit additional contributors to
> continue supporting the project [1]. However, this last week there was a
> PMC role call on the private list and it appears we will only have one
> active PMC member after the VMware folks completely leave.
>
> I think at this point the responsible thing to do is dissolve the Geode
> PMC and move the project to the attic, unless some new contributors
> suddenly show up. We need a minimum of 3 PMC members to keep the project
> viable.
>
> This is not yet a vote. I'll let this discussion run this week and start a
> vote next week. I believe even if we vote to dissolve the project and move
> to the attic, the soonest that process would start would be after the
> November board meeting [2].
>
> Thanks,
> -Dan
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fd88byb42gm5wplzqwkgywg3w9vtj64drdata=05%7C01%7Cjblum%40vmware.com%7C482d2bf794ef46bd167508dab1399813%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638017158176942172%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=eRrcPuf2Ccnkj1SIOWs%2B%2BRwjgiJch0T%2FnbYt2NMt78A%3Dreserved=0
> [2]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fattic.apache.org%2Fprocess.htmldata=05%7C01%7Cjblum%40vmware.com%7C482d2bf794ef46bd167508dab1399813%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638017158176942172%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=PcH23xVCIid04KbsJnbJVKMZ2%2BcZyHWEov7hVsD0OjM%3Dreserved=0
>
>
> 
>
> ⚠ External Email: This email originated from outside of the organization.
> Do not click links or open attachments unless you recognize the sender.
>


Re: [VOTE] Apache Geode 1.15.1.RC1

2022-10-04 Thread Mark Bretl
+1 Built from source and ran tests

--Mark

On Fri, Sep 30, 2022 at 5:26 PM Anthony Baker 
wrote:

> +1
>
> Reviewed source for binaries
> Built from source
> Ran tests with source and binary builds
>
> Anthony
>
>
>
>
> > On Sep 30, 2022, at 3:21 PM, Dan Smith 
> wrote:
> >
> > ⚠ External Email
> >
> > +1 - Ran dev-tools/release-testing/smoketest_rc.sh
> >
> > -Dan
> > 
> > From: Mario Kevo 
> > Sent: Thursday, September 29, 2022 5:36 AM
> > To: dev@geode.apache.org 
> > Subject: [VOTE] Apache Geode 1.15.1.RC1
> >
> > ⚠ External Email
> >
> > Hello Geode Dev Community,
> >
> > This is a release candidate for Apache Geode version 1.15.1.RC1.
> > Thanks to all the community members for their contributions to this
> release!
> >
> > Please do a review and give your feedback, including the checks you
> performed.
> >
> > Voting deadline:
> > 3PM PST Tue, Oct 04 2022.
> >
> > Please note that we are voting upon the source tag:
> > rel/v1.15.1.RC1
> >
> > Release notes:
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FGEODE%2FRelease%2BNotes%23ReleaseNotes-1.15.1data=05%7C01%7Cbakera%40vmware.com%7Cb73823916fde47ef42d008daa3323cfc%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638001733427513622%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=hSCHGk0E40DZ7j78Md6BoBCJNnSmaU9pveaOFQLeLqo%3Dreserved=0
> >
> > Source and binary distributions:
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fgeode%2F1.15.1.RC1%2Fdata=05%7C01%7Cbakera%40vmware.com%7Cb73823916fde47ef42d008daa3323cfc%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638001733427670822%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=mY4lnlJQI%2FSNSb0zsh4ItlsPbeFicrQ6TXFWfbO43kE%3Dreserved=0
> >
> > Maven staging repo:
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachegeode-1139data=05%7C01%7Cbakera%40vmware.com%7Cb73823916fde47ef42d008daa3323cfc%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638001733427670822%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=mSqZGxOo%2FvJrsO9meBpvs%2FdQtjy%2FwwGdC47ps8ti8F8%3Dreserved=0
> >
> > GitHub:
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Ftree%2Frel%2Fv1.15.1.RC1data=05%7C01%7Cbakera%40vmware.com%7Cb73823916fde47ef42d008daa3323cfc%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638001733427670822%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=9Z2n4u4Bl5GHiPT2lk5jJdaTH5f4KFHtXKZIxJkt0oQ%3Dreserved=0
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-examples%2Ftree%2Frel%2Fv1.15.1.RC1data=05%7C01%7Cbakera%40vmware.com%7Cb73823916fde47ef42d008daa3323cfc%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638001733427670822%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=s%2Fe7KKYL2DMPIHlPS4V2HkD4swo19kw5npvzOorPJmo%3Dreserved=0
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-native%2Ftree%2Frel%2Fv1.15.1.RC1data=05%7C01%7Cbakera%40vmware.com%7Cb73823916fde47ef42d008daa3323cfc%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638001733427670822%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=ONBsKzsafV04B02Qe2iNbXIPONTBJx6HLzWlMCIiyxA%3Dreserved=0
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-benchmarks%2Ftree%2Frel%2Fv1.15.1.RC1data=05%7C01%7Cbakera%40vmware.com%7Cb73823916fde47ef42d008daa3323cfc%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638001733427670822%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=%2BVyak4x9mkAJIuDtampfjfhSvIcCmqFUr0e6zH2ox0Y%3Dreserved=0
> >
> > Pipelines:
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fconcourse.apachegeode-ci.info%2Fteams%2Fmain%2Fpipelines%2Fapache-support-1-15-maindata=05%7C01%7Cbakera%40vmware.com%7Cb73823916fde47ef42d008daa3323cfc%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638001733427670822%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=0h2gklOfaZcS4UkEqHlghNLEEqEf%2Blhsul80NCdnK2M%3Dreserved=0
> >
> 

Re: Jira Contributors vs Committers vs "Assign User"

2022-09-22 Thread Mark Bretl
Hey Kirk,

I think this is a great idea. I do not see any reason why Contributors
should not be able to assign issues to themselves, it would definitely help
onboarding new contributors to the project without giving more permissions
as necessary. No need to contact Infra for this change, I have Jira Admin
permissions and can do the task.  I will work on this probably tomorrow.

--Mark

On Wed, Sep 21, 2022 at 2:08 PM Kirk Lund  wrote:

> Contributors have the "Assignable" permission, but are lacking "Assign
> User" which despite the text description means that they cannot assign a
> ticket to themselves. Basically Contributors cannot assign anything to
> anyone.
>
> Ideally, we want to add "Assign User" to Contributors rather than keep
> adding everyone who comes along to the Committers group.
>
> The Apache Geode PMC and admins do not have the necessary permissions to
> edit the Roles. We can only add, assign and remove Users. If we want to
> edit Contributors to add "Assign User" we'll need to have one of us contact
> ASF Infra to request this change to our Project in Jira.
>
> Otherwise we have to assign all newcomers to the Committers group instead
> of Contributors.
>
> Note: I haven't changed any Users or Roles in Jira (I just have time to
> quickly post this message right now).
>
> -Kirk
>


Re: Need access in Jira to be assigned

2022-09-22 Thread Mark Bretl
Hi Tim,

Not sure what happened the first time. Set permissions, would you be able
to try again please?

--Mark

On Wed, Sep 21, 2022 at 1:35 AM Tim Zhang  wrote:

> Hi Mark,
>
> I still cannot assign ticket to myself, could you please help double
> check? Thanks!
> My JIRA username: wabp2005
>
> Br,
> Tim
>
> -Original Message-
> From: Mark Bretl 
> Sent: Tuesday, September 20, 2022 5:43 AM
> To: dev@geode.apache.org
> Subject: Re: Need access in Jira to be assigned
>
> Hi Tim,
>
> I have added you to the Geode project and you should be able to assign
> tickets to yourself now.
>
> Let me know if you have any issues.
>
> Best regards,
>
> Mark
>
> On Wed, Sep 14, 2022 at 8:24 AM Tim Zhang  wrote:
>
> > Hi community,
> >
> > Please also help grant the JIRA access permission to me, I need to
> > assign JIRA ticket to myself, thanks!
> >
> > My JIRA username: wabp2005
> >
> > Brs,
> > Tim
> >
> > -Original Message-
> > From: Wei Yi Luo 
> > Sent: Thursday, September 8, 2022 1:13 PM
> > To: dev@geode.apache.org
> > Subject: Re: Need access in Jira to be assigned
> >
> > Hi Mark,
> >
> > The username: boluo
> >
> > Thanks a lot!
> >
> > Br
> > Bo
> > 
> > From: Mark Bretl 
> > Sent: Thursday, September 8, 2022 4:17 AM
> > To: dev@geode.apache.org 
> > Subject: Re: Need access in Jira to be assigned
> >
> > Hi Wei Yi Luo,
> >
> > What is your Jira username? I should be able to help with access.
> >
> > --Mark
> >
> > On Wed, Sep 7, 2022 at 4:35 AM Wei Yi Luo  wrote:
> >
> > > Hi there,
> > >
> > > Just created a ticket GEODE-10416<
> > > https://issues.apache.org/jira/browse/GEODE-10416>, but still
> > > without access to be the assignee.
> > >
> > > Thanks and looking forward to the helps!
> > >
> > > Br
> > > Bo
> > >
> >
>


Re: Need access in Jira to be assigned

2022-09-19 Thread Mark Bretl
Hi Tim,

I have added you to the Geode project and you should be able to assign
tickets to yourself now.

Let me know if you have any issues.

Best regards,

Mark

On Wed, Sep 14, 2022 at 8:24 AM Tim Zhang  wrote:

> Hi community,
>
> Please also help grant the JIRA access permission to me, I need to assign
> JIRA ticket to myself, thanks!
>
> My JIRA username: wabp2005
>
> Brs,
> Tim
>
> -Original Message-
> From: Wei Yi Luo 
> Sent: Thursday, September 8, 2022 1:13 PM
> To: dev@geode.apache.org
> Subject: Re: Need access in Jira to be assigned
>
> Hi Mark,
>
> The username: boluo
>
> Thanks a lot!
>
> Br
> Bo
> 
> From: Mark Bretl 
> Sent: Thursday, September 8, 2022 4:17 AM
> To: dev@geode.apache.org 
> Subject: Re: Need access in Jira to be assigned
>
> Hi Wei Yi Luo,
>
> What is your Jira username? I should be able to help with access.
>
> --Mark
>
> On Wed, Sep 7, 2022 at 4:35 AM Wei Yi Luo  wrote:
>
> > Hi there,
> >
> > Just created a ticket GEODE-10416<
> > https://issues.apache.org/jira/browse/GEODE-10416>, but still without
> > access to be the assignee.
> >
> > Thanks and looking forward to the helps!
> >
> > Br
> > Bo
> >
>


Re: Need access in Jira to be assigned

2022-09-08 Thread Mark Bretl
Hi,

You should be all set now. Let me know if you have any issues.

--Mark

On Wed, Sep 7, 2022 at 11:13 PM Wei Yi Luo  wrote:

> Hi Mark,
>
> The username: boluo
>
> Thanks a lot!
>
> Br
> Bo
> ____
> From: Mark Bretl 
> Sent: Thursday, September 8, 2022 4:17 AM
> To: dev@geode.apache.org 
> Subject: Re: Need access in Jira to be assigned
>
> Hi Wei Yi Luo,
>
> What is your Jira username? I should be able to help with access.
>
> --Mark
>
> On Wed, Sep 7, 2022 at 4:35 AM Wei Yi Luo  wrote:
>
> > Hi there,
> >
> > Just created a ticket GEODE-10416<
> > https://issues.apache.org/jira/browse/GEODE-10416>, but still without
> > access to be the assignee.
> >
> > Thanks and looking forward to the helps!
> >
> > Br
> > Bo
> >
>


Re: Need access in Jira to be assigned

2022-09-07 Thread Mark Bretl
Hi Wei Yi Luo,

What is your Jira username? I should be able to help with access.

--Mark

On Wed, Sep 7, 2022 at 4:35 AM Wei Yi Luo  wrote:

> Hi there,
>
> Just created a ticket GEODE-10416<
> https://issues.apache.org/jira/browse/GEODE-10416>, but still without
> access to be the assignee.
>
> Thanks and looking forward to the helps!
>
> Br
> Bo
>


Re: [DRAFT] Apache Geode Board report due by Wed Feb 9th

2022-02-04 Thread Mark Bretl
I agree with Dan here that bragging about 'one of the quickest' is not
needed, but noting we are up-to-date with Log4J patches and have
documentation for mitigation might be a better approach.

My $.02

--Mark

On Fri, Feb 4, 2022 at 11:34 AM Dan Smith  wrote:

> Counting the kafka connector I'm not sure bragging about CVE patching
> speed is justified, but otherwise looks good to me!
>
> -Dan
> 
> From: Nabarun Nag 
> Sent: Tuesday, February 1, 2022 2:25 PM
> To: dev@geode.apache.org 
> Subject: Re: [DRAFT] Apache Geode Board report due by Wed Feb 9th
>
> Thank you for the feedback, please find the new draft with the added
> review comments.
>
> ## Project Activity:
> We issued 9 releases this quarter which include an updated Log4j2 version
> to handle the remote code execution CVE. The project had one of the
> quickest turnaround times from the Log4j2 CVE disclosure to the patch
> releases with the fix. Apache Geode Kafka Connector 1.1.0 was also released
> this quarter.
> We have also started the effort to remove the use of deprecated components
> in the project.
>
> > Recent Releases of Apache Geode:
> > - 1.14.3 was released on 2022-01-25
> > - 1.13.7 was released on 2022-01-22
> > - 1.12.8 was released on 2022-01-13
> > - 1.12.7 was released on 2022-12-17
> > - 1.13.6 was released on 2021-12-17
> > - 1.14.2 was released on 2021-12-17
> > - 1.12.6 was released on 2021-12-11
> > - 1.13.5 was released on 2021-12-11
> > - 1.14.1 was released on 2021-12-11
>
>
> 
> From: Owen Nichols 
> Sent: Tuesday, February 1, 2022 12:39 PM
> To: dev@geode.apache.org 
> Subject: Re: [DRAFT] Apache Geode Board report due by Wed Feb 9th
>
> 1.12.8 seems to be missing from the list of releases. Also consider
> bragging about Geode’s turnaround time from CvE disclosure to patch
> release…only one other ASF project got theirs out faster than we did.
>
>
> ---
> Sent from Workspace ONE Boxer<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwhatisworkspaceone.com%2Fboxerdata=04%7C01%7Cdasmith%40vmware.com%7C38f5f23b5d3447df5bee08d9e5d1dbd4%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637793511813886329%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=klI3CJDjpPQoknRVSncdCMBJWbctMIQmOSl5pjyalgc%3Dreserved=0
> >
>
> On January 31, 2022 at 1:57:18 PM PST, Dave Barnes 
> wrote:
> LGTM +1
>
> On Mon, Jan 31, 2022 at 12:50 PM Nabarun Nag  wrote:
>
> > This is a draft of our report to the board. Please let me know if there
> > are details you'd like me to add!
> >
> > --Naba
> >
> > ## Description:
> > The mission of Apache Geode is the creation and maintenance of software
> > related
> > to a data management platform that provides real-time, consistent access
> to
> > data-intensive applications throughout widely distributed cloud
> > architectures.
> >
> > ## Issues:
> > There are no Board-level issues at this time.
> >
> > ## Membership Data:
> > Apache Geode was founded 2016-11-15 (5 years ago)
> > There are currently 115 committers and 54 PMC members in this project.
> > The Committer-to-PMC ratio is roughly 2:1.
> >
> > Community changes, past quarter:
> > - No new PMC members. Last addition was Donal Evans on 2021-03-22.
> > - No new committers. Last addition was Alberto Bustamante on 2021-05-13.
> >
> > ## Project Activity:
> > We issued 8 releases this quarter which include an updated Log4j2 version
> > to handle the remote code execution CVE. Apache Geode Kafka Connector
> 1.1.0
> > was also released this quarter.
> > We have also started the effort to remove the use of deprecated
> components
> > in
> > the project.
> >
> > Recent Releases of Apache Geode:
> > - 1.14.3 was released on 2022-01-25
> > - 1.13.7 was released on 2022-01-22
> > - 1.12.7 was released on 2022-12-17
> > - 1.13.6 was released on 2021-12-17
> > - 1.14.2 was released on 2021-12-17
> > - 1.12.6 was released on 2021-12-11
> > - 1.13.5 was released on 2021-12-11
> > - 1.14.1 was released on 2021-12-11
> >
> > Work on releasing 1.15.0 is progressing as planned.
> >
> > Apache Geode Kafka Connector 1.1.0 was released on 2022-01-18.
> >
> > ## Community Health:
> > - Continuing our monthly video conferences.
> > - Addition of Kafka Connector project to grow the community.
> > - Mailing lists are seeing the usual amount of traffic involving
> > discussions
> > related to improving performance, operation protocols, etc.
> >
> >
> >
>


Re: Requesting eligibility for JIRA ticket assignment

2021-09-23 Thread Mark Bretl
Hi Kaustubh,

I have updated your permissions on the GEODE project, you now should be
able to edit and assign issues.

Please let me know if you have any questions,

Mark

On Thu, Sep 23, 2021 at 10:12 AM Dave Barnes  wrote:

> +1
> Kaustubh's contribution was a good one.
>
> On Thu, Sep 23, 2021 at 8:26 AM Kaustubh Maske Patil 
> wrote:
>
> > Hi,
> > I recently made my first contribution to apache/geode on ticket
> GEODE-9619
> > and would like to request eligibility for assignment to that ticket, and
> > hopefully more in the future :)
> >
> > This is my GitHub profile https://github.com/nikochiko
> >
> > Thanks!
> >
> > Best,
> > Kaustubh Maske Patil
> >
>


Re: New PMC Chair [ was ASF Board Meeting Summary - May 19, 2021]

2021-05-21 Thread Mark Bretl
Congrats Dan!

--Mark

On Thu, May 20, 2021 at 2:00 PM Anthony Baker  wrote:

> Hi everyone, please congratulate Dan Smith as the new PMC Chair [1] of
> Geode!
>
> Karen, thanks for your service!
>
> Anthony
>
> [1] https://www.apache.org/dev/pmc.html#chair <
> https://www.apache.org/dev/pmc.html#chair>
>
>
>
> > Begin forwarded message:
> >
> > From: Sander Striker 
> > Subject: ASF Board Meeting Summary - May 19, 2021
> > Date: May 19, 2021 at 3:25:32 PM PDT
> > To: committ...@apache.org
> > Reply-To: bo...@apache.org
> >
> > The May board meeting took place on the 19th.
> >
> > The following directors were present:
> >
> >  Bertrand Delacretaz, Roy T. Fielding, Sharan Foga, Justin Mclean, Craig
> L Russell, Roman Shaposhnik, Sander Striker, Sheng Wu
> >
> > The following officers were present:
> >
> >  David Nalley, Matt Sicker, Ruth Suehle
> >
> > The following guests were present:
> >
> >  Balázs Donát Bessenyei, Dave Fisher, Daniel Gruno, Sally Khudairi,
> Gavin McDonald, Daniel Ruggeri, Greg Stein
> >
> > The April minutes were approved.
> > Minutes will be posted to
> http://www.apache.org/foundation/records/minutes/
> >
> > The following reports were not received and are expected next month:
> >
> >  Report from the Apache BookKeeper Project [Sijie Guo]
> >  Report from the Apache RocketMQ Project [Xiaorui Wang]
> >
> > All of the received reports to the board were approved.
> >
> > The following resolutions were passed unanimously:
> >
> >  Change the Apache Parquet Project Chair (Xinli Shang, VP)
> >  Change the Apache Geode Project Chair (Dan Smith, VP)
> >  Change the Apache DataFu Project Chair (Eyal Allweil, VP)
> >
> > The next board meeting will be on the 16th of June.
>
>


Re: Please review and contribute: draft of Nov 2020 Apache board report

2020-11-10 Thread Mark Bretl
Looks good. And yes, I would probably make note there is active progress on
a v1.13.1.

Happy Four Year Anniversary Geode Community!

Thanks Karen!

--Mark

On Tue, Nov 10, 2020 at 11:51 AM Anthony Baker  wrote:

> Same, thanks Karen!
>
> On Nov 10, 2020, at 10:19 AM, Dave Barnes  dbar...@apache.org>> wrote:
>
> LGTM
>
>


Re: [PROPOSAL] Backport GEODE-8608 to support 1.13, 1.12 branch

2020-10-14 Thread Mark Bretl
+1

--Mark

On Wed, Oct 14, 2020 at 2:51 PM Darrel Schneider  wrote:

> +1
> 
> From: Anilkumar Gingade 
> Sent: Wednesday, October 14, 2020 1:34 PM
> To: dev@geode.apache.org 
> Subject: Re: [PROPOSAL] Backport GEODE-8608 to support 1.13, 1.12 branch
>
> +1
> After the PR pipeline is completed.
>
> -Anil.
>
> On 10/14/20, 1:32 PM, "Xiaojian Zhou"  wrote:
>
> Hi,
>
> There’s a race that StateFlush could hang when the target member is
> shutdown. GEODE-8608 fixed. This fix is a patch to GEODE-8385.
>
> The fix should be backported to all previous versions with GEODE-8385.
>
> We are still waiting for prechecking to finish.
>
> Regards
> Xiaojian Zhou
>
>


Re: [PROPOSAL] Remove "Fix Version/s" and "Sprint" from Jira "Create Issue" dialogue and include "Affects Version/s"

2020-08-18 Thread Mark Bretl
+1

--Mark

On Tue, Aug 18, 2020 at 9:39 AM Raymond Ingles  wrote:

> +1
>
> On 8/17/20, 3:04 PM, "Donal Evans"  wrote:
>
> Looking at the dialogue that opens when you attempt to create a new
> ticket in the GEODE Jira[1], there are two fields included that aren't
> really necessary and may cause confusion. The "Fix Version/s" field should
> presumably not be filled out until the issue has actually been fixed,
> rather than at the time of ticket creation. The "Sprint" field seems to no
> longer serve any purpose at all that I can discern, having only been filled
> in 13 tickets, the most recent of which was created in December 2018[2].
> With the expansion of the community contributing to the Geode project, it's
> important to provide a straightforward experience for people who are new to
> the project and wish to file tickets, so the presence of these fields may
> cause issues.
>
> I propose that these two fields be removed from the "Create Issue"
> dialogue and that the "Affects Version/s" field be added, since that field
> is far more important at time of ticket creation. There are currently 3851
> bug tickets in the Jira with no "Affects Version/s" value entered at
> all[3], which I suspect is in part due to that field not being an option in
> the "Create Issue" dialogue, meaning you have to remember to go back after
> creating the ticket and enter it. With Geode moving to a model of having
> support branches and patch releases, properly capturing the versions
> affected by a given issue becomes even more important.
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fi.imgur.com%2FoQ8CW87.pngdata=02%7C01%7Cringles%40vmware.com%7C5918d3df46ab428a9eb208d842e06aab%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637332878916804491sdata=c6RjzAIws55sOgzk%2BGJmEGmNzAwBQYjKQrO75eQ7Jho%3Dreserved=0
> [2]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fprojects%2FGEODE%2Fissues%2FGEODE-8433%3Ffilter%3Dallissues%26orderby%3Dcf%255B12310921%255D%2BASC%252C%2Bcreated%2BDESCdata=02%7C01%7Cringles%40vmware.com%7C5918d3df46ab428a9eb208d842e06aab%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637332878916814487sdata=ye5J7qVbdhCGlmpbgOe8D64NWkFviky%2F4e3732NzTFI%3Dreserved=0
> [3]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FGEODE-8433%3Fjql%3Dproject%2520%253D%2520GEODE%2520AND%2520issuetype%2520%253D%2520Bug%2520AND%2520affectedVersion%2520%253D%2520EMPTY%2520ORDER%2520BY%2520created%2520DESC%252C%2520affectedVersion%2520ASC%252C%2520cf%255B12310921%255D%2520ASCdata=02%7C01%7Cringles%40vmware.com%7C5918d3df46ab428a9eb208d842e06aab%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637332878916814487sdata=%2FX3co0tPaXWmyJdqy4B3gf3OVxUqz5udUFDOe2kXBxg%3Dreserved=0
>
>


Re: Proposal to backport GEODE-8395 (gfsh help banner) to support branches

2020-08-03 Thread Mark Bretl
I would vote for 1.13 since that is still up for release, however, I do not
see a need for 1.12 as it is not a critical issue.

--Mark

On Mon, Aug 3, 2020 at 9:00 AM Dave Barnes  wrote:

> Hard to believe this problem was still hanging around. Definitely
> back-port, the sooner, the better.
>
> On Mon, Aug 3, 2020 at 7:56 AM Dave Barnes  wrote:
>
> > +1
> >
> >
> > On Sun, Aug 2, 2020 at 7:07 AM Donal Evans  wrote:
> >
> >> +1
> >>
> >> Nice catch!
> >>
> >> Get Outlook for Android
> >>
> >> 
> >> From: Jinmei Liao 
> >> Sent: Saturday, August 1, 2020 11:09:45 PM
> >> To: dev@geode.apache.org 
> >> Subject: Re: Proposal to backport GEODE-8395 (gfsh help banner) to
> >> support branches
> >>
> >> +1
> >>
> >> On Aug 1, 2020 10:30 PM, Owen Nichols  wrote:
> >> This issue was present since Geode 1.0.  There is zero risk from this
> >> fix, which is already on develop.  It is critical because Geode releases
> >> are a legal Act of the Apache Foundation and should not misrepresent the
> >> identity of the project.
> >>
> >> Here’s the issue:
> >>
> >> $ gfsh
> >> _ __
> >>/ _/ __/ __/ // /
> >>   / /  __/ /___  /_  / _  /
> >> / /__/ / /  _/ / // /
> >> /__/_/  /__/_//_/1.12.0
> >>
> >> Monitor and Manage Apache Geode<-- right product name
> >>
> >> $gfsh --help
> >> Pivotal GemFire(R) v1.12.0 Command Line Shell   <-- WRONG product name
> >>
> >> The “right” instance above was fixed 5 years ago.  GEODE-8395 fixes gfsh
> >> to use the “right” code in both places.  Please vote +1 to backport this
> >> fix to support/1.13 and support/1.12.
> >>
> >>
> >>
>


Re: [PROPOSAL] one-time cleanup of stray and obsolete tags in geode repo

2020-07-30 Thread Mark Bretl
+1

--Mark

On Thu, Jul 30, 2020 at 1:30 PM Robert Houghton 
wrote:

> Highwater isn't used by benchmarks?
>
> On Jul 30, 2020 12:02, Dave Barnes  wrote:
> +1
>
> On Thu, Jul 30, 2020 at 8:45 AM Owen Nichols  wrote:
>
> > Hi Donal, I can confirm that develop/highwater hasn't been updated in a
> > year and is no longer in use by any pipelines (all pipelines use the last
> > release tag as the benchmark baseline now).
> >
> > On 7/30/20, 5:48 AM, "Donal Evans"  wrote:
> >
> > I may be mistaken, but I think the develop/highwater tag was used by
> > the geode-benchmarks project. Can we get confirmation that it's no longer
> > in use?
> >
> > +1 conditional on that
> >
> > Get Outlook for Android<
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fghei36data=02%7C01%7Crhoughton%40vmware.com%7C399c0ee0d7824ffc4e5008d834bb2a3e%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637317325761204283sdata=xmzDLn4YsP4KyZl9vWEbY2pOzWHJDKef7dMtgtEHy3E%3Dreserved=0
> > >
> >
> > 
> > From: Ju@N 
> > Sent: Thursday, July 30, 2020 3:10:44 AM
> > To: dev@geode.apache.org 
> > Subject: Re: [PROPOSAL] one-time cleanup of stray and obsolete tags
> in
> > geode repo
> >
> > +1
> >
> > On Thu 30 Jul 2020 at 08:21, Owen Nichols 
> wrote:
> >
> > > Tags in the rel/ namespace should be created by the Geode release
> > manager
> > > as part of an official Geode release only, yet we seem to have some
> > extra
> > > ones somehow.
> > > Further, I don't see any value in keeping RC tags forever long
> after
> > the
> > > release is final.
> > >
> > > Please vote +1 in favor of trimming the current list of 110 tags
> > down to
> > > 20 to make it nice and easy for newcomers (as well as the rest of
> > us) to
> > > find and checkout a specific version of Geode; otherwise vote -1.
> > If the
> > > majority vote is +1 at 3PM PDT Fri Aug 7, I will proceed to archive
> > and
> > > delete the 90 unnecessary tags as detailed below.
> > >
> > > I propose to KEEP only the following tags, corresponding to
> official
> > Geode
> > > releases:
> > >
> > > rel/v1.12.0
> > > rel/v1.11.0
> > > rel/v1.10.0
> > > rel/v1.9.2
> > > rel/v1.9.1
> > > rel/v1.9.0
> > > rel/v1.8.0
> > > rel/v1.7.0
> > > rel/v1.6.0
> > > rel/v1.5.0
> > > rel/v1.4.0
> > > rel/v1.3.0
> > > rel/v1.2.1
> > > rel/v1.2.0
> > > rel/v1.1.1
> > > rel/v1.1.0
> > > rel/v1.0.0-incubating
> > > rel/v1.0.0-incubating.M3
> > > rel/v1.0.0-incubating.M2
> > > rel/v1.0.0-incubating.M1
> > >
> > > I propose a one-time cleanup to DELETE all other tags,
> specifically:
> > >
> > > develop/highwater
> > > modules-pre-merge
> > > rel/v1.0.0-incubating.M1.RC1
> > > rel/v1.0.0-incubating.M1.RC2
> > > rel/v1.0.0-incubating.M2.RC1
> > > rel/v1.0.0-incubating.M2.RC2
> > > rel/v1.0.0-incubating.M3.RC1
> > > rel/v1.0.0-incubating.M3.RC2
> > > rel/v1.0.0-incubating.M3.RC3
> > > rel/v1.0.0-incubating.M3.RC4
> > > rel/v1.0.0-incubating.M3.RC5
> > > rel/v1.0.0-incubating.M3.RC6
> > > rel/v1.0.0-incubating.M3.RC7
> > > rel/v1.0.0-incubating.RC1
> > > rel/v1.0.0-incubating.RC2
> > > rel/v1.1.0.RC1
> > > rel/v1.1.0.RC2
> > > rel/v1.1.0manualrev-2017-02-16
> > > rel/v1.1.0manualrev-2017-10-19
> > > rel/v1.1.1.RC1
> > > rel/v1.1.1.RC2
> > > rel/v1.10.0.1
> > > rel/v1.10.0.1.RC1
> > > rel/v1.10.0.2
> > > rel/v1.10.0.RC1
> > > rel/v1.10.0.RC2
> > > rel/v1.11.0.1
> > > rel/v1.11.0.2
> > > rel/v1.11.0.23755
> > > rel/v1.11.0.23755_2
> > > rel/v1.11.0.23755_3
> > > rel/v1.11.0.3
> > > rel/v1.11.0.4
> > > rel/v1.11.0.5
> > > rel/v1.11.0.6
> > > rel/v1.11.0.7
> > > rel/v1.11.0.7565
> > > rel/v1.11.0.8
> > > rel/v1.11.0.RC1
> > > rel/v1.11.0.RC2
> > > rel/v1.11.0.RC3
> > > rel/v1.11.0.RC4
> > > rel/v1.12.0.1
> > > rel/v1.12.0.1234
> > > rel/v1.12.0.2
> > > rel/v1.12.0.23755
> > > rel/v1.12.0.3
> > > rel/v1.12.0.4
> > > rel/v1.12.0.5
> > > rel/v1.12.0.6
> > > rel/v1.12.0.RC1
> > > rel/v1.12.0.RC2
> > > rel/v1.12.0.RC3
> > > rel/v1.12.0.RC4
> > > rel/v1.14.0.23755
> > > rel/v1.2.0.RC1
> > > rel/v1.2.0.RC2
> > > rel/v1.2.1.RC1
> > > rel/v1.2.1.RC2
> > > rel/v1.2.1.RC3
> > > rel/v1.2.1.RC4
> > > rel/v1.2.1manualrev-2017-10-19
> > > rel/v1.3.0.RC1
> > > rel/v1.3.0.RC2
> > > rel/v1.3.0.RC3
> > > rel/v1.3.0.RC4
> > > rel/v1.4.0.RC1
> > > rel/v1.4.0.RC2
> > > rel/v1.5.0.RC1
> > > rel/v1.5.0.RC2
> > > rel/v1.6.0.RC1
> > > rel/v1.7.0.RC1
> > > rel/v1.7.0.RC2
> > > rel/v1.8.0.RC1
> > > rel/v1.8.0.RC2
> > > rel/v1.9.0.1
> > > rel/v1.9.0.1.RC1
> > > rel/v1.9.0.2
> > > rel/v1.9.0.RC1

Re: [PROPOSAL] Postpone Geode 1.14

2020-07-29 Thread Mark Bretl
+1

Should we need to drop a line to user@geode or is communicating on this
list enough once decided?

--Mark

On Wed, Jul 29, 2020 at 7:05 AM Joris Melchior  wrote:

> +1
>
> On 2020-07-28, 7:34 PM, "Alexander Murmann"  wrote:
>
> Hi all,
>
> As mentioned on the previous discuss thread, I propose to hold off
> cutting
> 1.14 until we have shipped 1.13.
>
> Once we have shipped 1.13, we should discuss when we want to cut the
> 1.14
> release. The actual ship date for Geode 1.13 is important information
> for
> that conversation. Thus we cannot have that conversation before then.
>
>


Re: Switching default branch in .net core repo

2020-04-24 Thread Mark Bretl
+1

--Mark

On Thu, Apr 23, 2020 at 9:47 AM Dave Barnes  wrote:

> +1
> Dave
>
> On 4/23/20, 8:29 AM, "Karen Miller"  wrote:
>
> +1
> Karen
>
>
> On Thu, Apr 23, 2020 at 8:14 AM Dan Smith  wrote:
>
> > +1
> >
> > -Dan
> >
> > On Thu, Apr 23, 2020, 8:05 AM Anthony Baker 
> wrote:
> >
> > > Please do, this will match our default approach to development
> > > (gitflow-ish).
> > >
> > > +1
> > >
> > > Anthony
> > >
> > >
> > > > On Apr 23, 2020, at 7:35 AM, Blake Bender 
> wrote:
> > > >
> > > > Good morning,
> > > >
> > > > We created a repo yesterday for the .net core client work, and
> the
> > > default
> > > > branch out of the gate is set to master.  I'd like to switch it
> to
> > > develop,
> > > > like the rest of the Geode repos, which apparently requires a
> quick
> > > > heads-up and a couple of +1s to go ahead with.  So... is
> everyone okay
> > > with
> > > > this change?
> > > >
> > > > Thanks,
> > > >
> > > > Blake
> > >
> > >
> >
>
>


Re: [DISCUSS] preparing for Geode 1.13.0 release

2020-04-24 Thread Mark Bretl
Thanks Dave!

--Mark

On Thu, Apr 23, 2020 at 2:55 PM Owen Nichols  wrote:

> Awesome, thanks for stepping up, Dave!
>
> Please familiarize yourself with the instructions at
> https://cwiki.apache.org/confluence/display/GEODE/Releasing+Apache+Geode.
> If you have any questions along the way, there are quite a few past release
> managers on the dev list you can reach out to.
>
> > On Apr 23, 2020, at 2:40 PM, Dave Barnes  wrote:
> >
> > I'm willing.
> >
> > On 4/22/20, 11:43 AM, "Owen Nichols"  wrote:
> >
> >Geode is scheduled to cut support/1.13 on May 4, as per the quarterly
> release schedule approved [1] in 2018 and affirmed in last month’s
> “Shipping patch releases” RFC [2].
> >
> >Please volunteer if you are interested in serving as Release Manager
> for Geode 1.13.0.
> >
> >[1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2F8626f7cc73b49cc90129ec5f6021adab3815469048787032935bfc1e%2540%253Cdev.geode.apache.org%253Edata=02%7C01%7Cdaveba%40vmware.com%7Ccee476d475d84a2a3ceb08d7e6ed0867%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637231778047185914sdata=%2BC7sDyrQloYd%2F4UxmBPEXvDKmeKHXzKV6rxPdghbZIE%3Dreserved=0
> >[2]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FGEODE%2FShipping%2Bpatch%2Breleasesdata=02%7C01%7Cdaveba%40vmware.com%7Ccee476d475d84a2a3ceb08d7e6ed0867%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637231778047190906sdata=CAMNC6g7u9GconPgjQF1Qvk90EIFvPvQ449jHjitRIY%3Dreserved=0
> >
>
>


Re: Proposal to restore Pulse logging in support/1.12

2020-04-24 Thread Mark Bretl
+1

On Fri, Apr 24, 2020 at 3:07 PM Owen Nichols  wrote:

> +1
>
> > On Apr 24, 2020, at 3:06 PM, Jinmei Liao  wrote:
> >
> > +1
> >
> > On Fri, Apr 24, 2020 at 2:53 PM Anthony Baker  wrote:
> >
> >> +1
> >>
> >>> On Apr 24, 2020, at 2:46 PM, Dale Emery  wrote:
> >>>
> >>> During the cleanup of the gradle build and logging, the Pulse webapp
> >> lost its slf4j implementation. As a result, Pulse stopped writing log
> files.
> >>>
> >>> I’ve restored Pulse logging in the develop branch.
> >>>
> >>> I would like to restore it in support/1.12. I’ve created a PR:
> >> https://github.com/apache/geode/pull/4992 <
> >> https://github.com/apache/geode/pull/4992>
> >>>
> >>> Cheers,
> >>> Dale
> >>>
> >>> —
> >>> Dale Emery
> >>> dem...@pivotal.io
> >>> dem...@vmware.com
> >>>
> >>
> >>
> >
> > --
> > Cheers
> >
> > Jinmei
>
>


Re: Reconfiguring our notifications and more

2020-04-21 Thread Mark Bretl
+1

--Mark

On Tue, Apr 21, 2020 at 9:27 AM Jacob Barrett  wrote:

> +1 and fast! Well I guess it doesn’t need to be that fast since GitHub is
> down and not generating any notifications. ;)
>
> > On Apr 21, 2020, at 9:07 AM, Ju@N  wrote:
> >
> > +1
> >
> > On Tue, 21 Apr 2020 at 17:02, Dan Smith  wrote:
> >
> >> +1
> >>
> >> -Dan
> >>
> >> On Tue, Apr 21, 2020 at 9:00 AM Owen Nichols 
> wrote:
> >>
> >>> +1
> >>>
>  On Apr 21, 2020, at 8:54 AM, Anthony Baker  wrote:
> 
>  I’d like a quick round of feedback so we can stop the dev@ spamming
> >> [1].
> 
>  ASF has implemented a cool way to give projects control of lots of
> >>> things [2].  In short, you provide a .asf.yml in each and every GitHub
> >> repo
> >>> to control lots of interesting things.  For us the most immediately
> >>> relevant are:
> 
>  notifications:
>  commits: comm...@geode.apache.org
>  issues:  iss...@geode.apache.org
>  pullrequests:  notificati...@geode.apache.org
>  jira_options: link label comment
> 
>  I’d like to commit this to /develop and cherry-pick over to /master
> >>> ASAP.  Later on we can explore the website and GitHub sections.  Let me
> >>> know what you think.
> 
>  Anthony
> 
> 
>  [1] https://issues.apache.org/jira/browse/INFRA-20156
>  [2]
> >>>
> >>
> https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Notificationsettingsforrepositories
> >>>
> >>>
> >>
> >
> >
> > --
> > Ju@N
>
>


Re: [DISCUSS] - Move gfsh into its own submodule

2019-11-22 Thread Mark Bretl
+1

On Fri, Nov 22, 2019 at 12:55 PM Nabarun Nag  wrote:

> +1
>
> On Fri, Nov 22, 2019 at 12:51 PM Charlie Black  wrote:
>
> > this proposal == awesome sauce
> >
> > +1
> >
> > On Fri, Nov 22, 2019 at 11:24 AM Robert Houghton 
> > wrote:
> >
> > > +1
> > >
> > > Do we want to restart from my lazy POC from a few months ago?
> > >
> > > On Fri, Nov 22, 2019, 08:40 Jens Deppe  wrote:
> > >
> > > > Hello All,
> > > >
> > > > We'd like to propose moving gfsh and all associated commands into its
> > own
> > > > gradle submodule (implicitly thus also producing a separate maven
> > > > artifact). The underlying intent is to decouple geode core from any
> > > Spring
> > > > dependencies.
> > > >
> > > > The proposal is outlined here:
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/GEODE/Move+gfsh+code+to+a+separate+gradle+sub-project
> > > >
> > > > Please provide feedback for this proposal *on this email thread* and
> > not
> > > in
> > > > the comment section of the proposal page.
> > > >
> > > > The deadline for this proposal will be Monday, December 2.
> > > >
> > > > Thanks in advance for feedback / comments.
> > > >
> > > > --Jens & Patrick
> > > >
> > >
> >
> >
> > --
> > Charlie Black | cbl...@pivotal.io
> >
>


[DISCUSS] Support For LTS Version Of Geode

2019-09-30 Thread Mark Bretl
Hi All,

It has come up a few times in recent weeks about the possibility of an LTS
version of Geode. Is this something the community would be interested in?

There are advantages and disadvantages to supporting an LTS. Some
advantages may include:
- Stable release for downstream projects
- Include security and other maintenance related patches

Disadvantages:
- Additional support for multiple distributions/versions
- Release management overhead

Thoughts/Comments/Concerns?

--Mark


Fwd: Migration of Jira to LDAP

2019-09-23 Thread Mark Bretl
Forwarding this from ASF INFRA, in case people have not seen it.

-- Forwarded message -
From: John Andrunas 
Date: Wed, Sep 18, 2019 at 11:44 AM
Subject: Migration of Jira to LDAP
To: , Users , <
operati...@apache.org>


Jira will be upgraded to the latest release on Wednesday 25th
September starting at 2100UTC. Backups will be taken.   We will also
be enabling  LDAP on the service. Should you not have your Jira
username match your asf id then get an infra jira in quick.

Downtime should be around 2 hours.

Thanks

John
ASF Infra


Re: [DISCUSS] Criteria for PMC, committers

2019-06-04 Thread Mark Bretl
I think in any point of view we are looking at Committer or PMC membership,
it does come down to merit. Does the person have the merit, which can also
be trust, to be a Committer and/or PMC member?

The difference between Committer and PMC member is not simply being
'gatekeepers' of the codebase, PMC members provide oversight to the entire
project [1], which I cannot put the same responsibility on a Committer. I
don't think there has to a promotion path in terms of Committer -> PMC,
however, I do believe there is a distinction between the two, especially
since it is the Apache Board which ultimately makes the decision for PMC
membership. A candidate be nominated for both at one time, but then it
would be an all or nothing vote.

--Mark

[1]: https://www.apache.org/foundation/governance/pmcs.html

On Fri, May 31, 2019 at 3:17 PM Jacob Barrett  wrote:

> I think it's a lot of what is under the contributing section, but I think
> it needs to be cleaned up. A lot of the what should be done is lost under
> the screen shots of things. I nice clear bullet point, with maybe links to
> the wiki for details, would be nice. If we collected all of this in the
> CONTRIBUTING.md its right there in your source and baked into GitHub, which
> is the primary place developers go, not the wiki. Then our PR template
> could just say something like “[ ] complies with contributing guidelines”.
> Eh??
>
> -Jake
>
>
> > On May 31, 2019, at 3:12 PM, Anthony Baker  wrote:
> >
> > Are you thinking in terms of something like this?
> > https://cwiki.apache.org/confluence/display/GEODE/Code+of+Conduct <
> https://cwiki.apache.org/confluence/display/GEODE/Code+of+Conduct>
> >
> > Or something more specific to coding tasks?
> >
> >
> > Thanks,
> > Anthony
> >
> >
> >> On May 31, 2019, at 2:41 AM, Owen Nichols  wrote:
> >>
> >> I think it might be helpful to first define clearly what code of
> conduct a committer is expected to follow.  That exercise would help frame
> exactly what we are trusting new (and existing) committers to adhere to.
> >
>
>


Re: Static Analysis Tools such as SonarQube or others?

2019-06-04 Thread Mark Bretl
I have used SonarQube for many years, including integrating for the Geode
codebase in the past and using it now my current day job, and like it a
lot. The ASF hosts a server at https://builds.apache.org/analysis/,
however, the version is quite old and does not have features such as
Quality Gating or PR decoration. There is now a cloud version at
https://sonarcloud.io, which is free for open source projects.

As Dan said, in order to make them productive, they need to be integrated
into the CI pipeline or the issues will end up as noise.

--Mark

On Tue, Jun 4, 2019 at 11:30 AM Dan Smith  wrote:

> We're currently running PMD as part of the gradle build. PMD is just
> running a couple of rules specifically to look for mutable statics. We've
> also enabled integration with lgtm to get a report -
> https://lgtm.com/projects/g/apache/geode/.
> 
>
> I think added more static analysis is a good idea. I'm not that particular
> about which tool(s) we are using - although maybe we should focus on open
> source tools? I do think that in order to be valuable, the static analysis
> rules need to fail the build like we're doing with spotless and PMD. So I
> think an approach of cleaning up and enforcing one rule at a time is better
> than just generating a report with a bunch of rule violations.
>
> -Dan
>
>
> On Tue, Jun 4, 2019 at 6:56 AM Peter Tran  wrote:
>
> > Hi all,
> >
> > Has anyone had experience using static analysis tools such as SonarQube?
> > Were there helpful? And favourites that worked well?
> >
> > Thanks
> >
>


Re: Need edit access to cwiki

2019-04-02 Thread Mark Bretl
Hi Jinmei,

I have viewed your permissions and they look correct. When I click on edit
page, it was successful in loading the editor.

Did you login with your Apache LDAP account? It looks like INFRA has
updated that fairly recently.

--Mark

On Tue, Apr 2, 2019 at 2:58 PM Jinmei Liao  wrote:

> Username is jinmeiliao. I used to have edit access, but now Confluence
> throws "The editor didn't load this time" error when trying to edit a page
>
> --
> Cheers
>
> Jinmei
>


New Geode PMC Chair: Karen Miller

2018-11-26 Thread Mark Bretl
Hello Geode Community,

After two years, the Project Management Committee (PMC) agreed to
transition the role of PMC chair from me to another PMC member. I would
like to announce, at last week's Apache Board Meeting, the Board approved
the Geode PMC's recommendation of Karen Miller to the office of V.P.,
Apache Geode.

Please welcome our new PMC Chair, Karen Miller!

Best regards,

--Mark


Re: November 2018 Board Report Final Draft

2018-11-15 Thread Mark Bretl
Board report has been posted, thanks Robert!

--Mark

On Wed, Nov 14, 2018 at 10:00 AM Robert Houghton 
wrote:

> Here is the final form our report for the quarter. If it passes muster, can
> someone commit it to the Apache repository for me?
>
> ## 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:
> >
> > - We released v1.7.0, containing 859 commits resolving 196 bugs, 98
> >> improvements
> >
> >  and features, and a total of 357 JIRA tickets
> >
> > - We've made a number of build improvements, including upgrading to
> Gradle
> >> v4.10.1
> >
> > - We've begun testing with Java 11 and have added automated Windows
> >> testing to our CI jobs.
> >
> > - We have reviewed and acted on a number of code issues reported by
> >> lgtm.com .
> >
> > - We discussed use of Lombok and decided that adoption would prove to be
> a
> >> barrier to users and contributors.
> >
> > - We added a notifications@ mailing list to track GitHub PR activity.
> >
> > - We agreed to adopt a quarterly release schedule to improve
> >> predictability of releases.
> >
> > - We reorganized the top-level wiki for better navigation and
> >> discoverability.  We also added a page to track conference
> >
> >  presentations, blog postings, and other media.
> >
> > - The Geode Summit at SpringOnePlatform 2018 was very well-attended with
> >> over 400 people filling the conference room.
> >
> >  Both users and committers alike presented 15 talks during the
> >> conference.  The sessions were recorded and available on
> >
> >  youtube.
> >
> >
> >>
> >> ## Health report:
> >
> > - Overall project momentum is picking back up. We are seeing good results
> >> from the efforts
> >
> >  to improve test reliability
> >
> >
> >> ## PMC changes:
> >
> >
> >> - Currently 46 PMC members.
> >
> > - No new PMC members added in the last 3 months
> >
> > - Last PMC addition was Dick Cavender on Tue Feb 20 2018
> >
> >
> >
> > ## Committer base changes:
> >
> >
> >> - Currently 98 committers.
> >
> > - New commmitters:
> >
> >- Addison Huddy was added as a committer on Sat Sep 01 2018
> >
> >- Alexander Murmann was added as a committer on Sat Sep 08 2018
> >
> >- Blake Bender was added as a committer on Sat Sep 01 2018
> >
> >- Helena Bales was added as a committer on Sat Sep 01 2018
> >
> >- Ivan Godwin was added as a committer on Sat Sep 01 2018
> >
> >- Juan Ramos was added as a committer on Sat Sep 08 2018
> >
> >- Ryan McMahon was added as a committer on Sat Sep 01 2018
> >
> >- Michael Martell was added as a committer on Sat Sep 08 2018
> >
> >- Michael Oleske was added as a committer on Sat Sep 08 2018
> >
> >- Robert Houghton was added as a committer on Mon Oct 01 2018
> >
> >- Sean Goller was added as a committer on Sat Sep 01 2018
> >
> >
> >> ## Releases:
> >
> >
> >> - 1.7.0 was released on Thu Oct 04 2018
> >
> > - We have begun work on the 1.8.0 release.  We expect the release to
> >> include geode-native (a C++/C# client for Geode)
> >
> >  for the first time.
> >
> > - We're continuing to rotate release manager duties among committers to
> >> ensure the release process is well documented
> >
> >  and repeatable.
> >
> >
> >> ## Mailing list activity:
> >
> >
> >> - Mailing lists have remained active and have been seen a marked
> increase
> >> in use
> >
> >  for both development and issues
> >
> > - The increase in the user@ mailing list is very encouraging and seems
> to
> >> correlate with the Geode Summit.
> >
> >
> >> - dev@geode.apache.org:
> >
> >- 190 subscribers (up 8 in the last 3 months):
> >
> >- 889 emails sent to list (624 in previous quarter)
> >
> >
> >
> > - iss...@geode.apache.org:
> >
> >- 55 subscribers (up 1 in the last 3 months):
> >
> >- 4283 emails sent to list (2707 in previous quarter)
> >
> >
> >
> > - notificati...@geode.apache.org:
> >
> >- 7 subscribers (up 7 in the last 3 months):
> >
> >- 1998 emails sent to list (0 in previous quarter)
> >
> >
> >
> > - u...@geode.apache.org:
> >
> >- 249 subscribers (up 7 in the last 3 months):
> >
> >- 201 emails sent to list (138 in previous quarter)
> >
> >
> >
> >
> >
> > ## JIRA activity:
> >
> >
> >> - 456 JIRA tickets created in the last 3 months
> >
> > - 485 JIRA tickets closed/resolved in the last 3 months
> >
> >
> >>
>


[CANCEL][VOTE] Apache Geode 1.7.0 RC1

2018-09-28 Thread Mark Bretl
Officially canceling vote for mail archive.

--Mark

On Wed, Sep 26, 2018 at 8:54 PM Nabarun Nag  wrote:

> Hi Jason,
>
> Thanks for sharing your finding with the community and doing the needful to
> resolve the issue. I will be cherry-picking the resolution to the release
> branch and start with the process of create a new release candidate.
>
> Hello Geode community,
>
> We are terminating all tasks related to RC1 for Apache Geode 1.7.0. Please
> stay tuned for the next release candidate.
>
> Regards
> Nabarun Nag
>
>
> On Wed, Sep 26, 2018 at 5:41 PM Jason Huynh  wrote:
>
> > Hi Nabarun,
> >
> >
> >
> > Thanks for delaying the vote, after investigating, it looks like we may
> > have increased our chances of WAN inconsistency in a specific scenario.
> > After trying this same app on previous releases, I was able to pinpoint
> > which checkin started to amplify the problem and increase the number of
> > scenarios this inconsistency can occur.
> >
> >
> > The ticket in question is GEODE-3967, the problem with this checkin is
> that
> > we try to enqueue wan events in a catch block for
> > ConcurrentCacheModificationExceptions.  We end up enqueueing these “old”
> > events (which can now be considered out of order) and then get
> transmitted
> > to the other WAN site and leaves the sites inconsistent with each other.
> >
> >
> > I’ve reverted the commit for GEODE-3967 on develop if you want to pull
> this
> > into the release.
> >
> >
> >
> > Thanks,
> >
> > -Jason
> >
> > On Mon, Sep 24, 2018 at 12:23 PM Nabarun Nag  wrote:
> >
> > > Hi Jason,
> > >
> > > We can wait until the investigation is completed, as this can be a
> > > potential -1 to the RC.
> > >
> > > Regards
> > > Nabarun Nag
> > >
> > > On Mon, Sep 24, 2018 at 12:20 PM Jason Huynh 
> wrote:
> > >
> > > > I'm currently looking into an issue in WAN when running this rc.  Not
> > > sure
> > > > if it's a showstopper and I can't actually describe what the problem
> > is,
> > > > but a sample application I have is not behaving the same as before,
> > there
> > > > may be a data inconsistency... if it's not too late, would you be
> able
> > to
> > > > extend the vote?
> > > >
> > > >
> > > >
> > > >
> > > > On Wed, Sep 19, 2018 at 11:47 AM Dave Barnes 
> > wrote:
> > > >
> > > > > +0
> > > > > Recasting my vote, just for full disclosure. I found a (very minor)
> > > > problem
> > > > > in the source release doc files: If a user builds their own docs
> from
> > > > > sources, they'll say version 1.8.
> > > > >
> > > > >- NOT (even close to) a showstopper
> > > > >- This will NOT affect the User Guide we'll push to the website
> > with
> > > > the
> > > > >release, which will be correctly labeled 1.7
> > > > >- Javadocs are NOT affected - they are correctly versioned as
> 1.7
> > > > >
> > > > >
> > > > > On Wed, Sep 19, 2018 at 11:09 AM, Sai Boorlagadda <
> > > > > sai.boorlaga...@gmail.com
> > > > > > wrote:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > * verified commit hash
> > > > > > * checked concourse pipeline is green
> > > > > > * ran examples with RC1
> > > > > > * built from source
> > > > > >
> > > > > > Sai
> > > > > >
> > > > > > On Wed, Sep 19, 2018 at 8:46 AM Nabarun Nag 
> > wrote:
> > > > > >
> > > > > > > REMINDER: VOTE deadline is today (EOD 19th September 2018 PDT)
> > > > > > >
> > > > > > > Regards
> > > > > > > Nabarun Nag
> > > > > > >
> > > > > > > On Wed, Sep 19, 2018 at 7:13 AM Anthony Baker <
> aba...@pivotal.io
> > >
> > > > > wrote:
> > > > > > >
> > > > > > > > I think we can get rid of the **/out/** exclusion in the
> build
> > > > > script,
> > > > > > > > let’s do that for the next release.
> > > > > > > >
> > > > > > > > Anthony
> > > > > > > >
> > > > > > > >
> > > > > > > > > On Sep 18, 2018, at 3:52 PM, Dan Smith 
> > > > wrote:
> > > > > > > > >
> > > > > > > > > +0
> > > > > > > > >
> > > > > > > > > I noticed that someone added some files called "out" to the
> > > repo
> > > > > that
> > > > > > > > > aren't included in the source distribution:
> > > > > > > > >
> > > > > > > > > ./ci/resource-types/gce-instances-resource/out
> > > > > > > > > ./ci/resource-types/concourse-metadata-resource/files/out
> > > > > > > > >
> > > > > > > > > These aren't included in the source distribution because we
> > are
> > > > > > > > explicitly
> > > > > > > > > excluding anything called "out." Presumably we thought
> > anything
> > > > > > called
> > > > > > > > out
> > > > > > > > > is an output directory ("out" is also in .gitignore). So
> the
> > ci
> > > > > > > directory
> > > > > > > > > in the source distribution is incomplete. But maybe that
> > > doesn't
> > > > > > matter
> > > > > > > > > because it is just CI configuration?
> > > > > > > > >
> > > > > > > > > Everything else looks good.
> > > > > > > > >
> > > > > > > > > -Dan
> > > > > > > > >
> > > > > > > > > On Mon, Sep 17, 2018 at 5:06 PM, Nabarun Nag <
> > n...@apache.org>
> > > > > > wrote:
> > > > > > > > >
> > > > > > > > >> *DEADLINE 

Re: August 2018 Board Report Volunteer

2018-08-10 Thread Mark Bretl
Report has been posted.

Thanks all!

--Mark

On Thu, Aug 9, 2018 at 4:40 PM Anthony Baker  wrote:

> @Mark, looks like we got enough eyeballs on this.  Can you submit?
>
> Thanks,
> Anthony
>
>
> > On Aug 9, 2018, at 4:03 PM, Dave Barnes  wrote:
> >
> > +1 LGTM
> >
> > On Thu, Aug 9, 2018 at 3:57 PM, Kirk Lund  wrote:
> >
> >> +1 looks good!
> >>
> >> On Thu, Aug 9, 2018 at 3:46 PM, Anthony Baker 
> wrote:
> >>
> >>> This is a bit late so please review asap.  Thanks!
> >>>
> >>> ## 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:
> >>> - We held up releasing v1.7.0 in favor of fixing more bugs and making
> >>> our tests more reliable.  We closed out 40% of the open test bugs (out
> >>> of 220) and removed the ‘FlakyTest’ category from 136 tests.
> >>> - We integrated our pre-commit tests directly into GitHub PR checks.
> >>> This makes it super easy for committers and contributors to run and
> >>> review test results.
> >>> - We’ve optimized test runtimes for pull requests to get results in
> >>> less than an hour.  If someone were to run the same tests on a laptop
> >>> it would take over 18h.
> >>> - We upgraded the project build tools to Gradle 4.9 in preparation for
> >>> supporting Java 11.
> >>> - We merged a contribution to add thread monitoring and take action if
> >>> a thread appears to hang.
> >>> - We discussed improvements to handling of the default SSL context.
> >>> - We discussed improvements to allow customizable trust boundaries for
> >>> securing OQL method invocations.
> >>> - The Geode PMC discussed and approved a Geode session track at the
> >>> SpringOnePlatform conference (see
> >>> https://springoneplatform.io/2018/geode).
> >>> - Community member Addison Huddy posted a series of seven (and
> >>> counting) youtube videos on “Geode by Example”.
> >>>
> >>> ## Health report:
> >>> - We’ve had a number of excellent contributions from new community
> >>> members in the last three months.  Although the PMC did not add any
> >>> committers this quarter we should definitely review and discuss adding
> >>> new committers soon.
> >>> - By increasing test speed, reliability, and ease of access we have
> >>> lowered the barriers for new contributions and community
> >>> participation.
> >>>
> >>> ## PMC changes:
> >>>
> >>> - Currently 46 PMC members.
> >>> - No new PMC members added in the last 3 months
> >>> - Last PMC addition was Dick Cavender on Tue Feb 20 2018
> >>>
> >>> ## Committer base changes:
> >>>
> >>> - Currently 87 committers.
> >>> - No new committers added in the last 3 months
> >>> - Last committer addition was Michael W. Dodge at Wed Jan 24 2018
> >>>
> >>> ## Releases:
> >>>
> >>> - Last release was 1.6.0 on Fri May 04 2018
> >>>
> >>> ## Mailing list activity:
> >>>
> >>> Mailing lists have remained active and have maintained consistent usage
> >>> levels.
> >>>
> >>> - dev@geode.apache.org:
> >>>   - 183 subscribers (up 0 in the last 3 months):
> >>>   - 683 emails sent to list (793 in previous quarter)
> >>>
> >>> - iss...@geode.apache.org:
> >>>   - 54 subscribers (up 0 in the last 3 months):
> >>>   - 2991 emails sent to list (6890 in previous quarter)
> >>>
> >>> - u...@geode.apache.org:
> >>>   - 242 subscribers (down -9 in the last 3 months):
> >>>   - 141 emails sent to list (148 in previous quarter)
> >>>
> >>> ## JIRA activity:
> >>>
> >>> - 349 JIRA tickets created in the last 3 months
> >>> - 330 JIRA tickets closed/resolved in the last 3 months
> >>>
> >>> Anthony
> >>>
> >>> On Thu, Jul 26, 2018 at 1:52 PM Dave Barnes 
> wrote:
> >>>>
> >>>> ...and just betw

August 2018 Board Report Volunteer

2018-07-26 Thread Mark Bretl
Hi Everyone,

Its that time again to submit a report for the August Board Meeting. We
need to submit a report by August 8th. Would anyone like to volunteer to
write a draft of the report?

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

Previous Reports: https://whimsy.apache.org/board/minutes/Geode.html

Best regards,

--Mark


Re: wiki userid locked

2018-05-22 Thread Mark Bretl
Hi Barbara,

Unfortunately, we can not help you with login issues. You will need to
contact Apache INFRA team by emailing us...@infra.apache.org to unlock your
account.

--Mark

On Tue, May 22, 2018 at 8:51 AM, Barbara Pruijn  wrote:

> Hi,
>
> It looks like my geode wiki userid is locked.
> My userid is bpruijn.
> I have reset my password several times, but I cannot log in with any new
> password created. I think my account is in a locked state.
>
> Can someone please unlock it?
>
> Thanks,
> Barbara
>
>


Re: geode.apache.org and GDPR

2018-05-22 Thread Mark Bretl
Thanks Anthony for bringing this to attention as the GDPR deadline is
looming. +1 for removing.

--Mark

On Mon, May 21, 2018 at 3:12 PM, Joey McAllister 
wrote:

> +1 to removing this. Thanks, Anthony!
>
> On Mon, May 21, 2018 at 3:03 PM Michael Stolz  wrote:
>
> > +1 to remove it
> >
> > --
> > Mike Stolz
> > Principal Engineer, GemFire Product Lead
> > Mobile: +1-631-835-4771 <(631)%20835-4771>
> > Download the GemFire book here.
> > <
> > https://content.pivotal.io/ebooks/scaling-data-services-
> with-pivotal-gemfire
> > >
> >
> > On Mon, May 21, 2018 at 11:31 AM, Greg Chase  wrote:
> >
> > > Part of GDPR: Don’t collect or store data you don’t intend to use.
> > >
> > > +1 to remove it.
> > >
> > > This email encrypted by tiny buttons & fat thumbs, beta voice
> > recognition,
> > > and autocorrect on my iPhone.
> > >
> > > > On May 21, 2018, at 8:29 AM, Anthony Baker 
> wrote:
> > > >
> > > > The geode website uses Google Analytics [1].  IANAL but there are
> some
> > > constraints that will apply when GPDR takes effect [2].  Specifically,
> > > users can opt-out of data collection.  Given how little use we’ve made
> of
> > > this data, I think it would be simpler to just remove the GA tracker
> from
> > > our website.
> > > >
> > > > Thoughts?
> > > >
> > > >
> > > > Anthony
> > > >
> > > > [1] https://github.com/apache/geode-site/blob/master/
> > > website/layouts/header.html#L40  > > geode-site/blob/master/website/layouts/header.html#L40>
> > > > [2] https://issues.apache.org/jira/browse/MSKINS-143 <
> > > https://issues.apache.org/jira/browse/MSKINS-143>
> > > >
> > >
> >
>


Re: Wiki permissions

2018-05-16 Thread Mark Bretl
Hi Sai,

I have added 'sai_boorlagadda' to the Geode space, however, I do see you
have another user named 'sboorlagadda'. Is this an active username or does
it need to be removed?

--Mark

On Wed, May 16, 2018 at 12:34 PM, Sai Boorlagadda <
sai_boorlaga...@apache.org> wrote:

> Hello Devs,
>
> Could someone grant me permissions to edit Apache Wiki?
>
> My Id: sai_boorlagadda
>
> Sai
>


Re: Quarterly report - DRAFT for your review

2018-05-08 Thread Mark Bretl
Looks good! Thanks Dave!

--Mark

On Tue, May 8, 2018 at 10:13 AM, Dave Barnes  wrote:

> Here's the near-final draft of our quarterly report. Responses received by
> 5pm PDT today (May 8) will be incorporated.
> Thanks,
> Dave Barnes
>
> ## 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:
>  - Two full product releases, Apache Geode versions 1.5 and 1.6
>  - Community member Addison Huddy presented "What the Heck is an In-Memory
> Data Grid?" at DataEngConf SF '18
>  - Launched an investigation into adding PR status updates based on CI jobs
> (see INFRA-16409).
>  - In connection with SpringOne Platform, Pivotal, Inc., proposed to host a
> Geode community event, prompting a discussion among the PMC regarding logo
> use
>
> ## Health report:
>  - Mailing lists remain active and productive.
>  - JIRA tickets show that issues continue to be identified and resolved.
>  - We’re continuing to work on attracting new contributors and making it
> easier to participate in the community.
>
> ## PMC changes:
>
>  - Currently 46 PMC members.
>  - New PMC members:
> - Dick Cavender was added to the PMC on Tue Feb 20 2018
> - Lynn Hughes-Godfrey was added to the PMC on Mon Feb 19 2018
> - Lynn Gallinat was added to the PMC on Mon Feb 19 2018
>
> ## Committer base changes:
>
>  - Currently 87 committers.
>  - No new committers added in the last 3 months
>  - Last committer addition was Michael W. Dodge at Wed Jan 24 2018
>
> ## Releases:
>
>  - Apache Geode 1.5.0 was released on Fri Apr 06 2018. Highlights include:
>
> - Support for arithmetic operators in the WHERE clause of OQL queries
> - Expanded gfsh (cli) functionality in the form of new commands and
> enhancements to existing commands
> - REST interface improvements
> - Improved deadlock prevention
> - Improved client capabilities, including enhancements to load
> balancing and subscription behavior
> - 18 new features
> - 270 enhancements and improvements
> - 226 bug fixes
>
> A full list of issues that were resolved in Apache Geode 1.5 can be found
> at
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12318420=12342395
>
>  - Apache Geode 1.6.0 was released on Fri May 04 2018 under the watchful
> eye of Mike Stolz, in his debut as an Apache Geode Release Manager.
> Highlights include:
>
> - Serialization refinements
> - JDBC connector improvements
> - gfsh (cli) commands to configure and manage JNDI bindings
> - Cluster configuration enhancements
> - 17 new features
> - 139 enhancements and improvements
> - 148 bug fixes
>
> A full list of issues that were resolved in Apache Geode 1.6 can be found
> at
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12318420=12342867
>
>
> ## Mailing list activity:
>
> Mailing lists have remained active and have maintained consistent usage
> levels.
>
>  - dev@geode.apache.org:
> - 182 subscribers (up 6 in the last 3 months):
> - 818 emails sent to list (706 in previous quarter)
>
>  - iss...@geode.apache.org:
> - 54 subscribers (up 0 in the last 3 months):
> - 7028 emails sent to list (4960 in previous quarter)
>
>  - u...@geode.apache.org:
> - 251 subscribers (up 12 in the last 3 months):
> - 151 emails sent to list (228 in previous quarter)
>
>
> ## JIRA activity:
>
>  - 612 JIRA tickets created in the last 3 months
>  - 701 JIRA tickets closed/resolved in the last 3 months
>


Geode Website Check For Apache Events Does Not Have Expected Link

2018-04-12 Thread Mark Bretl
Hi All,

Apache has a tool for checking all TLP websites and our site is all 'green'
except for the Events check, https://whimsy.apache.org/site/project/geode.

At the bottom/footer of our main page, there is an Apache -> Events link
which has a HREF value of http://www.apache.org/events/.  The website
Events check is searching for ^https?://.*apache.org/events/current-event.

The expected link is on the Community page, but I think the crawler is
finding the link on the main page and stopping. Do we want to update the
footer or leave it as is?

--Mark


Re: [DISCUSS] New List for Commit and CI Emails

2018-03-22 Thread Mark Bretl
+0

I think sending notifications another list are likely to be ignored, or
at-least hard to make sure people sign up for the new list. I would be for
anything to 'optimize' the amount of emails from the automated systems.

--Mark

On Thu, Mar 22, 2018 at 12:55 PM, Ernest Burghardt 
wrote:

> +1 for less noise and spam
>
> On Wed, Mar 21, 2018 at 11:56 AM, Galen O'Sullivan 
> wrote:
>
> > Yeah, I think I'm sending myself convinced by Swapnil's argument.
> >
> > How about muting the "nightly build succeeded" email?
> >
> > On Wed, Mar 21, 2018 at 9:58 AM, Sean Goller  wrote:
> >
> > > Concourse sends mail whenever a job fails.
> > >
> > > On Wed, Mar 21, 2018 at 9:49 AM, Swapnil Bawaskar <
> sbawas...@pivotal.io>
> > > wrote:
> > >
> > > > I know travis is already configured to send emails only when the
> build
> > > > breaks and then when it is fixed. Is concourse configured the same?
> > > >
> > > > On Wed, Mar 21, 2018 at 9:38 AM Patrick Rhomberg <
> prhomb...@pivotal.io
> > >
> > > > wrote:
> > > >
> > > > > I'm with Swapnil on this one.  I think the way we make it less
> noisy
> > is
> > > > to
> > > > > take the time to fix the failing tests.
> > > > >
> > > > > I suppose we could split the difference and give the CI emails a,
> > say,
> > > > > daily cadence.  No news is good news, or else it gives you all the
> > > > failures
> > > > > in the last 24 hours.  Don't know how easy that would be to cache
> and
> > > > > report under the existing framework, though.
> > > > >
> > > > > On Wed, Mar 21, 2018 at 12:05 AM, Jacob Barrett <
> jbarr...@pivotal.io
> > >
> > > > > wrote:
> > > > >
> > > > > > It’s sad that the most frequent spammer... e... I mean mailer
> > is
> > > > the
> > > > > > new CI process. If we aren’t going to send it elsewhere how can
> we
> > > make
> > > > > it
> > > > > > less noisy?
> > > > > >
> > > > > > -Jake
> > > > > >
> > > > > >
> > > > > > > On Mar 20, 2018, at 8:37 PM, Dan Smith 
> > wrote:
> > > > > > >
> > > > > > > I was curious about the stats for bot vs. humans on the dev
> list.
> > > Out
> > > > > of
> > > > > > > 915 messages, looks like we're about 50% robot.
> > > > > > >
> > > > > > > I'm still be in favor of not sending these messages to
> dev@geode.
> > > > Long
> > > > > > time
> > > > > > > members have probably already created a mail filter by now (I
> > know
> > > I
> > > > > > have)
> > > > > > > so we're only hurting newbies by sending a bunch of messages.
> > > > > > >
> > > > > > > 1) apac...@gmail.com 241
> > > > > > > 2) Spring CI 109
> > > > > > > 3) Kirk Lund 63
> > > > > > > 4) Apache Jenkins Server 51
> > > > > > > 5) Anthony Baker 41
> > > > > > > 6) Dan Smith 40
> > > > > > > 7) Travis CI 38
> > > > > >
> > > > >
> > > >
> > >
> >
>


Re: ASF Quarterly report - final

2018-02-13 Thread Mark Bretl
Thanks Dave! Report has been submitted.

--Mark

On Tue, Feb 13, 2018 at 1:36 PM, Dave Barnes  wrote:

> Here's the final report, approved by all who reviewed it.
> Mark: I lack credentials to submit this myself - I'll leave that to you.
> Cheers,
> Dave
>
> ## 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.
>
>
>
> ## Activity:
>
>  - Released Apache Geode 1.4 with 288 resolved tickets, including the
> following improvements:
>
> - Added a JDBC connector
>
> - Introduced an improved eviction algorithm
>
> - Added Lucene indexing/searching for nested objects
>
> - Added new examples
>
> - Provided blacklist/whitelist capability for Java serialization
>
> - Several additions and improvements to the gfsh CLI utility
>
>
>  - The SpringOne Platform conference in December 2017 included 12 talks on
> Apache Geode
>
>   ([https://springoneplatform.io/geode](https://
> springoneplatform.io/geode)
> ).
>
>   The talks were given by users and developers of Geode, covering uses
> cases, extensions, and
>
>   integration stories.  All the talks were well-attended and the afternoon
> sessions the first day were
>
>   standing-room-only.
>
>
>
> ## Health report:
>
> - We’re continuing to work on attracting new contributors and making it
> easier
>
> to participate in the community.
>
> - Mailing list activity is healthy.
>
> - Work has started toward the next Geode 1.5.0 release, with a plan to
> include improvements in usability and security.
>
>
>
> ## PMC changes:
>
>  - Currently 43 PMC members.
>
>  - New PMC members:
>
> - Michael W. Dodge was added to the PMC on Tue Jan 23 2018
>
> - Brian Rowe was added to the PMC on Tue Jan 23 2018
>
>
>
> ## Committer base changes:
>
>  - Currently 88 committers.
>
>  - New commmitters:
>
> - Michael W. Dodge was added as a committer on Wed Jan 24 2018
>
> - Brian Rowe was added as a committer on Wed Jan 24 2018
>
>
>
> ## Releases:
>
>  - 1.4.0 was released on Fri Jan 26 2018, including new features, examples,
> and bug fixes.
>
> - Release notes:
> https://cwiki.apache.org/confluence/display/GEODE/
> Release+Notes#ReleaseNotes-1.4.0
>
> - Release artifacts: http://geode.apache.org/releases/
>
> - Release documentation:
> http://geode.apache.org/docs/guide/14/about_geode.html
>
>
>
>
>
> ## Mailing list activity:
>
>  - dev@geode.apache.org:
>
> - 176 subscribers (down -2 in the last 3 months):
>
> - 734 emails sent to list (1784 in previous quarter)
>
>
>
>  - iss...@geode.apache.org:
>
> - 54 subscribers (down -1 in the last 3 months):
>
> - 5677 emails sent to list (4632 in previous quarter)
>
>
>
>  - u...@geode.apache.org:
>
> - 240 subscribers (up 5 in the last 3 months):
>
> - 253 emails sent to list (225 in previous quarter)
>
>
>
>
>
> ## JIRA activity:
>
>  - 677 JIRA tickets created in the last 3 months
>
>  - 495 JIRA tickets closed/resolved in the last 3 months
>


Re: Updating dependencies

2018-02-12 Thread Mark Bretl
OWASP is good too, even has a Gradle plugin [1]

--Mark

[1] https://github.com/jeremylong/dependency-check-gradle

On Mon, Feb 12, 2018 at 12:36 PM, Anthony Baker <aba...@pivotal.io> wrote:

>
>
> > On Feb 12, 2018, at 12:29 PM, Mark Bretl <asf.mbr...@gmail.com> wrote:
> >
> > Late to the game here, as I see this was merged today…
> >
>
> Comments always appreciated :-)
>
> > The addition of the Gradle versions plugin is good and hopefully we can
> go
> > farther down the path of dependency scanning by adding security as well.
> > Currently, GitHub has this setup for Ruby and JavaScript [1], however it
> is
> > lacking Java dependencies. Until GitHub can support Java dependencies, I
> > would suggest we look at other tools, such as snyk.io [2], for tracking
> our
> > dependencies with security vulnerabilities.
> >
>
> dependency-check [1] from OWASP is pretty nice and easy to run
> automatically in a pipeline.
>
> Anthony
>
> [1] https://www.owasp.org/index.php/OWASP_Dependency_Check <
> https://www.owasp.org/index.php/OWASP_Dependency_Check>
>
>
> > --Mark
> >
> > [1] https://github.com/blog/2470-introducing-security-alerts-on-github
> > [2] https://snyk.io/
> >
> > On Fri, Feb 9, 2018 at 4:06 PM, Anthony Baker <aba...@pivotal.io> wrote:
> >
> >> Hi all,
> >>
> >> I’ve got a PR [1] open that updates lots of dependencies.  Please review
> >> and let me know if you have any concerns.  I’d like to merge it early
> next
> >> week barring any objections.
> >>
> >> Thanks,
> >> Anthony
> >>
> >> [1] https://github.com/apache/geode/pull/1400 <
> >> https://github.com/apache/geode/pull/1400>
> >>
> >>
>
>


Re: Updating dependencies

2018-02-12 Thread Mark Bretl
Late to the game here, as I see this was merged today...

The addition of the Gradle versions plugin is good and hopefully we can go
farther down the path of dependency scanning by adding security as well.
Currently, GitHub has this setup for Ruby and JavaScript [1], however it is
lacking Java dependencies. Until GitHub can support Java dependencies, I
would suggest we look at other tools, such as snyk.io [2], for tracking our
dependencies with security vulnerabilities.

--Mark

[1] https://github.com/blog/2470-introducing-security-alerts-on-github
[2] https://snyk.io/

On Fri, Feb 9, 2018 at 4:06 PM, Anthony Baker  wrote:

> Hi all,
>
> I’ve got a PR [1] open that updates lots of dependencies.  Please review
> and let me know if you have any concerns.  I’d like to merge it early next
> week barring any objections.
>
> Thanks,
> Anthony
>
> [1] https://github.com/apache/geode/pull/1400 <
> https://github.com/apache/geode/pull/1400>
>
>


Volunteer Request: Write Draft Board Report For February 2018

2018-02-05 Thread Mark Bretl
Hi Everyone,

Great job on getting 1.4.0 released, which makes it good timing that we are
scheduled to report to the Apache board for the board meeting on February
21st.

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

Previous Reports: https://whimsy.apache.org/board/minutes/Geode.html

Would anyone like to volunteer to write a draft of the report?

Best regards,

--Mark


Re: build is broken

2018-01-23 Thread Mark Bretl
I agree with Kirk. A simple notice to the dev list to say what dependency
and why it is being added, this would also be an opportunity to make sure
the dependency is not using a Cat-X license [1].

--Mark

[1] https://www.apache.org/legal/resolved.html#category-x

On Tue, Jan 23, 2018 at 2:09 PM, Kirk Lund  wrote:

> Discussing the addition of new dependencies is something the community
> should be doing on the dev-list regardless of how many git repos we have.
> It's part of the Apache Way that we are beholden to as an Apache project.
>
> On Tue, Jan 23, 2018 at 11:25 AM, Udo Kohlmeyer 
> wrote:
>
> > This really just another reason that we should be pushing for the
> > separation of Geode into different (independent) modules with potentially
> > separate repos.
> > This way modules can advance and iterate faster without having to be
> > influenced by external factors causing unrelated failures.
> >
> > I would push for this, rather than having to slow the whole development
> > process down, whilst waiting for consensus on libraries used for external
> > tooling.
> >
> > --Udo
> >
> > On Tue, Jan 23, 2018 at 11:15 AM, Kirk Lund  wrote:
> >
> > > I have it working now. My IntelliJ project was using JDK1.8.0_66 for
> > Gradle
> > > which prevented updating of dependencies which then caused compilation
> in
> > > IntelliJ to fail on that new dependency.
> > >
> > > This doesn't resolve my main issue here which is this: *all new
> > > dependencies should be discussed on the dev list before introducing
> them
> > in
> > > a commit*. Can you please point me at an email that proposes adding
> this
> > > dependency?
> > >
> > > On Tue, Jan 23, 2018 at 10:10 AM, Anthony Baker 
> > wrote:
> > >
> > > > I just ran `gradle clean build` from HEAD and did not get any errors.
> > > >
> > > > > On Jan 23, 2018, at 10:08 AM, Jens Deppe 
> wrote:
> > > > >
> > > > > The dependency is the rmi-io library. It provides functionality for
> > > > > streaming data over RMI.
> > > > >
> > > > > It was added a few weeks ago, so I'm not sure why your build is
> > > breaking
> > > > > now.
> > > > >
> > > > > --Jens
> > > > >
> > > > > On Tue, Jan 23, 2018 at 9:41 AM, Kirk Lund 
> wrote:
> > > > >
> > > > >> Looks like this dependency is Jackcess (used for reading and
> writing
> > > MS
> > > > >> Access databases). I cannot find any discussion about adding this
> > > > >> dependency on the dev-list. Why does Geode need to talk to MS
> Access
> > > > >> databases for Cluster Configuration?
> > > > >>
> > > > >> It does have an Apache 2.0 license, but I think there are two
> > problems
> > > > with
> > > > >> adding Jackcess: 1) all new dependencies should be discussed on
> > > dev-list
> > > > >> BEFORE adding them to Geode, 2) we shouldn't need to talk to MS
> > Access
> > > > for
> > > > >> Cluster Configuration.
> > > > >>
> > > > >> On Tue, Jan 23, 2018 at 9:30 AM, Kirk Lund 
> > wrote:
> > > > >>
> > > > >>> I just tried to compile Geode develop.
> ClusterConfigurationService
> > > has
> > > > >> two
> > > > >>> broken imports that don't exist:
> > > > >>>
> > > > >>> import com.healthmarketscience.rmiio.RemoteInputStream;
> > > > >>> import com.healthmarketscience.rmiio.RemoteInputStreamClient;
> > > > >>>
> > > > >>> Was there a new dependency added to Geode?
> > > > >>>
> > > > >>
> > > >
> > > >
> > >
> >
>


Re: Default branch for geode should be 'develop'

2017-12-11 Thread Mark Bretl
+1

On Mon, Dec 11, 2017 at 2:07 PM, Dan Smith  wrote:

> +1
>
> -Dan
>
> On Mon, Dec 11, 2017 at 1:40 PM, Jens Deppe  wrote:
>
> > Currently, github has the default branch for apache/geode set to
> 'master'.
> > (which is why you need to point the relevant branch to 'develop' for
> every
> > new PR).
> >
> > Do we agree that this should be set to 'develop'?
> >
> > (I've messaged with some of the Infra folks and nothing appears to have
> > changed recently so this is a bit weird).
> >
> > I'll create a Jira once there is agreement.
> >
> > --Jens
> >
>


Re: Test Coverage Mapping

2017-11-10 Thread Mark Bretl
Yea, the integration into the Apache SonarQube dropped off at some point. I
can look into it again.

As for the coverage for tests, take a look at $root/gradle/code-analysis.gradle
for seeing how code coverage works now. I think we have 'test
integrationTest distributedTest' configured for creating HTML reports,
acceptanceTests need to be added.

--Mark

On Fri, Nov 10, 2017 at 2:23 PM, Dan Smith  wrote:

> Sorry, wrong link. I think they updated analysis.apache.org to this:
>
> https://builds.apache.org/analysis
>
> -Dan
>
> On Fri, Nov 10, 2017 at 2:00 PM, Dan Smith  wrote:
>
> > We have some support in our gradle build to run tests coverage manually
> > with something like this:
> >
> > ../gradlew clean test integrationTest distributedTest  acceptanceTest
> > -PcodeCoverage jacocoOverallTestReport
> >
> > This should generate a code coverage report. At one point I know we were
> > talking about integrating with analysis.apache.org, which is running
> > sonarqube, but I don't know what happened with that. I don't think there
> is
> > any job that is automatically running these tests with coverage.
> >
> > -Dan
> >
> > On Fri, Nov 10, 2017 at 12:11 PM, Patrick Rhomberg  >
> > wrote:
> >
> >> Hello, all.
> >>
> >>   While looking at expanding testing coverage, the natural question
> arose:
> >> what does the existing test coverage map look like?
> >>   Does anyone know if we have an existing code-coverage analysis done as
> >> part of our testing?  If there is, does anyone know if our DUnitTests or
> >> AcceptanceTests are (or could be) included in the coverage map?  I think
> >> this could be a very useful tool in driving new tests and the detection
> of
> >> dead code.
> >>
> >> Imagination is Change.
> >> ~Patrick
> >>
> >
> >
>


Re: [DRAFT] Geode Board Report November 2017

2017-11-10 Thread Mark Bretl
Thanks!

I have submitted the report. If anyone else finds an issue, please let me
know and I can edit it.

--Mark

On Fri, Nov 10, 2017 at 9:08 AM, Dan Smith  wrote:

> Looks good to me!
>
> We did switch from git.apache.org to gitbox.apache.org and github this
> quarter. That may partly explain changes in the mailing list message counts
> if we get a getting fewer automated emails with the new system.
>
> -Dan
>
> On Thu, Nov 9, 2017 at 5:15 PM, Joey McAllister 
> wrote:
>
> > Hi folks,
> >
> > Please review the below draft of our report to the board for this past
> > quarter
> > and offer corrections. As Mark mentioned, we need to submit the draft
> ASAP,
> > preferably before the weekend. Please review and comment by 5p Pacific
> Time
> > tomorrow (i.e., about 24 hours from now).
> >
> > I do have one question regarding the mailing list health: Does anyone
> have
> > any thoughts about the decline in email count to the Dev list? We have
> > about half the number of emails to the Dev list as we had in the previous
> > quarter, and that number also declined between the previous two reports.
> I
> > suspect that this might be related to the creation of the Issues email
> list
> > (and that the number has now stabilized), but I wanted to put it to the
> > community.
> >
> > Thanks!
> > Joey
> >
> > -
> >
> > ## Description:
> > - Apache Geode provides a database-like consistency model, reliable
> > transaction
> >   processing and a shared-nothing architecture to maintain low-latency
> >   performance with high-concurrency processing.
> >
> > ## Issues:
> > - There are no issues requiring board attention.
> >
> > ## Activity:
> > - Released Geode 1.3.0 with 371 resolved tickets, including the following
> >   improvements:
> >   - Finer-grained security
> >   - The ability to snapshot multiple regions simultaneously
> >   - New Geode examples:
> > - Putting multiple values at once
> > - Demonstrating Lucene indexing and searching
> >
> > ## Health report:
> > - We’re continuing to work on attracting new contributors and making it
> > easier
> >   to participate in the community.
> > - Mailing list activity is healthy.
> > - Work has started toward the next Geode 1.4.0 release, with a plan to
> > include
> >   the new client/server protocol.
> >
> > ## PMC changes:
> > - Currently 41 members
> > - New PMC members:
> >   - David Kimura was added to the PMC on Sun Sep 10 2017.
> >   - Galen O'Sullivan was added to the PMC on Mon Sep 25 2017.
> >   - Mike Stolz was added to the PMC on Sun Oct 29 2017.
> >   - Nick Reich was added to the PMC on Thu Oct 19 2017.
> >   - Patrick Rhomberg was added to the PMC on Tue Oct 31 2017.
> >
> > ## Committer base changes:
> > - Currently 86 committers.
> > - New committers:
> >   - David Kimura was added as a committer on Mon Sep 11 2017.
> >   - Galen O'Sullivan was added as a committer on Tue Sep 05 2017.
> >   - Mike Stolz was added as a committer on Sat Oct 21 2017.
> >   - Nick Reich was added as a committer on Sat Oct 14 2017.
> >   - Patrick Rhomberg was added as a committer on Wed Nov 01 2017.
> >
> > ## Releases:
> > - Most recent release was 1.3.0 on Tue Oct 31 2017. Geode 1.3.0 contains
> a
> >   number of bug fixes and improvements, including finer-grained security
> > and
> >   the ability to snapshot multiple regions simultaneously.
> >   - Release notes:
> >
> > https://cwiki.apache.org/confluence/display/GEODE/
> > Release+Notes#ReleaseNotes-1.3.0
> >   - Release artifacts: http://geode.apache.org/releases/
> >   - Release documentation:
> > http://geode.apache.org/docs/guide/13/about_geode.html
> >
> > ## Mailing list activity:
> > - dev@geode.apache.org:
> >   - 175 subscribers (up 1 in the last 3 months):
> >   - 2030 emails sent to list (4170 in previous quarter)
> >
> > - iss...@geode.apache.org:
> >   - 55 subscribers (down 1 in the last 3 months):
> >   - 4883 emails sent to list (3066 in previous quarter)
> >
> > - u...@geode.apache.org:
> >   - 234 subscribers (up 2 in the last 3 months):
> >   - 236 emails sent to list (277 in previous quarter)
> >
> > ## JIRA activity:
> > - 547 JIRA tickets created in the last 3 months
> > - 422 JIRA tickets closed/resolved in the last 3 months
> >
>


Re: Volunteer Request: Write Draft Board Report For November 2017

2017-11-08 Thread Mark Bretl
Thanks!

--Mark

On Wed, Nov 8, 2017 at 1:58 PM, Alexander Murmann <amurm...@pivotal.io>
wrote:

> Hi Mark,
>
> Thanks for bringing this up! Joey McAllister and I can pair on a draft
> tomorrow.
>
> On Wed, Nov 8, 2017 at 12:04 PM, Mark Bretl <mbr...@apache.org> wrote:
>
> > Hi Everyone,
> >
> > We are scheduled to report to the Apache board for the board meeting on
> > November 15 and need to submit a report ASAP, preferrably before the
> > weekend. Sorry for the late notice.
> >
> > Template: https://cwiki.apache.org/confluence/display/GEODE/ASF+
> > Board+Report
> > +Template
> >
> > Previous Reports: https://whimsy.apache.org/board/minutes/Geode.html
> >
> > Would anyone like to volunteer to write a draft of the report?
> >
> > Best regards,
> >
> > --Mark
> >
>


Volunteer Request: Write Draft Board Report For November 2017

2017-11-08 Thread Mark Bretl
Hi Everyone,

We are scheduled to report to the Apache board for the board meeting on
November 15 and need to submit a report ASAP, preferrably before the
weekend. Sorry for the late notice.

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

Previous Reports: https://whimsy.apache.org/board/minutes/Geode.html

Would anyone like to volunteer to write a draft of the report?

Best regards,

--Mark


Re: Permissions To View Builds?

2017-11-07 Thread Mark Bretl
Hi Sarge,

Not sure what is going on with the URL, however, there are two different
URLs you can use for the nightly build job:

Old Jenkins UI:
https://builds.apache.org/view/E-G/view/Geode/job/Geode-nightly/

New Jenkins UI:
https://builds.apache.org/blue/organizations/jenkins/Geode-nightly/

Let me know if those don't work for you,

--Mark

On Tue, Nov 7, 2017 at 12:35 PM, Michael William Dodge 
wrote:

> I tried to check on the nightly builds via https://builds.apache.org/
> jobs/Geode-nightly/ . I
> think that's the right URL but I get an error message that says "Invalid
> login information. Please try again.". If that's the right URL, may I have
> permissions to view the nightly builds? Thanks.
>
> Sarge


Re: Removing the old Authenticator/AccessControl interfaces

2017-10-30 Thread Mark Bretl
If we are talking about the following:
https://github.com/apache/geode/blob/develop/geode-core/src/main/java/org/apache/geode/security/Authenticator.java
https://github.com/apache/geode/blob/develop/geode-core/src/main/java/org/apache/geode/security/AccessControl.java

They are both marked '@deprecated since Geode 1.0' which I interpret to
mean they were deprecated in Geode 1.0 and need to stay until 2.0, if we
keep with semver.

--Mark



On Mon, Oct 30, 2017 at 3:55 PM, Jinmei Liao  wrote:

> Yes, it's deprecated in 1.0.
>
> On Mon, Oct 30, 2017 at 3:39 PM, Dan Smith  wrote:
>
> > Are you saying these interfaces were already deprecated in 1.0? If so,
> then
> > I think we can remove them. If they have been deprecated after 1.0, I
> think
> > we have to wait until 2.0 to remove them.
> >
> > -Dan
> >
> > On Mon, Oct 30, 2017 at 1:18 PM, Jinmei Liao  wrote:
> >
> > > The old security framework, basically Authentcator/AccessControl
> > interfaces
> > > and the usage of them inside GEODE is deprecated since 1.0. I am
> > wondering
> > > since 1.3 is out already, can we start removing these interfaces and
> > > usages? It would enable of deleting bunch of unmanageable tests.
> > >
> > >
> > > --
> > > Cheers
> > >
> > > Jinmei
> > >
> >
>
>
>
> --
> Cheers
>
> Jinmei
>


Re: need suggestion about below exception

2017-10-27 Thread Mark Bretl
+ user

On Fri, Oct 27, 2017 at 9:37 AM, dinesh 1004 
wrote:

> Hi All,
> Is there any geode test  class which populate data in
> *ParallelGatewaySenderQueue
> and create some back log. *
> Insert/remove operation i can test.
>
> Thanks,
> Dinesh Akhand
>
> On Fri, Oct 27, 2017 at 9:24 PM, Dinesh Akhand 
> wrote:
>
> > Any one suggest about below exception:
> >
> > at org.apache.geode.internal.cache.DiskEntry$Helper.
> > removeFromDisk(DiskEntry.java:1505)
> > at org.apache.geode.internal.cache.AbstractOplogDiskRegionEntry.
> > removePhase1(AbstractOplogDiskRegionEntry.java:42)
> > at org.apache.geode.internal.cache.AbstractRegionEntry.
> > destroy(AbstractRegionEntry.java:896)
> > at org.apache.geode.internal.cache.AbstractRegionMap.
> destroyEntry(
> > AbstractRegionMap.java:3084)
> > at org.apache.geode.internal.cache.AbstractRegionMap.
> > destroy(AbstractRegionMap.java:1422)
> > at org.apache.geode.internal.cache.LocalRegion.mapDestroy(
> > LocalRegion.java:6566)
> > at org.apache.geode.internal.cache.LocalRegion.mapDestroy(
> > LocalRegion.java:6540)
> > at org.apache.geode.internal.cache.BucketRegion.
> > basicDestroy(BucketRegion.java:1183)
> > at org.apache.geode.internal.cache.AbstractBucketRegionQueue.
> > basicDestroy(AbstractBucketRegionQueue.java:352)
> > at org.apache.geode.internal.cache.BucketRegionQueue.
> basicDestroy(
> > BucketRegionQueue.java:363)
> > at org.apache.geode.internal.cache.LocalRegion.
> > validatedDestroy(LocalRegion.java:)
> > at org.apache.geode.internal.cache.DistributedRegion.
> > validatedDestroy(DistributedRegion.java:904)
> > at org.apache.geode.internal.cache.LocalRegion.destroy(
> > LocalRegion.java:1096)
> > at org.apache.geode.internal.cache.AbstractRegion.destroy(
> > AbstractRegion.java:315)
> > at org.apache.geode.internal.cache.LocalRegion.remove(
> > LocalRegion.java:8976)
> > at org.apache.geode.internal.cache.wan.parallel.
> > ParallelGatewaySenderQueue.clearPartitionedRegion(
> > ParallelGatewaySenderQueue.java:1830)
> > at org.apache.geode.internal.cache.wan.parallel.
> > ParallelGatewaySenderQueue.clearQueue(ParallelGatewaySenderQueue.
> > java:1800)
> > at org.apache.geode.internal.cache.wan.parallel.
> > ConcurrentParallelGatewaySenderQueue.clearQueue(
> > ConcurrentParallelGatewaySenderQueue.java:237)
> > at org.apa
> >
> > In geode 1.1 Clear queue function is working correctly for us.
> > But with same configuration in geode 1.2 is not working.
> >
> > I tried to add the debug log and printed  disk region which is created
> > inside the LocalRegion.java, diskregion is not null.
> >
> > [info 2017/10/27 12:26:43.196 IDT eaasrt-server1  > Processor 3> tid=0xf2] akhand diskregion/__PR/_B__AsyncEventQueue
> > __PWInfoQueue__PARALLEL__GATEWAY__SENDER__QUEUE_4fullpath:=/__PR/_B__
> > AsyncEventQueue__PWInfoQueue__PARALLEL__GATEWAY__SENDER__QUEUE_4isuse
> >
> > Which is not Null , also  DiskStoreImpl is Not null
> >
> > info 2017/10/27 13:59:36.407 IDT eaasrt-server1  > Processor 2> tid=0xe8] akhand diskregion/__PR/_B__AsyncEventQueue
> > __PWInfoQueue__PARALLEL__GATEWAY__SENDER__QUEUE_109fullpath:=/__PR/_B__
> > AsyncEventQueue__PWInfoQueue__PARALLEL__GATEWAY__SENDER__QUEUE_109i
> > suse:false,dsi:PWInfo-queue-overflow
> >
> > Thanks,
> > Dinesh Akhand
> > This message and the information contained herein is proprietary and
> > confidential and subject to the Amdocs policy statement,
> >
> > you may review at https://www.amdocs.com/about/email-disclaimer <
> > https://www.amdocs.com/about/email-disclaimer>
> >
>


Re: [DISCUSS] CI improvements

2017-10-06 Thread Mark Bretl
Correct, there is no requirement from ASF about where to run CI or even to
run CI. I am all for the best tools and stable (and repeatable)
environments. I would be open to seeing how Concourse could work for Geode.

Once the Concourse environment is setup, probably would be best to update
the Jenkins job to a pipeline job type as well.

There a few questions I have, which can be discussed as we go:
- What does 'donate' mean for Pivotal? Is there a, for lack of a better
term, contract or is this a 'good faith' effort? I am hesitant to go to any
corporately controlled infrastructure, especially since the entity could
decide to stop funding.
- What types of activities will require admin assistance?
- Who will be watching the dev list for requests?

--Mark

On Fri, Oct 6, 2017 at 10:05 AM, Kenneth Howe  wrote:

> +1 - Reduce the noise level for analyzing CI results
>
> > On Oct 6, 2017, at 9:49 AM, Udo Kohlmeyer  wrote:
> >
> > +1 Switch... parallel runs would be safest
> >
> > On Fri, Oct 6, 2017 at 9:42 AM, Jianxia Chen  wrote:
> >
> >> +1 to switch to Concourse
> >> +1 As a first step we could run both CI systems side-by-side and see how
> >> the Concourse approach works for our project.
> >>
> >> On Fri, Oct 6, 2017 at 7:08 AM, Anthony Baker 
> wrote:
> >>
> >>> Hi all,
> >>>
> >>> I’d like to propose the following that we switch our continuous
> >>> integration (CI) system from Jenkins [1] to Concourse [2].  I suggest
> >>> this because we continue to experience a significant number of
> >>> environmental-related test failures.
> >>>
> >>> These issues include CPU interference from other Jenkins jobs on the
> >>> same host, running out of disk space, port conflicts, and other
> >>> gremlins.  The net effect is that we are only getting 1-2 successful
> >>> builds per month.  Certainly not all test failures can be traced back
> >>> to environmental issues.  However, internal testing on isolated VM’s
> >>> shows a combined success rate of about 3X higher compared to ASF
> >>> Jenkins for the same tests.  This is still definitely NotAwesome, but
> >>> removing environmental factors will let us focus on stabilizing flaky
> >>> tests.
> >>>
> >>> Concourse is an Apache-licensed open source CI system based on
> >>> pipelines.  The pipelines are defined in a YML file containing job
> >>> definitions—inputs, outputs, resources, and tasks.  A task is simply a
> >>> bash script that returns 0/1 for success/failure.  A web UI displays
> >>> build status.  Importantly, each job runs inside an isolated
> >>> container.  The containers are load-balanced across a pool of workers.
> >>> For an example of a build pipeline, see [3] for the pipeline used to
> >>> build concourse itself.
> >>>
> >>> A Concourse environment is deployed and managed in cloud environments
> >>> through bosh [4].  Pivotal has agreed to donate AWS and/or GCP compute
> >>> and storage resources as well as manage the infrastructure.  These
> >>> project resources would be available for use by all committers and
> >>> community members regardless of corporate affiliations.  Note that
> >>> AFAIK there is no explicit requirement to host CI on ASF
> >>> infrastructure—unlike for critical project resources such as source
> >>> code, mailing lists, and issue tracking.
> >>>
> >>> The source for the pipeline and job scripts would reside within the
> >>> geode-* repos.  Geode committers would be able to modify those, same
> >>> as with our .travis.yml scripts.  All test results and build artifacts
> >>> would be publicly viewable just like with our Jenkins build output
> >>> today.  Requests for admin assistance would go through the dev@geode
> >>> mailing list.
> >>>
> >>> Thoughts?  As a first step we could run both CI systems side-by-side
> >>> and see how the Concourse approach works for our project.
> >>>
> >>> Thanks,
> >>> Anthony
> >>>
> >>>
> >>> [1] https://builds.apache.org/job/Geode-nightly/
> >>> [2] https://concourse.ci
> >>> [3] https://ci.concourse.ci
> >>> [4] https://bosh.io
> >>>
> >>
> >
> >
> >
> > --
> > Kindest Regards
> > -
> > *Udo Kohlmeyer* | *Snr Solutions Architect* |*Pivotal*
> > *Mobile:* +61 409-279-160 | ukohlme...@pivotal.io
> > 
> > www.pivotal.io
>
>


Re: Rebase and squash before merging PRs

2017-10-05 Thread Mark Bretl
One helpful Git configuration I use which can help reduce merge commits is
to set the default action to rebase when doing a pull. To set this a global
configuration default on your system, do the following command:

git config --global pull.rebase true

--Mark

On Thu, Oct 5, 2017 at 3:00 PM, Jared Stewart  wrote:

> I’ve been seeing a lot more merge commits on develop since we moved to
> Gitbox.  Just wanted to give everyone a friendly reminder to please rebase
> before merging to keep our git history tidy and readable.
>
> Thanks,
> Jared


Re: [DISCUSS] Removal of "Submit an Issue" from Geode webpage

2017-09-29 Thread Mark Bretl
+1 for removal

—Mark

On Fri, Sep 29, 2017 at 1:17 PM Gregory Chase  wrote:

> Yes please, especially since I'm not the one posting these :)
>
> On Fri, Sep 29, 2017 at 11:35 AM, Dave Barnes  wrote:
>
> > +1 to removing the button.
> > +1 to Dan's suggestion of nudging users toward the mailing list.  I see a
> > place we could add a few words on the Community page, where the Users
> > mailing list is the first entry; add to the blurb "or raise an issue".
> (The
> > Mailing Lists menu choice takes you here, as well.)
> >
> >
> > On Fri, Sep 29, 2017 at 11:15 AM, Dan Smith  wrote:
> >
> > > +1 - I think it would be better to just encourage users to send
> > > issues/questions to the users list initially.
> > >
> > > -Dan
> > >
> > > On Fri, Sep 29, 2017 at 11:08 AM, Michael William Dodge
> > >  wrote:
> > > > +1 to improving the signal-to-noise ratio
> > > >
> > > >> On 29 Sep, 2017, at 11:07, Jason Huynh  wrote:
> > > >>
> > > >> GEODE-3280
> > > >
> > >
> >
>
>
>
> --
> Greg Chase
>
> Product team, Pivotal Cloud Foundry Services
> https://pivotal.io/platform/services 
>
> Pivotal Software
> http://www.pivotal.io/
>
> 650-215-0477
> @GregChase
>


New Geode PMC Member: Galen O'Sullivan

2017-09-26 Thread Mark Bretl
The Apache Geode Project Management Committee has invited Galen
O'Sullivan to join the Geode PMC and we are pleased to announce he has
accepted.

Please join me in welcoming Galen!

Best regards,

Mark
On behalf of the Apache Geode PMC


Re: How gitbox works

2017-09-18 Thread Mark Bretl
Hi Kirk,

I would go to the GitBox account linking utility page at
https://gitbox.apache.org/setup/ and verify all three steps are green. If
they are green, then probably need to contact INFRA to figure out the issue
with your account.

--Mark

On Mon, Sep 18, 2017 at 10:13 AM, Kirk Lund  wrote:

> PS: If I had known the switchover to github would be this messy I would
> have voted against it.
>
> On Mon, Sep 18, 2017 at 10:12 AM, Kirk Lund  wrote:
>
>> Yeah, I followed all of the directions shared by Jens and Bruce. I also
>> had my github account added to my Apache account for the last 2-3 years.
>> Apparently the switchover to gitbox removed by commit permission.
>>
>> /Users/klund/dev/geode [525]$ git push
>> ERROR: Permission to apache/geode.git denied to kirklund.
>> fatal: Could not read from remote repository.
>>
>> Please make sure you have the correct access rights
>> and the repository exists.
>>
>> I also don't have the "Merge" button available to me when viewing Apache
>> Geode pull requests.
>>
>> Anyone know who to contact to restore it?
>>
>> Thanks,
>> Kirk
>>
>> On Mon, Sep 18, 2017 at 10:05 AM, Kirk Lund  wrote:
>>
>>> Apparently I no longer have commit access. Anyone know who/how I get
>>> access restored?
>>>
>>> Thanks,
>>> Kirk
>>>
>>> On Mon, Sep 18, 2017 at 9:49 AM, Jacob Barrett 
>>> wrote:
>>>
 GitBox is just a fancy name Apache has given to their service that
 allows us to use GitHub as the source of authority for our Git repo.
 Everything is done on GitHub using the GitHub processes.

 Anyone with write access to GitHub can merge a PR. The PR can be merged
 from the PR GitHub website.

 -Jake


 > On Sep 18, 2017, at 9:43 AM, Kirk Lund  wrote:
 >
 > I've searched and not found a good summary on how gitbox works.
 Anyone know
 > of a good resource?
 >
 > The kinds of questions I have are: if other devs approve my PR, do I
 still
 > need to find another dev to commit for me or can I commit my own PR
 if has
 > been approved?
 >
 > Thanks,
 > Kirk

>>>
>>>
>>
>


Re: Visibility of Skipped tests in Jenkins

2017-08-24 Thread Mark Bretl
Hi Kirk,

I think you are looking for this page,
https://builds.apache.org/blue/organizations/jenkins/Geode-nightly/detail/Geode-nightly/930/tests
?

I see 'Skipped' under the Failed tests.

--Mark

On Thu, Aug 24, 2017 at 11:09 AM, Kirk Lund  wrote:

> In local instances of Jenkins, I can see a list of "Skipped" tests --
> these are JUnit tests which were skipped because they are marked with
> @Ignore or because they have an org.junit.Assume check that wasn't
> satisfied (example: Assume.assumeTrue(isWindows())). I can't figure out
> where that view is in the ASF Jenkins for Geode Nightly Build. Is it there
> and I'm just missing it or I have insufficient permissions?
>
>


Gradle Docker Plugin Fails After Upgrading Gradle To 3.5.1

2017-08-23 Thread Mark Bretl
Hi Everyone,

In the last nightly builds, the builds are not running the distributed
tests due to the Docker plugin not being compatible with Gradle 3.5.1. I
didn't notice this in my testing because for 'precheckin' I do not use the
Docker option. I do see the newest version of the Docker plugin should be
compatible with Gradle 3.5+, however, it does look like there are other
breaking changes which we would need to update. I created GEODE-3509 for
this issue.

My inclination is to keep the Gradle Wrapper update, revert the nightly
build config, and work on the Docker plugin as a side issue since it is
only a 'optional' feature at the moment.

Would do people think?

--Mark


Re: Native commit messages going to dev instead of commit list

2017-08-22 Thread Mark Bretl
Hey Jake,

Sorry I missed your ticket last week, my ticket has been completed and the
commits should now be going to commits@geode and notifications should be
going to dev@geode. I set my issue Type to GitBox Request and got though
the queue fairly quickly.

I don't know the GitBox configuration well enough to know what permissions
we can have. I would email the INFRA list or contact them on HipChat, as
the documentation is still lacking for the GitBox workflow setup.

--Mark

On Mon, Aug 21, 2017 at 6:42 PM, Jacob Barrett <jbarr...@pivotal.io> wrote:

> Mark,
>
> I opened https://issues.apache.org/jira/browse/INFRA-14900 last week.
>
> Do you know if we can get permissions to edit repo settings ourselves? I’d
> like to change the description so it doesn’t say mirror. Hate interrupting
> infra for every minor change we may have along the way.
>
> Thanks,
> Jake
>
>
> Sent from my iPhone
>
> > On Aug 21, 2017, at 5:56 PM, Mark Bretl <mbr...@apache.org> wrote:
> >
> > Oops...that was my copy-paste error on the request. I have opened a new
> > ticket to update the commit mail,
> > https://issues.apache.org/jira/browse/INFRA-14924.
> >
> > --Mark
> >
> >> On Thu, Aug 17, 2017 at 1:43 PM, Dan Smith <dsm...@pivotal.io> wrote:
> >>
> >> Was: Re: [geode-native] branch develop updated: GEODE-3455: Update
> Solaris
> >> build images.
> >>
> >> Probably need to file an infra ticket. I'm guessing this was caused by
> the
> >> gitbox migration.
> >>
> >> On Thu, Aug 17, 2017 at 1:40 PM, Jacob Barrett <jbarr...@pivotal.io>
> >> wrote:
> >>
> >>> I wonder if the native repo wasn't reconfigured when the main repo was.
> >> It
> >>> is not something I can change even though we are not a mirror site.
> >>>
> >>>
> >>> Mark, do you have karma to change this?
> >>>
> >>> -Jake
> >>>
> >>>
> >>>> On Thu, Aug 17, 2017 at 11:25 AM Dan Smith <dsm...@pivotal.io> wrote:
> >>>>
> >>>> I think these messages should be going to commits@geode?
> >>>>
> >>>>> On Thu, Aug 17, 2017 at 11:15 AM, <jbarr...@apache.org> wrote:
> >>>>>
> >>>>> This is an automated email from the ASF dual-hosted git repository.
> >>>>>
> >>>>> jbarrett pushed a commit to branch develop
> >>>>> in repository https://gitbox.apache.org/repos/asf/geode-native.git
> >>>>>
> >>>>>
> >>>>> The following commit(s) were added to refs/heads/develop by this
> >> push:
> >>>>> new 0fba5ce  GEODE-3455: Update Solaris build images.
> >>>>> 0fba5ce is described below
> >>>>>
> >>>>> commit 0fba5cee59d5d53eaab6cc9396eab45df4b8d79c
> >>>>> Author: Jacob Barrett <jbarr...@pivotal.io>
> >>>>> AuthorDate: Wed Aug 2 12:32:34 2017 -0700
> >>>>>
> >>>>>GEODE-3455: Update Solaris build images.
> >>>>>
> >>>>> - Fixes Solaris SPARC image.
> >>>>> - Addes developer images.
> >>>>> ---
> >>>>> packer/build-solaris-sparc.json | 10 +
> >>>>> packer/build-solaris-x86.json   |  7 +++---
> >>>>> packer/dev-solaris-sparc.json   | 38
> >>>>> +
> >>>>> packer/dev-solaris-x86.json | 38
> >>>>> +
> >>>>> packer/solaris/install-cmake.sh |  8 ---
> >>>>> packer/solaris/install-solarisstudio.sh |  1 -
> >>>>> 6 files changed, 91 insertions(+), 11 deletions(-)
> >>>>>
> >>>>> diff --git a/packer/build-solaris-sparc.json
> >>>> b/packer/build-solaris-sparc.
> >>>>> json
> >>>>> index 34aea96..0ce5eec 100644
> >>>>> --- a/packer/build-solaris-sparc.json
> >>>>> +++ b/packer/build-solaris-sparc.json
> >>>>> @@ -1,8 +1,9 @@
> >>>>> {
> >>>>>   "variables":{
> >>>>> "image_name":"build-solaris-sparc",
> >>>>> -"openstack_source_image":"7e1e66f1-8256-4e29-a314-
> >> ee7f54b2f720",
> >>>>> -"vmware_source_image_name":&q

Re: Native commit messages going to dev instead of commit list

2017-08-21 Thread Mark Bretl
Oops...that was my copy-paste error on the request. I have opened a new
ticket to update the commit mail,
https://issues.apache.org/jira/browse/INFRA-14924.

--Mark

On Thu, Aug 17, 2017 at 1:43 PM, Dan Smith  wrote:

> Was: Re: [geode-native] branch develop updated: GEODE-3455: Update Solaris
> build images.
>
> Probably need to file an infra ticket. I'm guessing this was caused by the
> gitbox migration.
>
> On Thu, Aug 17, 2017 at 1:40 PM, Jacob Barrett 
> wrote:
>
> > I wonder if the native repo wasn't reconfigured when the main repo was.
> It
> > is not something I can change even though we are not a mirror site.
> >
> >
> > Mark, do you have karma to change this?
> >
> > -Jake
> >
> >
> > On Thu, Aug 17, 2017 at 11:25 AM Dan Smith  wrote:
> >
> > > I think these messages should be going to commits@geode?
> > >
> > > On Thu, Aug 17, 2017 at 11:15 AM,  wrote:
> > >
> > > > This is an automated email from the ASF dual-hosted git repository.
> > > >
> > > > jbarrett pushed a commit to branch develop
> > > > in repository https://gitbox.apache.org/repos/asf/geode-native.git
> > > >
> > > >
> > > > The following commit(s) were added to refs/heads/develop by this
> push:
> > > >  new 0fba5ce  GEODE-3455: Update Solaris build images.
> > > > 0fba5ce is described below
> > > >
> > > > commit 0fba5cee59d5d53eaab6cc9396eab45df4b8d79c
> > > > Author: Jacob Barrett 
> > > > AuthorDate: Wed Aug 2 12:32:34 2017 -0700
> > > >
> > > > GEODE-3455: Update Solaris build images.
> > > >
> > > >  - Fixes Solaris SPARC image.
> > > >  - Addes developer images.
> > > > ---
> > > >  packer/build-solaris-sparc.json | 10 +
> > > >  packer/build-solaris-x86.json   |  7 +++---
> > > >  packer/dev-solaris-sparc.json   | 38
> > > > +
> > > >  packer/dev-solaris-x86.json | 38
> > > > +
> > > >  packer/solaris/install-cmake.sh |  8 ---
> > > >  packer/solaris/install-solarisstudio.sh |  1 -
> > > >  6 files changed, 91 insertions(+), 11 deletions(-)
> > > >
> > > > diff --git a/packer/build-solaris-sparc.json
> > > b/packer/build-solaris-sparc.
> > > > json
> > > > index 34aea96..0ce5eec 100644
> > > > --- a/packer/build-solaris-sparc.json
> > > > +++ b/packer/build-solaris-sparc.json
> > > > @@ -1,8 +1,9 @@
> > > >  {
> > > >"variables":{
> > > >  "image_name":"build-solaris-sparc",
> > > > -"openstack_source_image":"7e1e66f1-8256-4e29-a314-
> ee7f54b2f720",
> > > > -"vmware_source_image_name":"X.vmx",
> > > > +"openstack_source_image":"",
> > > > +"openstack_flavor":"Oracle Solaris non-global zone - tiny",
> > > > +"vmware_source_image_name":"",
> > > >  "gemfire_archive":"gemfire.tar.gz",
> > > >  "pkg_oracle_com_certificate":"pkg.oracle.com.certificate.pem",
> > > >  "pkg_oracle_com_key":"pkg.oracle.com.key.pem"
> > > > @@ -18,7 +19,7 @@
> > > >"ssh_username":"root",
> > > >"image_name":"native-{{user `version`}}-{{user `image_name`}}
> > > > {{timestamp}}",
> > > >"source_image":"{{user `openstack_source_image`}}",
> > > > -  "flavor":"Oracle Solaris non-global zone - tiny",
> > > > +  "flavor":"{{user `openstack_flavor`}}",
> > > >"insecure":"true"
> > > >  }
> > > >],
> > > > @@ -38,7 +39,8 @@
> > > >"scripts":[
> > > >  "solaris/install-opencsw.sh",
> > > >  "solaris/install-build-tools.sh",
> > > > -"solaris/install-solarisstudio.sh"
> > > > +"solaris/install-solarisstudio.sh",
> > > > +"solaris/install-cmake.sh"
> > > >]
> > > >  },
> > > >  {
> > > > diff --git a/packer/build-solaris-x86.json
> > > b/packer/build-solaris-x86.json
> > > > index b01519e..6a55c82 100644
> > > > --- a/packer/build-solaris-x86.json
> > > > +++ b/packer/build-solaris-x86.json
> > > > @@ -1,8 +1,9 @@
> > > >  {
> > > >"variables":{
> > > >  "image_name":"build-solaris-x86",
> > > > -"openstack_source_image":"c0df7ff9-fc8f-4220-ac1f-
> fd24924dfe7a",
> > > > -"vmware_source_image_name":"X.vmx",
> > > > +"openstack_source_image":"",
> > > > +"openstack_flavor":"Oracle Solaris non-global zone - tiny",
> > > > +"vmware_source_image_name":"",
> > > >  "gemfire_archive":"gemfire.tar.gz",
> > > >  "pkg_oracle_com_certificate":"pkg.oracle.com.certificate.pem",
> > > >  "pkg_oracle_com_key":"pkg.oracle.com.key.pem"
> > > > @@ -18,7 +19,7 @@
> > > >"ssh_username":"root",
> > > >"image_name":"native-{{user `version`}}-{{user `image_name`}}
> > > > {{timestamp}}",
> > > >"source_image":"{{user `openstack_source_image`}}",
> > > > -  "flavor":"Oracle Solaris non-global zone - tiny",
> > > > +  "flavor":"{{user `openstack_flavor`}}",
> > > >"insecure":"true"
> > > >  }
> > > >],
> > > > 

Re: Revert gradle upgrade

2017-08-21 Thread Mark Bretl
I have checked in the update to move the Gradle Wrapper to 3.5.1, with the
fix for Eclipse IDE, into the develop branch.

Hopefully this time we won't need to revert it.

--Mark

On Tue, Jul 25, 2017 at 2:50 PM, Mark Bretl <asf.mbr...@gmail.com> wrote:

> Now that we have 1.2.0 out the door, would I be able to get someone to
> verify my fixes from those who were having trouble with Gradle 3.4.1 in
> their IDE?
>
> Thanks,
>
> --Mark
>
> On Wed, Jun 14, 2017 at 5:08 PM, Mark Bretl <mbr...@apache.org> wrote:
>
>> I think I figured it out.
>>
>> Here is what I did:
>> Fix was to declare the version of Antlr in the dependencies{} because if
>> no version is set, the ANTLR plugin would default to 2.7.7. This was
>> causing issues since the ANTLR plugin was trying to 'change' the version
>> after dependency resolution for its configuration.
>>
>> I successfully tested imported into Eclipse, so I have checked in the
>> changes on the feature/gradle-3.4.1 branch. Would others take some time to
>> see if it works for them now?
>>
>> --Mark
>>
>> On Tue, May 9, 2017 at 10:51 AM, Udo Kohlmeyer <ukohlme...@pivotal.io>
>> wrote:
>>
>>> I think we have to check the ANTLR plugin to understand it's
>>> requirements..
>>>
>>> maybe there is a newer plugin version for ANTLR
>>>
>>>
>>> On 5/9/17 10:00, Kirk Lund wrote:
>>>
>>>> I've reverted the upgrade to gradle 3.4.1. I also went ahead and
>>>> created a
>>>> branch that repeats the upgrade:
>>>>
>>>> feature/gradle-3.4.1
>>>>
>>>> Feel free to experiment with that branch.
>>>>
>>>> On Tue, May 9, 2017 at 9:53 AM, Kirk Lund <kl...@apache.org> wrote:
>>>>
>>>> I'll go ahead and revert the upgrade. Hopefully we can eventually find
>>>>> the
>>>>> cause so we can repeat the upgrade.
>>>>>
>>>>> On Mon, May 8, 2017 at 4:19 PM, Bruce Schuchardt <
>>>>> bschucha...@pivotal.io>
>>>>> wrote:
>>>>>
>>>>> The "eclipse" target fails, too.
>>>>>>
>>>>>> Le 5/8/2017 à 3:32 PM, Kirk Lund a écrit :
>>>>>>
>>>>>> I want to revert the gradle upgrade because it breaks IntelliJ and the
>>>>>>> idea
>>>>>>> gradle task. Please let me know if you have a problem with this.
>>>>>>>
>>>>>>> PS: Please be prepared to help me if you vote against me reverting
>>>>>>> the
>>>>>>> upgrade ;) I really want to be able to work again. Thanks!
>>>>>>>
>>>>>>>
>>>>>>>
>>>
>>
>


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

2017-08-15 Thread Mark Bretl
Hi Jared,

Short answer: No, Longer answer: Ask Infra ;)

We are generally running on VMs with multiple Jenkins executors, which
means we could be sharing the box with other jobs. We have been
piggybacking on other project's systems so far, trying to find 'available'
systems. I have a feeling this is going to be an ongoing issue of getting a
stable environment until we have another solution, such as requesting
dedicated VMs or containers or etc.

Open to ideas here...

--Mark


On Tue, Aug 15, 2017 at 10:59 AM, Jared Stewart  wrote:

> It looks like all of our tests using default ports are failing in the
> nightly build.  Here is my suspicion of what happened: We have some
> Acceptance Tests that spin up separate JVMs for Locators and Servers.
> Those tests make sure to kill their child processes as part of their
> cleanup, but I suspect that when the build times out our test process gets
> hard-killed, which would prevent the proper cleanup from taking place.
> Does anyone have ssh access into this box to look for orphaned Java
> processes?
>
> Thanks,
> Jared
>
> > Begin forwarded message:
> >
> > From: Apache Jenkins Server 
> > Subject: Build failed in Jenkins: Geode-nightly #923
> > Date: August 14, 2017 at 8:53:03 PM PDT
> > To: dev@geode.apache.org, kmil...@pivotal.io, kh...@apache.org,
> bschucha...@pivotal.io, jstew...@pivotal.io, kl...@pivotal.io,
> dschnei...@pivotal.io, dbar...@pivotal.io, n...@pivotal.io
> > Reply-To: dev@geode.apache.org
> >
> > See  irect?page=changes>
> >
> > Changes:
> >
> > [jiliao] GEODE-3328: fix a test failure on windows.
> >
> > [klund] Revert "GEODE-3328: fix a test failure on windows."
> >
> > [klund] GEODE-3436: revert recent refactoring of GFSH commands
> >
> > --
> > [...truncated 129.88 KB...]
> >org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.modules.session.Tomcat8SessionsClientServer
> DUnitTest$$Lambda$56/1529418967.call in VM 1 running on Host
> asf905.gq1.ygridcore.net with 4 VMs
> >at org.apache.geode.test.dunit.VM.invoke(VM.java:387)
> >at org.apache.geode.test.dunit.VM.invoke(VM.java:357)
> >at org.apache.geode.test.dunit.VM.invoke(VM.java:325)
> >at org.apache.geode.modules.session.Tomcat8SessionsClientServer
> DUnitTest.setupServer(Tomcat8SessionsClientServerDUnitTest.java:60)
> >at org.apache.geode.modules.session.Tomcat8SessionsClientServer
> DUnitTest.postSetUp(Tomcat8SessionsClientServerDUnitTest.java:44)
> >
> >Caused by:
> >java.net.BindException: Failed to create server socket on
> null[40,404]
> >at org.apache.geode.internal.net.
> SocketCreator.createServerSocket(SocketCreator.java:783)
> >at org.apache.geode.internal.net.
> SocketCreator.createServerSocket(SocketCreator.java:745)
> >at org.apache.geode.internal.net.
> SocketCreator.createServerSocket(SocketCreator.java:712)
> >at org.apache.geode.internal.cach
> e.tier.sockets.AcceptorImpl.(AcceptorImpl.java:469)
> >at org.apache.geode.internal.cach
> e.CacheServerImpl.start(CacheServerImpl.java:344)
> >at org.apache.geode.modules.sessi
> on.Tomcat8SessionsClientServerDUnitTest.lambda$setupServer$f
> 0fd67c5$1(Tomcat8SessionsClientServerDUnitTest.java:65)
> >
> >Caused by:
> >java.net.BindException: Address already in use (Bind failed)
> >at java.net.PlainSocketImpl.socketBind(Native Method)
> >at java.net.AbstractPlainSocketIm
> pl.bind(AbstractPlainSocketImpl.java:387)
> >at java.net.ServerSocket.bind(ServerSocket.java:375)
> >at org.apache.geode.internal.net.
> SocketCreator.createServerSocket(SocketCreator.java:779)
> >... 5 more
> >
> > org.apache.geode.modules.session.Tomcat8SessionsClientServerDUnitTest >
> testSanity FAILED
> >org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.modules.session.Tomcat8SessionsClientServer
> DUnitTest$$Lambda$56/1529418967.call in VM 1 running on Host
> asf905.gq1.ygridcore.net with 4 VMs
> >at org.apache.geode.test.dunit.VM.invoke(VM.java:387)
> >at org.apache.geode.test.dunit.VM.invoke(VM.java:357)
> >at org.apache.geode.test.dunit.VM.invoke(VM.java:325)
> >at org.apache.geode.modules.session.Tomcat8SessionsClientServer
> DUnitTest.setupServer(Tomcat8SessionsClientServerDUnitTest.java:60)
> >at org.apache.geode.modules.session.Tomcat8SessionsClientServer
> DUnitTest.postSetUp(Tomcat8SessionsClientServerDUnitTest.java:44)
> >
> >Caused by:
> >java.net.BindException: Failed to create server socket on
> null[40,404]
> >at org.apache.geode.internal.net.
> SocketCreator.createServerSocket(SocketCreator.java:783)
> >at 

Re: continuous query - high availability and assurance

2017-08-15 Thread Mark Bretl
+ user

On Tue, Aug 15, 2017 at 10:17 AM, Roi Apelker 
wrote:

> Hi,
>
> I have been working on an issue related to continuous query mechanism, and
> I would like to know if this mechanism, with High availability, assures
> 100% data integrity?
>
> For example, if I have 2 nodes where a client registered to CQ, and one
> node fails, is there any scenario, in which a notification might be lost,
> either not sent at all, or hasn’t reached its destination and will not be
> sent, or any other?
>
> Is there a guarantee that all information pertinent for the CQ will reach
> the subscriber?
>
> Thanks,
>
> Roi
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
>
> you may review at https://www.amdocs.com/about/email-disclaimer <
> https://www.amdocs.com/about/email-disclaimer>
>


Re: Gitbox enables the full GitHub workflow

2017-08-14 Thread Mark Bretl
Ticket created, https://issues.apache.org/jira/browse/INFRA-14876

Lets see where it goes...

--Mark

On Mon, Aug 14, 2017 at 2:13 PM, Jacob Barrett <jbarr...@pivotal.io> wrote:

> Mark, if you want the experience for the next repo you should do it.
> Thanks!
>
> -Jake
>
>
> Sent from my iPhone
>
> > On Aug 14, 2017, at 1:17 PM, Ernest Burghardt <eburgha...@pivotal.io>
> wrote:
> >
> > Mark, Go ahead and file it and geode-native will be the canaries...
> >
> > Thanks,
> > Ernie
> >
> >> On Mon, Aug 14, 2017 at 2:16 PM, Mark Bretl <mbr...@apache.org> wrote:
> >>
> >> Since we have people wanting this and need a small experiment group to
> >> blaze the trail for us, I think the geode-native would be a good choice
> >> since it has active PRs and commits. Looks like the process to migrate
> from
> >> Git@ASF to GitHub is to create an INFRA ticket with type 'Gitbox
> Request'.
> >>
> >> Jake, do you want to file the ticket or I can do it?
> >>
> >> --Mark
> >>
> >> On Mon, Aug 14, 2017 at 12:42 PM, Jacob Barrett <jbarr...@pivotal.io>
> >> wrote:
> >>
> >>> Well, I am not seeing any -1 votes for this switch. Let's make the
> >> change.
> >>>
> >>> Any takers for following up with Inra to make this go?
> >>>
> >>> On Mon, Aug 7, 2017 at 6:49 PM Jacob Barrett <jbarr...@pivotal.io>
> >> wrote:
> >>>
> >>>> +1 for Gitbox
> >>>>
> >>>> This will greatly simplify the workflow committers go through with
> pull
> >>>> requests from the community. It will also allow us to close out pulls
> >>> that
> >>>> go dark. On our local repos we would really have no need to ever
> >> include
> >>>> the apache repo so it reduces the number of remotes we need to track.
> >>>>
> >>>> -Jake
> >>>>
> >>>> Sent from my iPhone
> >>>>
> >>>>> On Aug 7, 2017, at 6:09 PM, Roman Shaposhnik <ro...@shaposhnik.org>
> >>>> wrote:
> >>>>>
> >>>>> Hi!
> >>>>>
> >>>>> it has just come to my attention that Gitbox at ASF
> >>>>> has been enabling full GitHub workflow (with being
> >>>>> able to click Merge this PR button, etc.) for quite
> >>>>> some time.
> >>>>>
> >>>>> This basically allows a project to have GH as a R/W
> >>>>> repo as opposed to R/O mirror of what we all currnently
> >>>>> have: https://gitbox.apache.org/repos/asf
> >>>>>
> >>>>> Personally I'm not sure I like GH workflow all that much,
> >>>>> but if there's interest -- you can opt-in into Gitbox. Once
> >>>>> you do -- your source of truth moves to GH. You can't
> >>>>> have it both ways with git-wip-us.apache.org and Gitbox.
> >>>>>
> >>>>> Thanks,
> >>>>> Roman.
> >>>>
> >>>
> >>
>


Re: Gitbox enables the full GitHub workflow

2017-08-14 Thread Mark Bretl
Since we have people wanting this and need a small experiment group to
blaze the trail for us, I think the geode-native would be a good choice
since it has active PRs and commits. Looks like the process to migrate from
Git@ASF to GitHub is to create an INFRA ticket with type 'Gitbox Request'.

Jake, do you want to file the ticket or I can do it?

--Mark

On Mon, Aug 14, 2017 at 12:42 PM, Jacob Barrett  wrote:

> Well, I am not seeing any -1 votes for this switch. Let's make the change.
>
> Any takers for following up with Inra to make this go?
>
> On Mon, Aug 7, 2017 at 6:49 PM Jacob Barrett  wrote:
>
> > +1 for Gitbox
> >
> > This will greatly simplify the workflow committers go through with pull
> > requests from the community. It will also allow us to close out pulls
> that
> > go dark. On our local repos we would really have no need to ever include
> > the apache repo so it reduces the number of remotes we need to track.
> >
> > -Jake
> >
> > Sent from my iPhone
> >
> > > On Aug 7, 2017, at 6:09 PM, Roman Shaposhnik 
> > wrote:
> > >
> > > Hi!
> > >
> > > it has just come to my attention that Gitbox at ASF
> > > has been enabling full GitHub workflow (with being
> > > able to click Merge this PR button, etc.) for quite
> > > some time.
> > >
> > > This basically allows a project to have GH as a R/W
> > > repo as opposed to R/O mirror of what we all currnently
> > > have: https://gitbox.apache.org/repos/asf
> > >
> > > Personally I'm not sure I like GH workflow all that much,
> > > but if there's interest -- you can opt-in into Gitbox. Once
> > > you do -- your source of truth moves to GH. You can't
> > > have it both ways with git-wip-us.apache.org and Gitbox.
> > >
> > > Thanks,
> > > Roman.
> >
>


Re: BCSnapshotDUnitTest failing

2017-08-11 Thread Mark Bretl
Hi Kirk,

There is no 'pivotalgf-assembly' project in Geode. Looks like it is part of
a different distribution. ;)

--Mark

On Fri, Aug 11, 2017 at 4:09 PM, Kirk Lund  wrote:

> BCSnapshotDUnitTest seems to be failing intermittently(?) on develop.
>
> :pivotalgf-assembly:distributedTest
>
> org.apache.geode.BCSnapshotDUnitTest > testSnapshot[0] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.BCSnapshotDUnitTest$1.run in VM 0 running on Host
> 3dfb24d73711 with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:387)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:357)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:302)
> at
> org.apache.geode.BCSnapshotDUnitTest.validateOldSnapshot(
> BCSnapshotDUnitTest.java:103)
> at
> org.apache.geode.BCSnapshotDUnitTest.testSnapshot(
> BCSnapshotDUnitTest.java:95)
>
> Caused by:
> java.io.FileNotFoundException: No snapshot files found in
> /tmp/build/ae3c03f4/gemfire/closed/pivotalgf-assembly/
> build/distributedTest437/diskDir/disk-1/bcCacheSnapshotDir
>
> 14 tests completed, 1 failed, 1 skipped
> :pivotalgf-assembly:distributedTest FAILED
>


Re: PdxInitializationException: PDX registry could not be initialized

2017-08-10 Thread Mark Bretl
+ user

--Mark

On Thu, Aug 10, 2017 at 4:12 PM, Aashita Sharma <
aashitasha...@yahoo.co.in.invalid> wrote:

> Hello Team,
>
> We recently got whole gemfire bounced, and every region lost its data.
>
>
>
> Later, we were told to populate data to every region through code. Now
> while populating we got following error:
>
>
>
> PdxInitializationException: PDX registry
> could not be initialized
>
>
>
> It is occurring for all regions.
>
>
>
> Request you to please help me understand what it actually means and how
> should I avoid it to occur in future whenever bouncing of server happens.
>
>
>
>  Regards,  Aashita


Re: Request for Jenkins config ability

2017-08-10 Thread Mark Bretl
Hi Jens,

Skillz have been given.

Let me know if you have any issues,

--Mark

On Thu, Aug 10, 2017 at 10:46 AM, Jens Deppe  wrote:

> Hi,
>
> I'd like to request the ability to make Jenkins config changes for Geode
> builds; I want to start implementing parallel dockerized dunit tests.
>
> Could someone with the appropriate skillz set me up please?
>
> Thanks
> --Jens
>


Re: [DRAFT] Geode Board Report August 2017

2017-08-09 Thread Mark Bretl
Looks good to me. Thanks Dan for taking the time to create the draft.

If there are no issues, then I will post this EOD PST.

--Mark

On Mon, Aug 7, 2017 at 2:04 PM, Dan Smith  wrote:

> Hi folks,
>
> Please review the below draft for our report to the board for this past
> quarter and offer corrections. As Mark mentioned, we need to submit the
> draft this Wednesday.
>
> Thanks!
> -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 processing.
>
> ## Issues:
>
> - There are no issues requiring board attention at this time.
>
> ## Activity:
>
> - Geode 1.2 was released with over 300 tickets resolved, including
>   - Integration with Apache Lucene is no longer experimental
>   - A built in partition resolver
>   - Examples bundled with the distribution
> - ApacheCon presentation - Building an IoT platform with Apache Apollo and
> Apache Geode by Swapnil Bawaskar
>
> ## Health report:
>
> - We’re continuing to work on attracting new contributors and making it
> easier
> to participate in the community.
> - Mailing list activity is healthy.
> - Work has started towards the next Geode release, 1.3.0 including
> development of a new client/server protocol.
>
> ## PMC changes:
>
> - Currently 36 PMC members (+1 since last report)
> - Joey McAllister was added to the PMC on Mon Jul 24 2017
>
> ## Committer base changes:
>
> - Currently 81 committers (+2 since last report)
> - Joey McAllister was added as a committer on Tue Jul 25 2017
> - Deepak Dixit was added as a committer on Thu Jul 13 2017
>
> ## Releases:
>
> - 1.2.0 was released on Wed July 17th 2017
>
> ## Mailing list activity:
>
> - Mailing lists remain active and we’re seeing continued growth in
> subscriber
> counts.  Mailing list traffic on dev went down because we redirected jira
> traffic to iss...@geode.apache.org, but the combined activity increased.
>
> - dev@geode.apache.org:
>  - 174 subscribers (up 10 in the last 3 months)
>  - 4264 emails sent in the past 3 months, 7166 in the previous cycle
>
> - iss...@geode.apache.org:
>  - 56 subscribers (up 1 in the last 3 months)
>  - 3183 emails sent in the past 3 months, 0 in the previous cycle
>
> - u...@geode.apache.org:
>  - 232 subscribers (up 12 in the last 3 months)
>  - 286 emails sent in the past 3 months, 202 in the previous cycle
>
> ## JIRA activity:
>
> - 513 JIRA tickets created in the last 3 months
> - 351 JIRA tickets closed/resolved in the last 3 months
>


Re: Gitbox enables the full GitHub workflow

2017-08-08 Thread Mark Bretl
+1 for Gitbox

I have been watching threads on INFRA list and been waiting to see when a
good time would be to introduce the idea to the community. The Gitbox
project has been going since the end of 2016 and looks as though it might
be ready now as INFRA has begun moving some of their repositories to
GitHub. We still need to 'apply' by submitting a ticket to INFRA and wait
for approval, INFRA could still deny the move.

Advantages:
- GitHub PRs are fully functional (something which stopped us earlier)
- Provides ability to align committer and non-committer workflows
- Removing mirror from Git at Apache to GitHub and thus removing delay in
sync

Disadvantages:
- Permission mapping is configured on id.apache.org (need to set GitHub ID)

I can't think of many disadvantages to moving to GitBox.

--Mark


On Tue, Aug 8, 2017 at 10:56 AM, Dan Smith  wrote:

> I'm in favor of switching to gitbox. We're already getting pretty much all
> contributions from non-committers coming in as pull requests so we might as
> well make it easier for us to manage things in github.
>
> -Dan
>
> On Tue, Aug 8, 2017 at 8:57 AM, Kirk Lund  wrote:
>
> > One thing that's given me trouble is that the mirroring of ASF git (for
> > Apache Geode) to github can have a lengthy delay. In other words, after I
> > commit to ASF git, it's not uncommon for my commit to not show up in the
> > GitHub mirror right away and I've seen this delay take an hour.
> >
> > On Mon, Aug 7, 2017 at 6:09 PM, Roman Shaposhnik 
> > wrote:
> >
> > > Hi!
> > >
> > > it has just come to my attention that Gitbox at ASF
> > > has been enabling full GitHub workflow (with being
> > > able to click Merge this PR button, etc.) for quite
> > > some time.
> > >
> > > This basically allows a project to have GH as a R/W
> > > repo as opposed to R/O mirror of what we all currnently
> > > have: https://gitbox.apache.org/repos/asf
> > >
> > > Personally I'm not sure I like GH workflow all that much,
> > > but if there's interest -- you can opt-in into Gitbox. Once
> > > you do -- your source of truth moves to GH. You can't
> > > have it both ways with git-wip-us.apache.org and Gitbox.
> > >
> > > Thanks,
> > > Roman.
> > >
> >
>


Volunteer Request: Write Draft Board Report For August 2017

2017-08-04 Thread Mark Bretl
Hi Everyone,

We are scheduled to report to the Apache board for this months board
meeting on August 16 and need to submit a report by Wednesday, August 9th.
Goal would be to have a initial draft for the community by Tuesday.

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

Previous Reports: https://whimsy.apache.org/board/minutes/Geode.html

Would anyone like to volunteer to write a draft of the report?

Best regards,

--Mark


Re: Revert gradle upgrade

2017-07-25 Thread Mark Bretl
Now that we have 1.2.0 out the door, would I be able to get someone to
verify my fixes from those who were having trouble with Gradle 3.4.1 in
their IDE?

Thanks,

--Mark

On Wed, Jun 14, 2017 at 5:08 PM, Mark Bretl <mbr...@apache.org> wrote:

> I think I figured it out.
>
> Here is what I did:
> Fix was to declare the version of Antlr in the dependencies{} because if
> no version is set, the ANTLR plugin would default to 2.7.7. This was
> causing issues since the ANTLR plugin was trying to 'change' the version
> after dependency resolution for its configuration.
>
> I successfully tested imported into Eclipse, so I have checked in the
> changes on the feature/gradle-3.4.1 branch. Would others take some time to
> see if it works for them now?
>
> --Mark
>
> On Tue, May 9, 2017 at 10:51 AM, Udo Kohlmeyer <ukohlme...@pivotal.io>
> wrote:
>
>> I think we have to check the ANTLR plugin to understand it's
>> requirements..
>>
>> maybe there is a newer plugin version for ANTLR
>>
>>
>> On 5/9/17 10:00, Kirk Lund wrote:
>>
>>> I've reverted the upgrade to gradle 3.4.1. I also went ahead and created
>>> a
>>> branch that repeats the upgrade:
>>>
>>> feature/gradle-3.4.1
>>>
>>> Feel free to experiment with that branch.
>>>
>>> On Tue, May 9, 2017 at 9:53 AM, Kirk Lund <kl...@apache.org> wrote:
>>>
>>> I'll go ahead and revert the upgrade. Hopefully we can eventually find
>>>> the
>>>> cause so we can repeat the upgrade.
>>>>
>>>> On Mon, May 8, 2017 at 4:19 PM, Bruce Schuchardt <
>>>> bschucha...@pivotal.io>
>>>> wrote:
>>>>
>>>> The "eclipse" target fails, too.
>>>>>
>>>>> Le 5/8/2017 à 3:32 PM, Kirk Lund a écrit :
>>>>>
>>>>> I want to revert the gradle upgrade because it breaks IntelliJ and the
>>>>>> idea
>>>>>> gradle task. Please let me know if you have a problem with this.
>>>>>>
>>>>>> PS: Please be prepared to help me if you vote against me reverting the
>>>>>> upgrade ;) I really want to be able to work again. Thanks!
>>>>>>
>>>>>>
>>>>>>
>>
>


New Committer And PMC Member: Joey McAllister

2017-07-25 Thread Mark Bretl
The Apache Geode Project Management Committee has invited Joey McAllister to
be committer on the project and join the Geode PMC. We are pleased to
announce he has accepted.

Please join me in welcoming Joey!

Best regards,

Mark
On behalf of the Apache Geode PMC


New Committer: Deepak Dixit

2017-07-14 Thread Mark Bretl
The Apache Geode Project Management Committee has invited Deepak Dixit to
be committer on the project. We are pleased to announce he has accepted.

Please join me in welcoming Deepak!

Thanks,

Mark
On behalf of the Apache Geode PMC


Re: geode-3153 waiting on reviews

2017-07-03 Thread Mark Bretl
Hi Barry,

What Geode versions are these related to?

Please only use Geode versions when discussing issues on the community
lists.

Thanks,

--Mark

On Mon, Jul 3, 2017 at 6:26 PM Barry Oglesby  wrote:

> Bruce,
>
> Here is what I am seeing in my test (same one I sent you).
>
> 904 server -> 823 client:
>
> Before writing to stream: Client Message Dispatcher for
> 192.168.2.4(client:78763:loner):49721:b274160b:client(version:GFE 8.1):
> ClientUpdateMessageImpl.getGFE70Message membershipIdLength=39;
> membershipId=[4, -64, -88, 2, 4, 0, 0, 4, 3, 5, 10, 87, 0, 1, 57, 87, 0, 4,
> 112, 101, 101, 114, -80, 114, 25, 102, 117, -114, -43, -72, -98, -85, -124,
> -126, 97, -21, -116, 115, 0]
>
> Being written to stream: Client Message Dispatcher for
> 192.168.2.4(client:78763:loner):49721:b274160b:client(version:GFE 8.1):
> EventID.toData writing membershipIdLength=39; membershipId=[4, -64, -88, 2,
> 4, 0, 0, 4, 3, 5, 10, 87, 0, 1, 57, 87, 0, 4, 112, 101, 101, 114, -80, 114,
> 25, 102, 117, -114, -43, -72, -98, -85, -124, -126, 97, -21, -116, 115, 0]
>
> 91 server -> 823 client:
>
> Before writing to stream: Client Message Dispatcher for
> 192.168.2.4(client:78763:loner):49721:b274160b:client(version:GFE 8.1):
> ClientUpdateMessageImpl.getGFE70Message membershipIdLength=39;
> membershipId=[4, -64, -88, 2, 4, 0, 0, 4, 3, 5, 10, 87, 0, 1, 57, 87, 0, 4,
> 112, 101, 101, 114, -80, 114, 25, 102, 117, -114, -43, -72, -98, -85, -124,
> -126, 97, -21, -116, 115, 0]
>
> Being written to stream: Client Message Dispatcher for
> 192.168.2.4(client:78763:loner):49721:b274160b:client(version:GFE 8.1):
> EventID.toData writing membershipIdLength=22; membershipId=[4, -64, -88, 2,
> 4, 0, 0, 4, 3, 5, 10, 87, 0, 1, 57, 87, 0, 4, 112, 101, 101, 114]
>
> In the 904 case, the bytes in the original membership id are written to the
> stream. In the 91 case, the last 17 bytes are removed before the membership
> id is written to the stream.
>
>
> Thanks,
> Barry Oglesby
>
>
> On Mon, Jul 3, 2017 at 1:14 PM, Bruce Schuchardt 
> wrote:
>
> > I've checked in the fix for geode-3153, though Barry said he may still be
> > seeing trouble with it.  I plan to get together with him on-line
> wednesday
> > morning, if possible, to step through his test & verify if the problem
> > still exists.
> >
> > I've also pushed the commit to release/1.2.0
> >
> >
> >
> > On 7/1/17 8:54 AM, Bruce Schuchardt wrote:
> >
> >> This is a 1.2.0 blocker.  It's passed precheckin and new
> >> backward-compatibility unit tests and the reviewboard code review has no
> >> outstanding issues.  I'd like to get a shipIt or two & I'll push the
> >> changes to develop and release/1.2.0.
> >>
> >> https://reviews.apache.org/r/60570/
> >>
> >>
> >
>


Re: Review Request 60142: GEODE-3071: Provide capability to parallelize distributedTests

2017-06-16 Thread Mark Bretl

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


Ship it!




Excellent work Jens! Only issue I see is to add Apache license to docker.gradle.

- Mark Bretl


On June 15, 2017, 5:59 p.m., Jens Deppe wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/60142/
> ---
> 
> (Updated June 15, 2017, 5:59 p.m.)
> 
> 
> Review request for geode, Anthony Baker, Mark Bretl, and Dan Smith.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> Herewith the ability to leverage Gradle's parallel test execution
> capability to run dunits in parallel. This is combined with launching
> tests in Docker containers to provide process, network and filesystem
> isolation. Depending on the size of your system, this can speed up
> running the distributedTest task 2-5 times.
> 
> The capability is enabled by launching gradle with '-PparallelDunit'
> 
> Tunables, enabled as gradle parametrs (-P option) are:
> 
> - dunitDockerImage: The docker image which will be used to launch
>   tests. The image must have the JAVA_HOME environment variable set. The
>   image must be pulled locally before starting the tests.
> - dunitParallelForks: The number of parallel docker containers to be
>   launched.
> - dunitDockerUser: The docker user which will run the tests. Because of
>   the way that the containers map the build directory into them, the
>   test artifacts, will be written with this user id. By default this is
>   'root'.
> 
> Remove debug println
> 
> NOTE: There are problems running this on MacOS which will require a bit more 
> work.
> 
> 
> Diffs
> -
> 
>   build.gradle ec6b920c825491030120e99d288067d476d1fdcb 
>   gradle.properties ca79a3816bffa56e412d82dd570f1e0e445592be 
>   gradle/docker.gradle PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/60142/diff/1/
> 
> 
> Testing
> ---
> 
> Manual test on linux
> 
> 
> Thanks,
> 
> Jens Deppe
> 
>



Re: Revert gradle upgrade

2017-06-14 Thread Mark Bretl
I think I figured it out.

Here is what I did:
Fix was to declare the version of Antlr in the dependencies{} because if no
version is set, the ANTLR plugin would default to 2.7.7. This was causing
issues since the ANTLR plugin was trying to 'change' the version after
dependency resolution for its configuration.

I successfully tested imported into Eclipse, so I have checked in the
changes on the feature/gradle-3.4.1 branch. Would others take some time to
see if it works for them now?

--Mark

On Tue, May 9, 2017 at 10:51 AM, Udo Kohlmeyer 
wrote:

> I think we have to check the ANTLR plugin to understand it's requirements..
>
> maybe there is a newer plugin version for ANTLR
>
>
> On 5/9/17 10:00, Kirk Lund wrote:
>
>> I've reverted the upgrade to gradle 3.4.1. I also went ahead and created a
>> branch that repeats the upgrade:
>>
>> feature/gradle-3.4.1
>>
>> Feel free to experiment with that branch.
>>
>> On Tue, May 9, 2017 at 9:53 AM, Kirk Lund  wrote:
>>
>> I'll go ahead and revert the upgrade. Hopefully we can eventually find the
>>> cause so we can repeat the upgrade.
>>>
>>> On Mon, May 8, 2017 at 4:19 PM, Bruce Schuchardt >> >
>>> wrote:
>>>
>>> The "eclipse" target fails, too.

 Le 5/8/2017 à 3:32 PM, Kirk Lund a écrit :

 I want to revert the gradle upgrade because it breaks IntelliJ and the
> idea
> gradle task. Please let me know if you have a problem with this.
>
> PS: Please be prepared to help me if you vote against me reverting the
> upgrade ;) I really want to be able to work again. Thanks!
>
>
>
>


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

2017-06-13 Thread Mark Bretl
Done

--Mark

On Tue, Jun 13, 2017 at 9:58 AM, Kirk Lund  wrote:

> Can someone with Jenkins permissions please excluded mesos2 from being used
> for our nightly builds?
>
> ERROR: JAVA_HOME is set to an invalid directory: /home/jenkins/tools/java/
> latest1.8
>
> -- Forwarded message --
> From: Apache Jenkins Server 
> Date: Mon, Jun 12, 2017 at 8:42 PM
> Subject: Build failed in Jenkins: Geode-nightly #865
> To: dev@geode.apache.org, kmil...@pivotal.io, jstew...@pivotal.io,
> dbar...@pivotal.io, kl...@pivotal.io, kh...@apache.org, n...@pivotal.io,
> bschucha...@pivotal.io
>
>
> See  redirect?page=changes>
>
> Changes:
>
> [jiliao] GEODE-2925: add target for resource operation for finer grained
> security
>
> [dbarnes] Update geode-book README instructions
>
> [klund] GEODE-290: Remove deprecated methods from launcher classes
>
> [jiliao] GEODE-2928: get rid of the isGfshVM static variable
>
> [jiliao] GEODE-2928: get rid of the isGfshVM static variable - fix merge
> issues
>
> [nnag] GEODE-3066: Test tweaks to stabilize it.
>
> [jstewart] GEODE-3048: Introduce a rule to identify tests that require
> GEODE_HOME
>
> [klund] GEODE-3068: fix alphabetic ordering
>
> --
> Started by timer
> [EnvInject] - Loading node environment variables.
> Building remotely on mesos2 (mesos s390x) in workspace <
> https://builds.apache.org/job/Geode-nightly/ws/>
>  > git rev-parse --is-inside-work-tree # timeout=10
> Fetching changes from the remote Git repository
>  > git config remote.origin.url https://git-wip-us.apache.org/
> repos/asf/geode.git # timeout=10
> Fetching upstream changes from https://git-wip-us.apache.org/
> repos/asf/geode.git
>  > git --version # timeout=10
>  > git fetch --tags --progress https://git-wip-us.apache.org/
> repos/asf/geode.git +refs/heads/*:refs/remotes/origin/*
>  > git rev-parse refs/remotes/origin/develop^{commit} # timeout=10
>  > git rev-parse refs/remotes/origin/origin/develop^{commit} # timeout=10
> Checking out Revision 65471c1174df161c46237f87145d81d27a1663a9
> (refs/remotes/origin/develop)
>  > git config core.sparsecheckout # timeout=10
>  > git checkout -f 65471c1174df161c46237f87145d81d27a1663a9
>  > git branch -a -v --no-abbrev # timeout=10
>  > git branch -D develop # timeout=10
>  > git checkout -b develop 65471c1174df161c46237f87145d81d27a1663a9
>  > git rev-list 122b07afde7cd56898fae354fadc78fdd5dc721d # timeout=10
> [Geode-nightly] $ /bin/bash -xe /tmp/hudson4018735290081826255.sh
> + git clean -d -f gemfire-pulse/src/main/resources/
> [Gradle] - Launching build.
> [Geode-nightly] $ 
> --no-daemon clean precheckin distTar distZip uploadArchives -xflakyTest
>
> ERROR: JAVA_HOME is set to an invalid directory: /home/jenkins/tools/java/
> latest1.8
>
> Please set the JAVA_HOME variable in your environment to match the
> location of your Java installation.
>
> Build step 'Invoke Gradle script' changed build result to FAILURE
> Build step 'Invoke Gradle script' marked build as failure
> Archiving artifacts
> Recording test results
> ERROR: Step ?Publish JUnit test result report? failed: No test report files
> were found. Configuration error?
> Not sending mail to unregistered user ukohlme...@pivotal.io
> Not sending mail to unregistered user huyn...@gmail.com
> Not sending mail to unregistered user jil...@pivotal.io
>


Re: git commit message guidelines

2017-06-09 Thread Mark Bretl
Hey Kirk,

Found it on the wiki,
https://cwiki.apache.org/confluence/display/GEODE/Commit+Message+Format

--Mark

On Fri, Jun 9, 2017 at 11:10 AM, Kirk Lund  wrote:

> Do we have our git commit message guidelines saved or posted somewhere? I'm
> looking at a PR with a VERY long 1st line.
>


Re: [DISCUSS] Using Pull Requests over Review Board

2017-06-08 Thread Mark Bretl
I like the functionality we get with GitHub, including the Travis CI
integration.

Do we have a proposed workflow change for committers?

--Mark

On Thu, Jun 8, 2017 at 11:20 AM, Jacob Barrett  wrote:

> Some more fuel on this fire... PR's get checked against Travis CI
> automatically and the results show up in the PR. This is a good safety
> check even for committers before merging their branch into the development
> branch.
>
> -Jake
>


Re: What to do with the geode-spark-connector

2017-05-25 Thread Mark Bretl
I have similar thoughts as Anthony on this issue. No matter if it is a
separate repo or branch I think it will be left behind.

I think the bigger question is does this community want to continue to
support the connector?

--Mark


On Thu, May 25, 2017 at 8:34 AM Ernest Burghardt 
wrote:

> +1 on A
>
> On Thu, May 25, 2017 at 8:21 AM, Michael William Dodge 
> wrote:
>
> > +1 for A
> >
> > > On 24 May, 2017, at 21:30, Jared Stewart  wrote:
> > >
> > > +1 for A
> > >
> > > On May 24, 2017 6:48 PM, "Kirk Lund"  wrote:
> > >
> > >> +1 for A
> > >>
> > >> On Wed, May 24, 2017 at 5:50 PM, Jianxia Chen 
> wrote:
> > >>
> > >>> I prefer option A: Move it into it's own repository, with it's own
> > >> release
> > >>> cycle.
> > >>>
> > >>> On Wed, May 24, 2017 at 5:17 PM, Dan Smith 
> wrote:
> > >>>
> >  Our geode-spark-connector needs some work. It's currently building
> > >>> against
> >  geode 1.0.0-incubating, because it has it's own separate build
> > process.
> >  It's also somewhat out of date, we're building against spark 1.3. Is
> > >>> anyone
> >  actually using the spark connector?
> > 
> >  I think we need to get the spark connector out of the main geode
> repo
> > >>> since
> >  people are currently modifying code in the connector without even
> > >>> compiling
> >  it, since it's not linked into the gradle build.
> > 
> >  What do the geode devs think we should do with the
> > >> geode-spark-connector?
> > 
> >  A) Move it into it's own repository, with it's own release cycle
> >  B) Delete it
> >  C) Other??
> > 
> >  -Dan
> > 
> > >>>
> > >>
> >
> >
>


Re: Apache TLP Website Link Checks

2017-05-16 Thread Mark Bretl
When I searched for 'event' on the source of the tool, [1], I found the
following page, [2], with more event information.

However, looking at the code, it is searching for: 'apache.org/events/'. So
we can either create the link as text or use the image as a link.

--Mark

[1]
https://gitbox.apache.org/repos/asf?p=whimsy.git;a=blob_plain;f=tools/site-scan.rb;hb=HEAD
[2] http://www.apache.org/events/README.txt


On Tue, May 16, 2017 at 4:45 PM, Joey McAllister <jmcallis...@pivotal.io>
wrote:

> Hi Mark,
>
> I think I can swing that.
>
> It's kind of hard to tell what the requirement for an "Events" link is. The
> link-checker you point to links out to a "Required Links" page (
> https://www.apache.org/foundation/marks/pmcs#navigation), but there's no
> mention of "Events" on there.
>
> I *think* we just need a link to https://www.apache.org/events/ in the
> "Apache" section of our website footer. Does that sound right to you? Or,
> does anyone else in the community know whether this would suffice?
>
> Thanks!
> Joey
>
>
>
> On Tue, May 16, 2017 at 4:10 PM Mark Bretl <mbr...@apache.org> wrote:
>
> > Hi,
> >
> > ASF has created a new tool for scanning TLP sites for compliance and
> other
> > requests. The new tool is located at [1], with our own Geode report at
> [2].
> > The report looks good, with only one missing requirement of an Events
> page.
> >
> > Would someone with web skills be able to update our site?
> >
> > Best regards,
> >
> > --Mark
> >
> > [1] https://whimsy.apache.org/site
> > [2] https://whimsy.apache.org/site/project/geode
> >
>


Apache TLP Website Link Checks

2017-05-16 Thread Mark Bretl
Hi,

ASF has created a new tool for scanning TLP sites for compliance and other
requests. The new tool is located at [1], with our own Geode report at [2].
The report looks good, with only one missing requirement of an Events page.

Would someone with web skills be able to update our site?

Best regards,

--Mark

[1] https://whimsy.apache.org/site
[2] https://whimsy.apache.org/site/project/geode


Re: Problems in the gradle idea generated project

2017-05-16 Thread Mark Bretl
Yes, Eclipse can import Gradle projects through the Eclipse Buildship,
https://projects.eclipse.org/projects/tools.buildship. I have not tested
with Geode for verification it can handle some the custom tasks we have.

I think it may be time to not use the Eclipse or Idea plugins from Gradle.
The Gradle plugins came first, however, I think both IDEA and Eclipse have
both surpassed the level of functionality we are getting with the Gradle
plugins.

--Mark

On Tue, May 16, 2017 at 3:13 PM, Bruce Schuchardt 
wrote:

> I was refering to the problem introduced by the newer version of gradle.
> I also see Kirk's problem with Idea projects generated by gradle if I try
> to use them.  Should we just get rid of Idea project generation?
>
>
> Le 5/16/2017 à 3:11 PM, Bruce Schuchardt a écrit :
>
>> Yes, just import the gradle project, though I think the same problem
>> exists for eclipse project generation.  Does eclipse have the ability to
>> import gradle projects?
>>
>> Le 5/16/2017 à 3:03 PM, Dan Smith a écrit :
>>
>>> I don't think you actually need to use the gradle idea plugin - I think
>>> that's less up to date than the intellij's support for gradle. Just
>>> import
>>> the project as a gradle project in intellij.
>>>
>>> -Dan
>>>
>>> On Tue, May 16, 2017 at 2:52 PM, Kirk Lund  wrote:
>>>
>>> If I use the idea plugin to generate an IntelliJ project for Geode:

 $ ./gradlew idea

 ...the resulting IntelliJ project contains "5 Problems" involving the
 extensions modules:

 *Module geode-modules-session: invalid item
 'extensions/geode-modules-session-internal' in the dependencies list*
 *Module geode-modules-session: invalid item 'extensions/geode-modules'
 in
 the dependencies list*
 *Module geode-modules-session-internal: invalid item
 'extensions/geode-modules' in the dependencies list*
 *Module geode-modules-tomcat7: invalid item 'extensions/geode-modules'
 in
 the dependencies list*
 *Module geode-modules-tomcat8: invalid item 'extensions/geode-modules'
 in
 the dependencies list*

 This looks like we have some quirk or minor problem in our gradle files
 that doesn't perfectly translate to an IntelliJ project. Any ideas how
 to
 fix the above problems?


>>
>


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

2017-05-10 Thread Mark Bretl
Thanks Anthony! This is great.

I will follow up with infra about our stats on the issues mailing list, I
think you are right about it being something with configuration.

--Mark

On Tue, May 9, 2017 at 4:51 PM, Dan Smith <dsm...@pivotal.io> wrote:

> +1 - Thanks for taking this on Anthony!
>
> -Dan
>
> On Tue, May 9, 2017 at 4:47 PM, Anthony Baker <aba...@pivotal.io> wrote:
>
> >
> > Here’s a rough draft, please review and comment:
> >
> > (@Mark, I noticed that issues@geode has 0 emails.  Is that a
> > configuration issue?)
> >
> > ## 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:
> >  - The Geode PMC issued CVE-2017-5649 and released v1.1.1 to address this
> > vulnerability.
> >  - The geode-examples have been improved significantly to make it easier
> > to add new examples and provide a better learning experience.
> >  - The geode-native source and documentation has undergone significant
> > changes to prepare it for inclusion in a Geode release.
> >  - The community has discussed a number of new proposals on
> > modularization, binary protocol, redis adapter, class loading, and
> > finer-grained security.
> >
> > ## Health report:
> >  - We’re continuing to work on attracting new contributors and making it
> > easier to participate in the community.
> >  - Mailing list activity is healthy and discussions are productive.
> >  - Work is progressing towards the next Geode release, 1.2.0.
> >
> > ## PMC changes:
> >
> >  - Currently 35 PMC members.
> >  - New PMC members:
> > - Jacob Barrett was added to the PMC on Mon May 8 2017
> > - Ernest Burghardt was added to the PMC on Mon Mar 20 2017
> > - Jared Stewart was added to the PMC on Sun Feb 12 2017
> >
> > ## Committer base changes:
> >
> >  - Currently 79 committers.
> >  - Ernest Burghardt was added as a committer on Tue Mar 21 2017
> >
> > ## Releases:
> >
> > - 1.1.1 was released on Sat Apr 1 2017
> > - 1.1.0 was released on Wed Feb 15 2017
> >
> > ## Mailing list activity:
> >
> >  - Mailing lists remain active and we’re seeing continued growth in
> > subscriber counts.  The dev@geode list in particular is highly active.
> >
> >  - dev@geode.apache.org:
> > - 159 subscribers (up 3 in the last 3 months):
> > - 7550 emails sent to list (4317 in previous quarter)
> >
> >  - iss...@geode.apache.org:
> > - 55 subscribers (down -1 in the last 3 months):
> > - 0 emails sent to list (1042 in previous quarter)
> >
> >  - u...@geode.apache.org:
> > - 218 subscribers (up 12 in the last 3 months):
> > - 215 emails sent to list (305 in previous quarter)
> >
> > ## JIRA activity:
> >
> >  - 461 JIRA tickets created in the last 3 months
> >  - 327 JIRA tickets closed/resolved in the last 3 months
> >
> > Anthony
> >
> > > On May 8, 2017, at 9:14 AM, Mark Bretl <mbr...@apache.org> wrote:
> > >
> > > We need to submit a report by Friday and I have not seen any takers to
> > > creating the report. If there are no volunteers, I will create a draft
> on
> > > Wednesday.
> > >
> > > --Mark
> > >
> > > On Thu, Apr 27, 2017 at 12:48 PM, Mark Bretl <mbr...@apache.org>
> wrote:
> > >
> > >> 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

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

2017-05-08 Thread Mark Bretl
We need to submit a report by Friday and I have not seen any takers to
creating the report. If there are no volunteers, I will create a draft on
Wednesday.

--Mark

On Thu, Apr 27, 2017 at 12:48 PM, Mark Bretl <mbr...@apache.org> wrote:

> 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/commit
> tee-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: GEODE-2708: Upgrading Gradle Wrapper to 3.4.1

2017-05-04 Thread Mark Bretl
This is now checked in on Develop.

Happy Building!

--Mark

On Tue, May 2, 2017 at 11:46 AM, Udo Kohlmeyer <ukohlme...@pivotal.io>
wrote:

> +1, so have I
>
>
>
> On 5/2/17 11:09, Jared Stewart wrote:
>
>> +1 I've been running with Gradle 3+ without issues too
>>
>> On May 2, 2017, at 11:04 AM, Anthony Baker <aba...@pivotal.io> wrote:
>>>
>>> +1 I’ve been running against gradle 3+ for awhile now.
>>>
>>> Anthony
>>>
>>> On May 2, 2017, at 10:55 AM, Mark Bretl <mbr...@apache.org> wrote:
>>>>
>>>> I have done testing to upgrade our current Gradle wrapper version from
>>>> 2.14.1 to 3.4.1. There are a couple of warnings during the build,
>>>> however,
>>>> I didn't see anything in a precheckin run that would be an issue.
>>>>
>>>> Anybody have any issues with updating Gradle before releasing 1.2.0?
>>>>
>>>> If there no objections, I will checkin the upgrade changes on Thursday
>>>> EOD
>>>> PST.
>>>>
>>>> --Mark
>>>>
>>>
>


[jira] [Assigned] (GEODE-2708) Update Gradle Wrapper to Gradle 3

2017-05-04 Thread Mark Bretl (JIRA)

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

Mark Bretl reassigned GEODE-2708:
-

Assignee: Mark Bretl

> Update Gradle Wrapper to Gradle 3
> -
>
> Key: GEODE-2708
> URL: https://issues.apache.org/jira/browse/GEODE-2708
> Project: Geode
>  Issue Type: Task
>  Components: build
>Reporter: Galen O'Sullivan
>    Assignee: Mark Bretl
> Fix For: 1.2.0
>
>
> It looks like we're still running on a very old version of Gradle. This may 
> be related to incremental builds not working properly.
> {code}
> $ ./gradlew --version
> 
> Gradle 2.14.1
> 
> Build time:   2016-07-18 06:38:37 UTC
> Revision: d9e2113d9fb05a5caabba61798bdb8dfdca83719
> Groovy:   2.4.4
> Ant:  Apache Ant(TM) version 1.9.6 compiled on June 29 2015
> JVM:  1.8.0_111 (Oracle Corporation 25.111-b14)
> OS:   Mac OS X 10.12.3 x86_64
> $ gradle --version
> 
> Gradle 3.4.1
> 
> Build time:   2017-03-03 19:45:41 UTC
> Revision: 9eb76efdd3d034dc506c719dac2955efb5ff9a93
> Groovy:   2.4.7
> Ant:  Apache Ant(TM) version 1.9.6 compiled on June 29 2015
> JVM:  1.8.0_111 (Oracle Corporation 25.111-b14)
> OS:   Mac OS X 10.12.3 x86_64
> {code}



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


[jira] [Resolved] (GEODE-2708) Update Gradle Wrapper to Gradle 3

2017-05-04 Thread Mark Bretl (JIRA)

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

Mark Bretl resolved GEODE-2708.
---
   Resolution: Fixed
Fix Version/s: 1.2.0

Gradle Wrapper now updated to 3.4.1

> Update Gradle Wrapper to Gradle 3
> -
>
> Key: GEODE-2708
> URL: https://issues.apache.org/jira/browse/GEODE-2708
> Project: Geode
>  Issue Type: Task
>  Components: build
>Reporter: Galen O'Sullivan
>    Assignee: Mark Bretl
> Fix For: 1.2.0
>
>
> It looks like we're still running on a very old version of Gradle. This may 
> be related to incremental builds not working properly.
> {code}
> $ ./gradlew --version
> 
> Gradle 2.14.1
> 
> Build time:   2016-07-18 06:38:37 UTC
> Revision: d9e2113d9fb05a5caabba61798bdb8dfdca83719
> Groovy:   2.4.4
> Ant:  Apache Ant(TM) version 1.9.6 compiled on June 29 2015
> JVM:  1.8.0_111 (Oracle Corporation 25.111-b14)
> OS:   Mac OS X 10.12.3 x86_64
> $ gradle --version
> 
> Gradle 3.4.1
> 
> Build time:   2017-03-03 19:45:41 UTC
> Revision: 9eb76efdd3d034dc506c719dac2955efb5ff9a93
> Groovy:   2.4.7
> Ant:  Apache Ant(TM) version 1.9.6 compiled on June 29 2015
> JVM:  1.8.0_111 (Oracle Corporation 25.111-b14)
> OS:   Mac OS X 10.12.3 x86_64
> {code}



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


GEODE-2708: Upgrading Gradle Wrapper to 3.4.1

2017-05-02 Thread Mark Bretl
I have done testing to upgrade our current Gradle wrapper version from
2.14.1 to 3.4.1. There are a couple of warnings during the build, however,
I didn't see anything in a precheckin run that would be an issue.

Anybody have any issues with updating Gradle before releasing 1.2.0?

If there no objections, I will checkin the upgrade changes on Thursday EOD
PST.

--Mark


  1   2   >