Re: Draft of blog post for MXNet v0.12 release

A few small things: In the paragraph about volta support, I'd rather talk about "users" than "customers". Also the reference to the imagenet training script seems to be a bit out of context. In the following paragraph there is a typo: "allowing developerto" should be "allowing developers

Re: Draft of blog post for MXNet v0.12 release

It was noted that you've signed up. I've added you to the blog Sandeep :) On Tue, Oct 31, 2017 at 3:37 PM, Hen wrote: > Confirmed on the email. > > Can you sign in at blogs.apache.org using your Apache LDAP credentials > please? > > That will add you to the pool of users, and

Re: Draft of blog post for MXNet v0.12 release

Hello Hen, I can help in publishing the blog post at blogs.apache.org/MXNet with contents from draft by Sukwon posted here for review from community - https://cwiki.apache.org/confluence/display/MXNET/Draft+of+blog+post+for+MXNet+v0.12+release Just confirming here - after we post the blog, we

Re: Disable 'required status check' for master

I see 73 PR's for mxnet. 17 of those have successfully passed CI and are waiting for merge (assuming the CR passed human inspection). 21 Show some form of CI in progress. *Only 8 are in the queue in Jenkins* The rest have failed CI for one reason or another. On Tue, Oct 31, 2017 at 1:17 PM,

Re: Disable 'required status check' for master

+1 We enabled protected merge to master at a point when CI was stable (>90% build completion). However, with recent degradation in CI setup, it is no more practical. I see too many PRs in pending and development slowing down. Since new CI design and development is in progress and we have

Re: Disable 'required status check' for master

The number of pending PRs is growing very fast. At the current rate it will reach 200 before we can fix jenkins. Stability is not the only goal. Master will be most stable if we don't push anything, but that's not what we want. Committers should be responsible for their commits. Good judgement

Re: Disable 'required status check' for master

-1 I personally think it's a necessary evil and a good forcing factor to get CI fixed. Before that requirements, things that failed unit tests were being pushed into master daily. It was a big problem. At least now master is stable. On Tue, Oct 31, 2017 at 12:22 PM, Hen

Re: Disable 'required status check' for master

BTW, here is a separate thread where there is discussion happening on improving the CI system: https://lists.apache.org/thread.html/13e5ba08acd2f28a49f791c23f4baf97ba9e5bcdabe43aec598d1e19@%3Cdev.mxnet.apache.org%3E While we will eventually get a faster CI system, it is important to disable the

Re: Disable 'required status check' for master

This makes sense to me. CI isn't of value if it isn't continuous. +1. On Tue, Oct 31, 2017 at 12:07 PM, Indhu wrote: > Hi, > > We have been having issues getting CI to work fast enough. Currently the CI > is being the bottleneck to get commits in. This is severely

Disable 'required status check' for master

Hi, We have been having issues getting CI to work fast enough. Currently the CI is being the bottleneck to get commits in. This is severely impacting development. I propose we disable 'required status check' for the master branch so that we can development is not impacted. We can work on fixing

Re: mxnet java prebuilt

Hi TongKe, I've setup a travis build for scala-package, here (https://oss.sonatype.org/#nexus-search;quick~mxnet-full_2.11) you can find mxnet linux cu70, cu80, cu90, etc. We'll make full release (instead of SNAPSHOT) when the build system is stable. Best, Yizhi 2017-10-30 4:15 GMT+08:00 TongKe