Mailing-List: contact dev-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Received-SPF: pass (athena.apache.org: domain of henry.saputra@gmail.com
 designates 209.85.217.170 as permitted sender)
MIME-Version: 1.0
Date: Wed, 18 Mar 2015 11:37:14 -0700
Message-ID: 
 <CALuGr6YFh6hPq73Rcqdai=zjDwsRsL1gyUMMD5Jr4832A1Y_Mw@mail.gmail.com>
Subject: [DISCUSS] Submitting small PRs rather than massive ones
From: Henry Saputra <henry.saputra@gmail.com>
To: "dev@flink.apache.org" <dev@flink.apache.org>
Content-Type: text/plain; charset=UTF-8

Hi All,

Recently there have been some PRs with massive changes which include
multiple JIRA tickets.

It is getting tougher to review and also to back port changes if needed.

To help reviewers to help review the changes lets try to submit small
but often PRs to make it easier to review.
Not to mention Github UI suffers with diff changes over 200 files and
thousands lines of code changes =)

When committing to ASF git it should be fine to combine one day of
work but PRs should as isolated as possible.

Exception such as new module like Gelly or ML maybe ok, but others
that require changes to the execution flow should be done if smaller
batches if possible.

Thanks,

Henry