Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
From: rmetzger <git@git.apache.org>
To: issues@flink.incubator.apache.org
Reply-To: issues@flink.incubator.apache.org
References: <git-pr-1432-flink@git.apache.org>
In-Reply-To: <git-pr-1432-flink@git.apache.org>
Subject: [GitHub] flink pull request: [FLINK-3057][py] Bidirectional
 Connection
Content-Type: text/plain
Message-Id: <20160106140026.78FBFDFC8A@git1-us-west.apache.org>
Date: Wed,  6 Jan 2016 14:00:26 +0000 (UTC)

Github user rmetzger commented on the pull request:

    https://github.com/apache/flink/pull/1432#issuecomment-169329884
  
    I've quickly scrolled through the change. I'm wondering whether we should change the development process for the Python API a bit.
    It seems that you are currently the only committer working on the Python API. Maybe it makes sense that you push changes directly to `master` if they don't touch the rest of the system. Do you think that would improve the ease of development of the python API?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---