You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Jagadish (JIRA)" <ji...@apache.org> on 2016/04/20 04:29:25 UTC

[jira] [Commented] (SAMZA-880) Moving to github/pull-request for code review and check-in

    [ https://issues.apache.org/jira/browse/SAMZA-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15249143#comment-15249143 ] 

Jagadish commented on SAMZA-880:
--------------------------------

[~nickpan47] I've assigned this to myself and expect to work on it.

> Moving to github/pull-request for code review and check-in
> ----------------------------------------------------------
>
>                 Key: SAMZA-880
>                 URL: https://issues.apache.org/jira/browse/SAMZA-880
>             Project: Samza
>          Issue Type: Task
>            Reporter: Yi Pan (Data Infrastructure)
>            Assignee: Jagadish
>
> As per mailing list [discussion|http://mail-archives.apache.org/mod_mbox/samza-dev/201602.mbox/%3CCAFvExu230gjja7z99LzN6bhnEKYPjrnoF3KYC+dvGkO_ZnQExw@mail.gmail.com%3E], we are going to change the code review and commit process to use github pull request. This would require a few things:
> 1) incorporate kafka-merge-pr.py from [kafka repo|https://github.com/apache/kafka/blob/trunk/kafka-merge-pr.py] to Samza that include the merge steps for github pull requests to Apache Samza git repo
> 2) update the documentation in contributor corner for the new developer workflow 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)