Re: [VOTE] Retire Gearpump

[Vincent Wang]

+1

Jean-Baptiste Onofré 于2018年9月13日周四 下午1:55写道：

> +1
>
> Regards
> JB
>
> On 13/09/2018 07:54, Manu Zhang wrote:
> > Hi all,
> >
> > As per previous discussion
> > <
> https://lists.apache.org/thread.html/77946cfff4557cf10c13c2d35fc165223583e58c2f7705319acabcf4@%3Cdev.gearpump.apache.org%3E
> >,
> > we agree that it would be better for Gearpump to retire from the ASF
> > incubator. Here comes the formal vote.
> >
> > [ ] +1 to retire
> > [ ] -1 not to retire because...
> >
> > Here's my +1.
> >
> > This will be open for at least 72 hours and is a majority vote.
> >
> > Thanks,
> > Manu Zhang
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: Podling Report Reminder - December 2017

[Vincent Wang]

Hi all,

This is the Gearpump podling report. Please review.

Gearpump

 Gearpump is a reactive real-time streaming engine based on the
micro-service Actor model.
 Gearpump has been incubating since 2016-03-08.

 Three most important issues to address in the move towards graduation:

 1. Have frequent release cycles.
 2. Continue to evolve community interest and support.
 3. Keep up with Apache Beam's evolving API.


 - Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
 - None.


 - How has the community developed since the last report?
 - There was a company managed to deploy Gearpump on their secured Hadoop
cluster. They reported some bugs occurred in their environment and
contributed the fixes back to Gearpump community.

 - How has the project developed since the last report?
 - 15 issues created and 9 issues resolved.
 - An official Gearpump docker image was published.
 - Continuous improvements for Gearpump Runner in Apache Beam were made.

 Date of last release:
 2017-07-17


 When were the last committers or PMC members elected?
 No new committers or PMC members elected yet.

 Signed-off-by:

 [ ](gearpump) Jean-Baptiste Onofré
 [ ](gearpump) Andrew Purtell
 [ ](gearpump) Jarek Jarcec Cecho
 [ ](gearpump) Reynold Xin
 [ ](gearpump) Todd Lipcon
 [ ](gearpump) Xuefu Zhang


于2017年11月27日周一 上午11:48写道：

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 20 December 2017, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, December 06).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://wiki.apache.org/incubator/December2017
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

Re: [jira] [Commented] (GEARPUMP-363) Why not synchronize app jar files between active master and standby masters

[Vincent Wang]

Hi Xuetong,

I was on vacation last week and I'm very sorry for the late response.
I think it would be great if we can make jar files highly available in
default mode. But manually distributing jars across masters may not be a
good idea.
If we want to do so, each master should have the knowledge of whether there
are other standby masters, where they are and whether they are active. I
think this is kind of anti-design and not intuitive.

Thanks,
Huafeng

Xuetong Zhu (JIRA) 于2017年11月16日周四 下午4:36写道：

>
> [
> https://issues.apache.org/jira/browse/GEARPUMP-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254950#comment-16254950
> ]
>
> Xuetong Zhu commented on GEARPUMP-363:
> --
>
> Yes, I mean we should make jar files highly available in the cluster mode.
> we could deploy gearpump in same directory of every machine,  then we
> could  upload application jars to same folders of every master machine,
> eventually make jar files highly available.
>
> > Why not synchronize app jar files between active master and standby
> masters
> >
> ---
> >
> > Key: GEARPUMP-363
> > URL: https://issues.apache.org/jira/browse/GEARPUMP-363
> > Project: Apache Gearpump
> >  Issue Type: Wish
> >Reporter: Xuetong Zhu
> >Priority: Minor
> >
> > In addition to HDFS and NFS,  Could we add synchronization jar file
> method, which I think more convenience than the former.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.4.14#64029)
>

Re: [VOTE] Release of Apache Gearpump 0.8.3-incubating, release candidate #1

[Vincent Wang]

+1

Jean-Baptiste Onofré 于2017年6月24日周六 下午2:44写道：

> +1 (binding)
>
> I checked the signatures & checksums, build locally, checked the ASF
> header.
>
> Regards
> JB
>
> On 06/23/2017 08:20 PM, Karol Brejna wrote:
> > Hi Gearpump Community,
> >
> > This is a call for a discussion releasing Apache Gearpump
> > 0.8.4-incubating, release candidate #1, which leitmotiv is Apache Beam
> > integration.
> >
> > The source and binary tarballs, including signatures, digests, etc.
> > can be found at:
> >
> https://dist.apache.org/repos/dist/dev/incubator/gearpump/0.8.4-incubating/RC1/
> >
> > Release artifacts are signed with the key with fingerprint:
> > 3F12 81A2 DB58 0842 5ABA  6962 D8A8 4FBC 0A83 B291
> >
> > The KEYS file is available here:
> > https://dist.apache.org/repos/dist/dev/incubator/gearpump/KEYS
> >
> > The tag to be voted upon is:
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=shortlog;h=refs/tags/0.8.4-RC1
> >
> > The release hash is:
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=commit;h=71132b256b8edbd734839386d8de2731813bd290
> >
> > For information about the contents of this release see:
> > https://issues.apache.org/jira/projects/GEARPUMP/versions/12340225
> >
> > This vote will be open for 72 hours (Monday, April 27, 2017 at 4:00PM
> PST).
> >
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, run the
> > binary artifacts in the binary release and test.
> > Please vote:
> >
> > [ ] +1 Release this package as gearpump-0.8.4
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because because...
> >
> > Thanks,
> > Karol
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: How to add sub graph

[Vincent Wang]

Hi, currently we only exposed the API for replacing a node and adding a sub
graph from dashboard is not supported yet. Can you describe a little about
your application scenarios or requirement?

Thanks,
Huafeng
朱学通 于2017年5月19日周五 下午11:47写道：

> Dear :
>
>
> I find Gearpump Can be add sub graph in document. But I can’t find the way
> to add in web UI. Can someone give me a hand?
>

Re: [jira] [Commented] (GEARPUMP-284) Oauth2 tests fail

[Vincent Wang]

I remember that this UT actually will pass on travis sometimes, does it
fail all the time now?

Thanks,
Huafeng

Karol Brejna (JIRA) 于2017年5月9日周二 下午6:30写道：

>
> [
> https://issues.apache.org/jira/browse/GEARPUMP-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002448#comment-16002448
> ]
>
> Karol Brejna commented on GEARPUMP-284:
> ---
>
>
> From my observation, the test that fails is:
> services/jvm/src/test/scala/org/apache/gearpump/services/security/oauth2/GoogleOAuth2AuthenticatorSpec.scala
>
> The test tries to authenticate against google OAuth server.
>
> The log relevant for the error is:
> {code}
> ExecutorSystemLauncherSpec:^[[0m^[[0m
> - should report success when worker launch the system
> successfully^[[0m^[[0m
> - should report failure when worker refuse to launch the system
> explicitly^[[0m^[[0m
> - should report timeout when trying to start a executor system on worker,
> and worker doesn't response^[[0m^[[0m
> CloudFoundryUAAOAuth2AuthenticatorSpec:^[[0m^[[0m
> - should generate the correct authorization request^[[0m^[[0m
> - should authenticate the authorization code and return the correct
> profile *** FAILED ***^[[0m^[[0m
>   com.github.scribejava.core.exceptions.OAuthException: Response body is
> incorrect. Can't extract a '"access_token"\s*:\s*"(\S*?)"' from this:
> '^M^[[0m^[[0m
> Redirection^M^[[0m^[[0m
> Redirect^M^[[0m^[[0m
> '^[[0m^[[0m
>   at
> com.github.scribejava.core.extractors.OAuth2AccessTokenJsonExtractor.extractParameter(OAuth2AccessTokenJsonExtractor.java:64)^[[0m^[[0m
>   at
> com.github.scribejava.core.extractors.OAuth2AccessTokenJsonExtractor.extract(OAuth2AccessTokenJsonExtractor.java:37)^[[0m^[[0m
>   at
> com.github.scribejava.core.extractors.OAuth2AccessTokenJsonExtractor.extract(OAuth2AccessTokenJsonExtractor.java:12)^[[0m^[[0m
>   at
> com.github.scribejava.core.oauth.OAuth20Service$1.convert(OAuth20Service.java:47)^[[0m^[[0m
>   at
> com.github.scribejava.core.oauth.OAuth20Service$1.convert(OAuth20Service.java:43)^[[0m^[[0m
>   at
> com.github.scribejava.core.model.OAuthRequestAsync$OAuthAsyncCompletionHandler.onCompleted(OAuthRequestAsync.java:104)^[[0m^[[0m
>   at
> com.ning.http.client.AsyncCompletionHandler.onCompleted(AsyncCompletionHandler.java:55)^[[0m^[[0m
>   at
> com.ning.http.client.providers.netty.future.NettyResponseFuture.getContent(NettyResponseFuture.java:177)^[[0m^[[0m
>   at
> com.ning.http.client.providers.netty.future.NettyResponseFuture.done(NettyResponseFuture.java:214)^[[0m^[[0m
>   at
> com.ning.http.client.providers.netty.handler.HttpProtocol.finishUpdate(HttpProtocol.java:194)^[[0m^[[0m
>   ...^[[0m^[[0m
> GoogleOAuth2AuthenticatorSpec:^[[0m^[[0m
> - should generate the correct authorization request^[[0m^[[0m
> - should authenticate the authorization code and return the correct
> profile *** FAILED ***^[[0m^[[0m
>   com.github.scribejava.core.exceptions.OAuthException: Response body is
> incorrect. Can't extract a '"access_token"\s*:\s*"(\S*?)"' from this:
> '^M^[[0m^[[0m
> Redirection^M^[[0m^[[0m
> Redirect^M^[[0m^[[0m
> '^[[0m^[[0m
>   at
> com.github.scribejava.core.extractors.OAuth2AccessTokenJsonExtractor.extractParameter(OAuth2AccessTokenJsonExtractor.java:64)^[[0m^[[0m
>   at
> com.github.scribejava.core.extractors.OAuth2AccessTokenJsonExtractor.extract(OAuth2AccessTokenJsonExtractor.java:37)^[[0m^[[0m
>   at
> com.github.scribejava.core.extractors.OAuth2AccessTokenJsonExtractor.extract(OAuth2AccessTokenJsonExtractor.java:12)^[[0m^[[0m
>   at
> com.github.scribejava.core.oauth.OAuth20Service$1.convert(OAuth20Service.java:47)^[[0m^[[0m
>   at
> com.github.scribejava.core.oauth.OAuth20Service$1.convert(OAuth20Service.java:43)^[[0m^[[0m
> {code}
>
> It looks, like authorize url has moved recently. For me the following
> change worked:
> -  super.authorizeUrl.replace("https://accounts.google.com;, host)
> +  super.authorizeUrl.replace("
> https://accounts.google.com/ManageAccount;, host)
>
> I didn't check the rest of the test (what responses are sent, what secured
> endpoint it tries, etc. But I don't expect much changed there.
>
>
> > Oauth2 tests fail
> > -
> >
> > Key: GEARPUMP-284
> > URL: https://issues.apache.org/jira/browse/GEARPUMP-284
> > Project: Apache Gearpump
> >  Issue Type: Bug
> >  Components: services
> >Affects Versions: 0.8.2
> >Reporter: Karol Brejna
> >Assignee: Karol Brejna
> >   Original Estimate: 6h
> >  Remaining Estimate: 6h
> >
> > Running tests show that oauth2 tests fail.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.15#6346)
>

Re: IntelliJ IDEA licence expired

[Vincent Wang]

Hi Karol, I also noticed that. I tried to renew it but didn't find out how
to do that. Eventually I found that I can get a license using my apache
membership （email account).

Karol Brejna 于2017年5月9日周二 下午4:43写道：

> I've just noticed, that our IntelliJ license for Gearpump has expired.
>
> My license details:
>
> Licensed to: GearPump
> License restriction: For non-commercial open source development only
> Valid through: April 21, 2017
>
> Do you remember how to renew the license with JetBrains?
>
> Regards,
> Karol
>

Re: [jira] [Commented] (GEARPUMP-300) java.io.NotSerializableException official DSL version for Wordcount in java

[Vincent Wang]

Hi Yanghua, can you describe a little about how to reproduce this exception?

yanghua (JIRA) 于2017年4月28日周五 上午8:45写道：

>
> [
> https://issues.apache.org/jira/browse/GEARPUMP-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15987957#comment-15987957
> ]
>
> yanghua commented on GEARPUMP-300:
> --
>
> I try to find the problem, in source code :
> https://github.com/apache/incubator-gearpump/blob/master/streaming/src/main/scala/org/apache/gearpump/streaming/dsl/scalaapi/StreamApp.scala#L94
>  here need a Iterator and will be serialized.
> And in JavaStreamApp it seams if pass a ArrayList‘s instance it will use
> ArrayList's inner Itr(Iterator's implementation),
>
> https://github.com/apache/incubator-gearpump/blob/master/streaming/src/main/scala/org/apache/gearpump/streaming/dsl/javaapi/JavaStreamApp.scala#L36
>  but Itr is not serializable.
>
> > java.io.NotSerializableException official DSL version for Wordcount in
> java
> >
> ---
> >
> > Key: GEARPUMP-300
> > URL: https://issues.apache.org/jira/browse/GEARPUMP-300
> > Project: Apache Gearpump
> >  Issue Type: Bug
> >Reporter: yanghua
> >
> > java.io.NotSerializableException: java.util.ArrayList$Itr
> >   at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
> >   at
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
> >   at
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
> >   at
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
> >   at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
> >   at
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
> >   at
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
> >   at
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
> >   at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
> >   at
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
> >   at
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
> >   at
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
> >   at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
> >   at
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
> >   at
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
> >   at
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
> >   at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
> >   at
> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
> >   at
> akka.serialization.JavaSerializer$$anonfun$toBinary$1.apply$mcV$sp(Serializer.scala:235)
> >   at
> akka.serialization.JavaSerializer$$anonfun$toBinary$1.apply(Serializer.scala:235)
> >   at
> akka.serialization.JavaSerializer$$anonfun$toBinary$1.apply(Serializer.scala:235)
> >   at scala.util.DynamicVariable.withValue(DynamicVariable.scala:58)
> >   at akka.serialization.JavaSerializer.toBinary(Serializer.scala:235)
> >   at
> org.apache.gearpump.cluster.UserConfig.withValue(UserConfig.scala:139)
> >   at
> org.apache.gearpump.streaming.dsl.plan.DataSourceOp.getProcessor(OP.scala:98)
> >   at
> org.apache.gearpump.streaming.dsl.plan.Planner$$anonfun$plan$2.apply(Planner.scala:50)
> >   at
> org.apache.gearpump.streaming.dsl.plan.Planner$$anonfun$plan$2.apply(Planner.scala:50)
> >   at org.apache.gearpump.util.Graph$$anonfun$1.apply(Graph.scala:143)
> >   at org.apache.gearpump.util.Graph$$anonfun$1.apply(Graph.scala:143)
> >   at scala.collection.immutable.List.map(List.scala:277)
> >   at org.apache.gearpump.util.Graph.mapVertex(Graph.scala:143)
> >   at
> org.apache.gearpump.streaming.dsl.plan.Planner.plan(Planner.scala:50)
> >   at
> org.apache.gearpump.streaming.dsl.StreamApp.plan(StreamApp.scala:62)
> >   at
> org.apache.gearpump.streaming.dsl.StreamApp$.streamAppToApplication(StreamApp.scala:74)
> >   at
> org.apache.gearpump.streaming.dsl.javaapi.JavaStreamApp.run(JavaStreamApp.scala:45)
> >   at com.github.gearpump.demo.WordCount.main(WordCount.java:119)
> >   at com.github.gearpump.demo.WordCount.main(WordCount.java:25)
> >   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >   at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> >   at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >   at java.lang.reflect.Method.invoke(Method.java:498)
> >   at
> 

Re: [VOTE] Release of Apache Gearpump-0.8.2-incubating [RC2]

[Vincent Wang]

+1

Manu Zhang 于2016年11月18日周五 上午5:56写道：

> +1
>
> - verified KEYS and checksums
> - successfully built from source and ran SOL example locally
> - successfully deployed the binary on a 4-node cluster and run SOL locally
>
> Thanks,
> Manu
>
> On Thu, Nov 17, 2016 at 1:12 PM Kam Kasravi  wrote:
>
> > Hi Gearpump Community
> >
> > This is a call for a discussion releasing Apache Gearpump
> > 0.8.2-incubating, release candidate 2. This is the third release
> candidate.
> >
> > The source and binary tarballs, including signatures, digests, etc. can
> be
> > found
> > at:
> >
> https://dist.apache.org/repos/dist/dev/incubator/gearpump/0.8.2-incubating/RC2/
> >
> > The tag to be voted upon
> > is
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=shortlog;h=refs/tags/0.8.2-RC2
> >
> > The release hash
> > is
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=tree;h=4ab8cfae10e4f6a24a6f083352b2ca5bc9a186ab;hb=refs/tags/0.8.2-RC2
> >
> > Release artifacts are signed with the following
> > key: https://dist.apache.org/repos/dist/dev/incubator/gearpump/KEYS
> >
> > The KEYS file is available
> > here: https://dist.apache.org/repos/dist/dev/incubator/gearpump/KEYS
> >
> > For information about the contents of this release
> > see:
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=blob;f=CHANGELOG.md;h=24df95951fa2f5aee49d3a5c973b92ce28214bf1;hb=refs/tags/0.8.2-RC2
> >
> > This vote will be open for 72 hours (Sat, November 19, 2016 at 9:00PM
> PST).
> >
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, run the
> > binary artifacts in the binary release and test.
> > Please vote:
> >
> > [ ] +1 Release this package as gearpump-0.8.2
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because because...
> >
> > Thanks,
> > Kam
> >
>

Propose to combine module gearpump-daemon into gearpump-core

[Vincent Wang]

Hi all,

  Currently we have an EmbeddedCluster in gearpump-daemon module which
allows user to run their gearpump application in a local JVM.
  Now suppose user want to implement an streaming application using
Gearpump and use the EmbeddedCluster to test it locally or even in an IDE.
So the application needs to have extra dependency on the gearpump-daemon
module to access EmbeddedCluster,  and user have to write code like
* if (debugMode) {*
*  localCluster = new EmbeddedCluster(akkaConf);*
*  localCluster.start();*
*}*
*ClientContext masterClient = null;*
*if (localCluster != null) {*
*  masterClient = localCluster.newClientContext();*
*} else {*
*  masterClient = new ClientContext(akkaConf);*
*}*
*masterClient.submit(app);*

  Which is obviously tedious and inconvenient.

  So we'd like to provide user with a implementation just like what Flink
did.  Basically we want to integrate EmbeddedCluster into ClientContext so
that user can switch the application running mode easily by some
configuration or decision made by ClientConext automatically.
  However, currently the ClientContext is in module gearpump-core and
EmbeddedCluster
has dependencies on Worker and Master daemon actors, which means these
classes need to be moved along with EmbeddedCluster and finally almost the
whole gearpump-daemon module need to be integrated into gearpump-core
module.
   That's the side effect of achieving a more powerful ClientContext
integrated with a EmbeddedCluster and I'd like to hear your opinions about
on this proposal.

Thanks,
Huafeng

Re: Podling Report Reminder - September 2016

[Vincent Wang]

Hi All,

This is the Gearpump podling report for September 2016. Please help to
review.

Gearpump

Gearpump is a reactive real-time streaming engine based on the
micro-service actor model.
Gearpump has been incubating since 2016-03-08.

Three most important issues to address in the move towards graduation:

1. Make initial Apache branded release and release on a regular schedule.
2. Continue to evolve community interest and support.
3. Integrate with Apache Beam and akka-streams frameworks.

- Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware
of?
- None

- How has the community developed since the last report?
- Increased community contribution on integration with Apache Cassandra.

- How has the project developed since the last report?
- We released Apache Gearpump 0.8.1-incubating, which is Gearpump's first
release
as an Apache incubator project.
- Integration within Apache Beam (Gearpump Runner) has been merged into a
feature branch.
- Continued integration within akka-streams (Gearpump Materializer). Three
PRs committed.
- 28 issues created and 18 resolved.

Date of last release:  2016-08-16.

When were the last committers or PMC members elected?  No new committers or
PMC members elected yet.

Signed-off-by:  [ ](gearpump) Andrew Purtell  [ ](gearpump) Jarek
Jarcec Cecho  [ ](gearpump) Reynold Xin  [ ](gearpump) Todd Lipcon  [
](gearpump) Xuefu Zhang

Andrew Purtell <apurt...@apache.org>于2016年9月3日周六 上午8:27写道：

> Sounds good, thanks!
>
>
> On Thu, Sep 1, 2016 at 10:47 PM, Vincent Wang <fvunic...@gmail.com> wrote:
>
> > Hi Andrew,
> >
> >  I'd like to take it this time.
> >
> > Thanks,
> > Huafeng
> >
> > 2016-09-02 5:02 GMT+08:00 Andrew Purtell <apurt...@apache.org>:
> >
> > > Time to report to the Board and IPMC. Do we have a volunteer from the
> > PPMC
> > > to produce the report this time?
> > >
> > > On Tue, Aug 30, 2016 at 3:46 AM, <johndam...@apache.org> wrote:
> > >
> > > > Dear podling,
> > > >
> > > > This email was sent by an automated system on behalf of the Apache
> > > > Incubator PMC. It is an initial reminder to give you plenty of time
> to
> > > > prepare your quarterly board report.
> > > >
> > > > The board meeting is scheduled for Wed, 21 September 2016, 10:30 am
> > PDT.
> > > > The report for your podling will form a part of the Incubator PMC
> > > > report. The Incubator PMC requires your report to be submitted 2
> weeks
> > > > before the board meeting, to allow sufficient time for review and
> > > > submission (Wed, September 07).
> > > >
> > > > Please submit your report with sufficient time to allow the Incubator
> > > > PMC, and subsequently board members to review and digest. Again, the
> > > > very latest you should submit your report is 2 weeks prior to the
> board
> > > > meeting.
> > > >
> > > > Thanks,
> > > >
> > > > The Apache Incubator PMC
> > > >
> > > > Submitting your Report
> > > >
> > > > --
> > > >
> > > > Your report should contain the following:
> > > >
> > > > *   Your project name
> > > > *   A brief description of your project, which assumes no knowledge
> of
> > > > the project or necessarily of its field
> > > > *   A list of the three most important issues to address in the move
> > > > towards graduation.
> > > > *   Any issues that the Incubator PMC or ASF Board might wish/need to
> > be
> > > > aware of
> > > > *   How has the community developed since the last report
> > > > *   How has the project developed since the last report.
> > > >
> > > > This should be appended to the Incubator Wiki page at:
> > > >
> > > > http://wiki.apache.org/incubator/September2016
> > > >
> > > > Note: This is manually populated. You may need to wait a little
> before
> > > > this page is created from a template.
> > > >
> > > > Mentors
> > > > ---
> > > >
> > > > Mentors should review reports for their project(s) and sign them off
> on
> > > > the Incubator wiki page. Signing off reports shows that you are
> > > > following the project - projects that are not signed may raise alarms
> > > > for the Incubator PMC.
> > > >
> > > > Incubator PMC
> > > >
> > >
> > >
> > >
> > > --
> > > Best regards,
> > >
> > >- Andy
> > >
> > > Problems worthy of attack prove their worth by hitting back. - Piet
> Hein
> > > (via Tom White)
> > >
> >
>
>
>
> --
> Best regards,
>
>- Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>

Re: [VOTE] Release of Apache Gearpump-0.8.1-incubating [RC1]

[Vincent Wang]

After I build RC1 and ran tests on my desktop, the MainSpec fails, which is
caused by the akka version conflict. It's related to the shaded akka kryo
because it dependes Akka-2.3.X.
So I raise a pull request
 to update the shaded
akka kryo version and the failure is gone.

2016-07-06 17:23 GMT+08:00 Karol Brejna :

> I am able to build and run RC1 without any problems (dowloaded source
> tarball).
> I ran some examples - also OK.
> Dashboard looks fine (there were some problems with RC0).
>
> +1
>
> On Tue, Jul 5, 2016 at 3:26 AM, Kam Kasravi  wrote:
> > Hi Gearpump Community
> >
> > This is a call for a discussion releasing Apache Gearpump
> > 0.8.1-incubating, release candidate 1. This is the first release of
> > Gearpump and the second release candidate.
> >
> >
> > The source tarball, including signatures, digests, etc. can be found
> > at:*
> https://dist.apache.org/repos/dist/dev/incubator/gearpump/0.8.1-incubating/RC1/
> > <
> https://dist.apache.org/repos/dist/dev/incubator/gearpump/0.8.1-incubating/RC1/
> >*
> >
> > The tag to be voted upon is
> > 0.8.1-RC1:*
> https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=shortlog;h=refs/tags/0.8.1-RC1
> > <
> https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=shortlog;h=refs/tags/0.8.1-RC1
> >*
> >
> > The release hash is
> > 674cd8fd5ff7d3b1d3f33de3bef1c300bf664811:*
> https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=commit;h=674cd8fd5ff7d3b1d3f33de3bef1c300bf664811
> > <
> https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=commit;h=674cd8fd5ff7d3b1d3f33de3bef1c300bf664811
> >*
> >
> > Release artifacts are signed with the following
> > key:https://dist.apache.org/repos/dist/dev/incubator/gearpump/KEYS
> >
> > KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/gearpump/KEYS
> >
> > For information about the contents of this release,
> > see:*
> https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=blob;f=CHANGELOG.md;h=3ef4b4565d4ab965bc61b6783afe034b50ca5051;hb=674cd8fd5ff7d3b1d3f33de3bef1c300bf664811
> > <
> https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=blob;f=CHANGELOG.md;h=3ef4b4565d4ab965bc61b6783afe034b50ca5051;hb=674cd8fd5ff7d3b1d3f33de3bef1c300bf664811
> >*
> >
> >
> > The vote will be open for 96 hours (Friday, July 8, 2016 at 6:30 PM PST)
> >
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, and test.  The
> > please vote:
> >
> > [ ] +1 Release this package as gearpump-0.8.1
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because because...
> >
> > Thanks,
> > Kam
>