Return-Path: X-Original-To: apmail-flink-user-archive@minotaur.apache.org Delivered-To: apmail-flink-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 84AD018CAA for ; Wed, 16 Dec 2015 14:12:27 +0000 (UTC) Received: (qmail 63318 invoked by uid 500); 16 Dec 2015 14:12:22 -0000 Delivered-To: apmail-flink-user-archive@flink.apache.org Received: (qmail 63235 invoked by uid 500); 16 Dec 2015 14:12:22 -0000 Mailing-List: contact user-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@flink.apache.org Delivered-To: mailing list user@flink.apache.org Received: (qmail 63218 invoked by uid 99); 16 Dec 2015 14:12:22 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2015 14:12:22 +0000 Received: from mail-qk0-f178.google.com (mail-qk0-f178.google.com [209.85.220.178]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id DA27E1A03EA; Wed, 16 Dec 2015 14:12:21 +0000 (UTC) Received: by mail-qk0-f178.google.com with SMTP id u65so45546666qkh.2; Wed, 16 Dec 2015 06:12:21 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.13.203.200 with SMTP id n191mr14074381ywd.103.1450275141038; Wed, 16 Dec 2015 06:12:21 -0800 (PST) Received: by 10.13.204.7 with HTTP; Wed, 16 Dec 2015 06:12:21 -0800 (PST) Date: Wed, 16 Dec 2015 15:12:21 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: [DISCUSS] Flink roadmap for 2016 From: Kostas Tzoumas To: "dev@flink.apache.org" , user@flink.apache.org Content-Type: multipart/alternative; boundary=001a1148248e9bbbbe0527047efc --001a1148248e9bbbbe0527047efc Content-Type: text/plain; charset=UTF-8 Hi everyone, I think it is very interesting to both developers and users of Flink to define a roadmap for future development. Together with Stephan, we started a draft containing a couple of areas that we think are important to focus on next. https://docs.google.com/document/d/1ExmtVpeVVT3TIhO1JoBpC5JKXm-778DAD7eqw5GANwE/edit?usp=sharing It would be great if we could get your feedback on this document, and use it to get the discussing on the roadmap started. I am especially including the users@ list to see what would be the next priorities for users (for example, which systems should Flink integrate with next for data input and output). The document is editable by anyone, so feel free to comment and suggest directly there. Happy roadmaping! Best, Kostas --001a1148248e9bbbbe0527047efc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi everyone,

I think it is very interes= ting to both developers and users of Flink to define a roadmap for future d= evelopment. Together with Stephan, we started a draft containing a couple o= f areas that we think are important to focus on next.=C2=A0

--001a1148248e9bbbbe0527047efc--