You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2016/05/20 18:01:12 UTC
[jira] [Commented] (NIFI-742) discuss github-pr and patch-on-jira
tradeoff in contrib guide
[ https://issues.apache.org/jira/browse/NIFI-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15293869#comment-15293869 ]
Joseph Witt commented on NIFI-742:
----------------------------------
i agree this is working pretty well for now but would welcome other views. What really turned the corner for us was when Aldrin got Travis-CI integrated (and the upcoming appveyor piece). We're doing pretty well but our ability to stay on top of PRs in Github and such does need some focus. I am hopeful the upcoming meetup/hackathon will help put a dent in that which obviously isnt a fix but still..
> discuss github-pr and patch-on-jira tradeoff in contrib guide
> -------------------------------------------------------------
>
> Key: NIFI-742
> URL: https://issues.apache.org/jira/browse/NIFI-742
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Documentation & Website
> Reporter: Sean Busbey
>
> once NIFI-577 goes in, add a note in the contrib guide about the tradeoff for github pr vs patch on jira.
> * review ease
> * response traffic
> * precommit patch test
> (this will likely change substantially if the github support is live in the release of the patch tester we start with)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)