Guys, On behalf of the gearpump team, I'd like to propose to merge the gearpump-runner branch into master, which will give it more visibility to other contributors and users. The runner satisfies the following criteria outlined in contribution guide [1].
1. Have at least 2 contributors interested in maintaining it, and 1 committer interested in supporting it: *Both Huafeng and me have been making contributions[2] and we will continue to maintain it. Kenn and JB have been supporting the runner (Thank you, guys!)* 2. Provide both end-user and developer-facing documentation*: They are already on the website ([3] and [4]).* 3. Have at least a basic level of unit test coverage: *We do.* *[5]* 4. Run all existing applicable integration tests with other Beam components and create additional tests as appropriate: *gearpump-runner passes ValidatesRunner tests.* Additionally, as a runner, 1. Be able to handle a subset of the model that address a significant set of use cases (aka. ‘traditional batch’ or ‘processing time streaming’): *gearpump runner is able to handle event time streaming * 2. Update the capability matrix with the current status: *[4]* 3. Add a webpage under documentation/runners: *[3]* The PR for the merge: https://github.com/apache/beam/pull/3611 Thanks, Manu [1] http://beam.apache.org/contribute/contribution-guide/#feature-branches [2] https://issues.apache.org/jira/browse/BEAM-79 [3] https://beam.apache.org/documentation/runners/gearpump/ [4] https://beam.apache.org/documentation/runners/capability-matrix/ [5] https://github.com/apache/beam/tree/gearpump-runner/runners/gearpump/src/test/java/org/apache/beam/runners/gearpump
