We don't need to involve Apache Infra if we don't add it as required check
of the protected master branch. Does anybody know the previous maintainer
or the credentials to access the old setup of Travis CI?
On Fri, Dec 8, 2017 at 4:32 PM, Pedro Larroy
wrote:
> We can enable with just everything c
We can enable with just everything commented out and returning "true"
so we can fix it on successive PRs. Do we need an admin for that?
On Fri, Dec 8, 2017 at 12:20 PM, Marco de Abreu
wrote:
> Who's going to maintain and fix problems which will arise with travis CI?
> Due to the protected master
Hi,
I recently tried to look through open issues and noticed that we're not
really making use of the labelling feature:
https://github.com/apache/incubator-mxnet/issues. I think in order to
improve clarity and thus encourage people to actually work on open issues,
we should start to tag all issues
Who's going to maintain and fix problems which will arise with travis CI?
Due to the protected master branch, this can cause some serious blocking
issues. I think it should be tested and everything fixed before we
re-enable travis CI.
My proposal is to wait for stage 3 (new features) of the new CI
Can somebody re-enable travis CI so we can do mac builds? currently
the unit tests don't build in Mac because Mac is not tested.
On Fri, Dec 8, 2017 at 12:02 PM, Pedro Larroy
wrote:
> +1
>
>
>
> On Fri, Dec 8, 2017 at 1:02 AM, Chris Olivier wrote:
>> +1
>>
>> On Thu, Dec 7, 2017 at 3:57 PM, kel
+1
On Fri, Dec 8, 2017 at 1:02 AM, Chris Olivier wrote:
> +1
>
> On Thu, Dec 7, 2017 at 3:57 PM, kellen sunderland <
> kellen.sunderl...@gmail.com> wrote:
>
>> It's using a fixed binary version of openblas and opencv, so the versions
>> there might be different than what we use. It's compiling
