The repo splitting is the result of the grown code base. So this will
happen finally. The problem is when and how.
when: the time point seems not bad.
how: is the schema good?
I assume we can not add committer per project(or the committer is just a
logic concept?). So just splitting into flink-l
t;
>
> Am 20/02/17 um 14:47 schrieb Jin Mingjian:
>
> Hi, Flink dev community,
>>
>> I'd like to contribute to Flink. Particularly, I am interested in kinds of
>> optimization works in Flink.
>>
>> To be familiar with the process of contribution, I p
Hi, Flink dev community,
I'd like to contribute to Flink. Particularly, I am interested in kinds of
optimization works in Flink.
To be familiar with the process of contribution, I pick up some starter
issue as the entrance contribution(s) such as [FLINK-5692](
https://issues.apache.org/jira/brows
Cool, Jark and Kostas!
On Thu, Feb 16, 2017 at 3:04 PM, Vasudevan, Ramkrishna S <
ramkrishna.s.vasude...@intel.com> wrote:
> Congrats Jark and Kostas.
>
> Regards
> Ram
>
> -Original Message-
> From: Kostas Kloudas [mailto:k.klou...@data-artisans.com]
> Sent: Monday, February 13, 2017 3:0
+1. (sorry, I am not a committer now but still like to contribute some
ideas.)
Time-based releasing schema is more from reflections on fast paced
ecosystem. More stable revisions and more features are continued to
delivered in the future release. The stability of one release is a "best
effort" in
