Hi,
Kind reminder. The extended deadline for the RFC review is next Thursday 4th
June.
BR/
Alberto B.
De: Udo Kohlmeyer
Enviado: sábado, 30 de mayo de 2020 2:37
Para: dev@geode.apache.org
Asunto: RE: [DISCUSS] RFC: New option for serial gw sender dispatcher th
Hi all,
I have reported a performance problem of the c++ native client, which appeared
after the modification of the "<" operator of the PdxType class:
https://issues.apache.org/jira/browse/GEODE-8212
I just want to highlight it, just in case someone is facing the same issue.
BR/
Alberto B.
I know this has been brought up multiple times without resolution. I want us
resolve to ban the use of Geode repository for work in progress, feature
branches, or any other branches that are not release or support branches. There
is no reason given the nature of GitHub why you can’t fork the rep
I prefer to share a fork among multiple developers instead of using the
Apache Geode repository.
On Tue, Jun 2, 2020 at 3:42 PM Jacob Barrett wrote:
> I know this has been brought up multiple times without resolution. I want
> us resolve to ban the use of Geode repository for work in progress, f
+1 to avoiding clutter by not using feature branches on the Geode repo.
Sharing your own repo, as Kirk suggests, also works better when
collaborating with folks who aren't committers.
On Tue, Jun 2, 2020 at 4:16 PM Kirk Lund wrote:
> I prefer to share a fork among multiple developers instead of
- We are maintaining feature/GEODE-7665 which is the feature branch for PR
clear work on which multiple developers are working on.
- We are maintaining this in Geode repository.
- All sub-tasks of GEODE-7665 are merged into this feature branch.
- Anyone in the Geode community can work on any subt
While I am not 100% sure, I understand your thoughts here, I am pretty sure I
do. We have already done such work in a branch in a fork (Micrometer work). The
only real gotcha was that there needed to be one person at least as a
collaborator, in case of vacations and such.
All of the things you
I don’t think it is right to make the open source Geode Community to work on my
personal fork
Regards
Naba
-Original Message-
From: Mark Hanson
Sent: Tuesday, June 2, 2020 4:35 PM
To: dev@geode.apache.org
Subject: Re: [DISCUSSION] Stop using the Geode Repository for Feature/WIP
Bran
> On Jun 2, 2020, at 4:40 PM, Nabarun Nag wrote:
>
> I don’t think it is right to make the open source Geode Community to work on
> my personal fork
Why not? I can fork your fork. I can PR to your fork. Its sort of what Git was
made for, no single source repository.
Can you elaborate on w
> On Jun 2, 2020, at 4:29 PM, Nabarun Nag wrote:
>
> - We are maintaining feature/GEODE-7665 which is the feature branch for PR
> clear work on which multiple developers are working on.
> - We are maintaining this in Geode repository.
> - All sub-tasks of GEODE-7665 are merged into this feat
- Unified location, where anyone who wants to work on the feature can find the
feature branch on the geode-repository
- Visibility, the PRs to the geode repository can be viewed by everyone in the
Geode community. Which will not happen if they are raised to my fork.
- Long running feature develo
I agree, I am not justifying the use of repository for small bug fixes etc. or
short term individual tasks
I am justifying why PR clear has a feature branch in the geode repository.
Regards
Naba
-Original Message-
From: Jacob Barrett
Sent: Tuesday, June 2, 2020 4:48 PM
To: dev@geode
> On Jun 2, 2020, at 4:50 PM, Nabarun Nag wrote:
>
> - Unified location, where anyone who wants to work on the feature can find
> the feature branch on the geode-repository
> - Visibility, the PRs to the geode repository can be viewed by everyone in
> the Geode community. Which will not hap
I'm a fan of features on forks! It's fairly simple to make forks accessible to
other folks.
I know this isn't a vote, but I'm a +1 for the concept...
EB
On 6/2/20, 3:42 PM, "Jacob Barrett" wrote:
I know this has been brought up multiple times without resolution. I want
us resolve to ban
14 matches
Mail list logo
