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

Posted to dev@reef.apache.org by "Brian Cho (JIRA)" <ji...@apache.org> on 2014/12/30 03:19:13 UTC

[jira] [Closed] (REEF-77) Remove REEF Bridge from release branch

     [ https://issues.apache.org/jira/browse/REEF-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Cho closed REEF-77.
-------------------------
    Resolution: Fixed

[~markus.weimer], yes this has been resolved via commit dee0a76ff0fd21525d220d16d71170dbf5424d56 on branch-0.10.0-incubating.

Unfortunately, I was unable to create a PR for this change. The commit was the first change on a new branch. It seems the new branch only gets transferred to github after the first new commit. (This is what I observed, but I'm not 100% sure this is how it's supposed to work.)

> Remove REEF Bridge from release branch
> --------------------------------------
>
>                 Key: REEF-77
>                 URL: https://issues.apache.org/jira/browse/REEF-77
>             Project: REEF
>          Issue Type: Task
>          Components: REEF Bridge
>            Reporter: Brian Cho
>            Assignee: Brian Cho
>
> Apache source releases are not allowed to contain binary files. As such, REEF Bridge should be removed from the release branch. It should be added back once REEF-51 is resolved.



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