Hi Dominik,
Our builds couldn't update the PR commit status. I'm wondering if it might be
due to your credentials not having write access to the incubator-mxnet-test
repo?
> On Jun 30, 2017, at 4:27 PM, Mu Li wrote:
>
> Thanks Dom. Agree that we should use a credential to
Sure. As I noted "optional at compile-time", and it certainly looks that
way.
We just don't want to force downstream users to get adversely-licensed
products just to build our software. And MXNET_USE_DIST_KVSTORE meets that
requirement.
Cheers,
-g
On Mon, Jul 10, 2017 at 4:11 PM, Dominic
Greg, et al, do you believe this is a non-issue and resolved based on what
Mu has said?
On Fri, Jul 7, 2017 at 9:38 AM, Mu Li wrote:
> ZeroMQ is used only if setting `USE_DIST_KVSTORE = 1` during compilation.
> In default, it is 0.
>
> The source codes are close to the
Also, DON'T mark the branch as "*Require status checks to pass before
merging*" since builds may be unstable at first. The existing configuration
should be preserved after the transfer but we just have to validate that.
https://help.github.com/articles/enabling-required-status-checks/
On Mon,
Thank you for the info.
As I understand, if we skip the R pkg when releasing the a new version of
MXNet, everything is OK. This is can be done by adding a .gitattribute.
I will ask on legal-discuss@ for more info and confirmation.
Really thank you for all the info! It is super helpful.
Best,