[
https://issues.apache.org/jira/browse/FLINK-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16046373#comment-16046373
]
ASF GitHub Bot commented on FLINK-6877:
---------------------------------------
Github user zentol commented on the issue:
https://github.com/apache/flink/pull/4095
Of course we can't account for feature branches, nor prevent merge
conflicts entirely. But there are people who are very aware of what is going on
right now in regards to bigger initiatives. We can use this information to
coordinate on a best-effort basis to prevent us from activating checkstyle in a
package right before a PR is being opened. This saves time both for the
contributor and the person applying the checkstyle.
Keep in mind that the whole point of introducing it package by package was
to reduce the amount of merge conflicts by targeting areas of flink-runtime
that are not actively being worked on, as outlined in #4032 and FLINK-6729.
> Activate checkstyle for runtime/security
> ----------------------------------------
>
> Key: FLINK-6877
> URL: https://issues.apache.org/jira/browse/FLINK-6877
> Project: Flink
> Issue Type: Improvement
> Components: Local Runtime
> Affects Versions: 1.4.0
> Reporter: Greg Hogan
> Assignee: Greg Hogan
> Priority: Trivial
> Fix For: 1.4.0
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
