gearpump-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kam Kasravi <>
Subject Re: DISCUSS: Review, and decide whether to accept additional code commit from
Date Wed, 13 Apr 2016 14:26:50 GMT
If we have matching JIRA's I would prefer to import per JIRA and close the JIRA.This makes
it consistent with the apache process. 

    On Tuesday, April 12, 2016 9:17 PM, Sean Zhong <> wrote:

During the waiting of initial code import to Apache, there are 19 PR
committed in old git repo

In this thread, we should DISCUSS whether we should import these 19 PR to
Apache git, which is

We'd like to invite you to review the FAQ and PR list, to raise any
concerns if it exists.

The discussion will open for 72 hours, after the discussion, a VOTE thread
will be called for the importing.

1. How long the transition happens?
We waited for about 28 days. The code commit happens in these past 28 days.

2. How many PR are we talking about?
There are 17 PR covered. Start sha1: d5343681edde427022bf4c225ce602
2a6904ae88, End sha1: 79e15668c6498a54da691626dd2f91bf205d3720

3. Whether they is important fix?
Yes, they fix many bugs and improve the features.

4. Whether these PR have reviews and +1 from initial Apache committers?
Yes, all these PRs have reviews and at least one +1 from Apache initial

5. Whether these code has good code style by Apache process?
Yes. also have code style requirement, which is
consistent with Apache basic requirements.

6. Whether The ICLA are fired for the contributors of these PR?
Yes. All these 17 PR comes from Intel employees, the licensing is covered
by CCLA. The contributors list: Manu, Stanley Xu, Sean Zhong, Huafeng

*Pull requests list:*
GEARPUMP-11, fix code style

GEARPUMP-17, fix KafkaStorage lookup timestamp

GEARPUMP-10: Downgrade netty from Netty 4 to Netty 3.8 cause the OAuth2
authentication failure

GEARPUMP-8, fix "two machines can possibly have same worker id "

GEARPUMP-9, Clean and fix integration test

GEARPUMP-6: show add/remove worker buttons for admin

GEARPUMP-5, Add additional authorization check like checking
user-organization for cloudfoundry OAuth2 Authenticator.

GEARPUMP-3, Define REST API to add/remove worker instances, which allow us
to scale out in YARN

GEARPUMP-2, Define REST API to submit job jar

fix #1988, upgrade akka to akka 2.4.2

fix #2015, do not send AckRequest or LatencyProbe when there is no pending
message in the channel

fix #1943 allow user to config how many executors to use in an application

fix #1641, add exactly-once integration test

fix #1318, fix MinClock not updated fast enough for slow stream

fix #1981, Support OAuth2 Social login

fix #2007, add Java DSL

fix #2002, add akka stream examples



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message