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 to". Best, Sebastian On 01.11.2017 01:27, sandeep krishnamurthy wrote: Thank you, Henry, for the help. Regards, Sandeep On Tue, Oct 31, 2017 at 5:22 PM, Hen wrote: 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 then one of the mentors can add you to the blog :) Hen On Tue, Oct 31, 2017 at 2:08 PM, sandeep krishnamurthy < sandeep.krishn...@gmail.com> wrote: 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 will be emailing to - " annou...@apache.org" and "dev@mxnet.incubator.apache.org" with the blog link. Correct? Regards, Sandeep On Mon, Oct 30, 2017 at 4:48 PM, Hen wrote: Related question - which committer wants to publish the blog? It needs to be a member of the project. On Mon, Oct 30, 2017 at 4:41 PM, Sally Khudairi wrote: Thanks, Sukwon; hello Chris and MXNet pPMC. I have been discussing this with Sukwon and have agreed on the following tactics: 1) blog post published on blogs.apache.org/MXNet from the pPMC; 2) email sent to annou...@apache.org and the Apache MXNet (incubating) lists; and3) Sally will include in the Apache Weekly News Round-up once the email to announce@ is in the archives There is no formal press activity surrounding this release, nor is there any official ASF publicity on this release, as the project is still undergoing incubation. Kind regards, Sally - - - Vice President Marketing & Publicity The Apache Software Foundation Tel +1 617 921 8656 Skype sallykhudairi On Mon, Oct 30, 2017, at 19:11, Suk Won Kim wrote: Yes, I have been in touch with Sally for this post, and she is aware of this.> It will not be published via official press release. On Mon, Oct 30, 2017 at 4:10 PM, Chris Mattmann wrote:>> Has this been in coordination with Sally? There’s a pretty hard and fast Incubator rule to not promote>> Podlings via official press channels – where will this be published?>> Cheers, Chris On 10/30/17, 4:08 PM, "Suk Won Kim" wrote: Created a page in cwiki for a draft of blog post for MXNet v0.12 release. https://cwiki.apache.org/confluence/display/MXNET/ Draft+of+blog+post+for+MXNet+v0.12+release Thanks. -- *Sukwon Kim, *>> -- *Sukwon Kim, * Senior Product Manager-Technical, Amazon Web Services (AWS) EC2 -- Sandeep Krishnamurthy
Re: Draft of blog post for MXNet v0.12 release
Thank you, Henry, for the help. Regards, Sandeep On Tue, Oct 31, 2017 at 5:22 PM, Hen wrote: > 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 then one of the mentors can > > add you to the blog :) > > > > Hen > > > > > > On Tue, Oct 31, 2017 at 2:08 PM, sandeep krishnamurthy < > > sandeep.krishn...@gmail.com> wrote: > > > >> 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 will be emailing to - > " > >> annou...@apache.org" and "dev@mxnet.incubator.apache.org" with the blog > >> link. Correct? > >> > >> Regards, > >> Sandeep > >> > >> On Mon, Oct 30, 2017 at 4:48 PM, Hen wrote: > >> > >> > Related question - which committer wants to publish the blog? It needs > >> to > >> > be a member of the project. > >> > > >> > On Mon, Oct 30, 2017 at 4:41 PM, Sally Khudairi > wrote: > >> > > >> > > Thanks, Sukwon; hello Chris and MXNet pPMC. > >> > > > >> > > I have been discussing this with Sukwon and have agreed on the > >> > > following tactics: > >> > > 1) blog post published on blogs.apache.org/MXNet from the pPMC; > >> > > 2) email sent to annou...@apache.org and the Apache MXNet > >> (incubating) > >> > >lists; and3) Sally will include in the Apache Weekly News > Round-up > >> > once > >> > > the email > >> > >to announce@ is in the archives > >> > > There is no formal press activity surrounding this release, nor is > >> there > >> > > any official ASF publicity on this release, as the project is still > >> > > undergoing incubation. > >> > > Kind regards, > >> > > Sally > >> > > > >> > > - - - > >> > > Vice President Marketing & Publicity > >> > > The Apache Software Foundation > >> > > > >> > > Tel +1 617 921 8656 > >> > > Skype sallykhudairi > >> > > > >> > > > >> > > On Mon, Oct 30, 2017, at 19:11, Suk Won Kim wrote: > >> > > > Yes, > >> > > > I have been in touch with Sally for this post, and she is aware > >> > > > of this.> It will not be published via official press release. > >> > > > > >> > > > On Mon, Oct 30, 2017 at 4:10 PM, Chris Mattmann > >> > > > wrote:>> Has this been in coordination with > >> > > Sally? There’s a pretty hard and > >> > > >> fast Incubator rule to not promote>> Podlings via official press > >> > > channels – where will this be published?>> > >> > > >> Cheers, > >> > > >> Chris > >> > > >> > >> > > >> > >> > > >> > >> > > >> > >> > > >> On 10/30/17, 4:08 PM, "Suk Won Kim" > wrote: > >> > > >> > >> > > >> Created a page in cwiki for a draft of blog post for MXNet > >> v0.12 > >> > > >> release. > >> > > >> https://cwiki.apache.org/confluence/display/MXNET/ > >> > > Draft+of+blog+post+for+MXNet+v0.12+release > >> > > >> > >> > > >> Thanks. > >> > > >> -- > >> > > >> > >> > > >> *Sukwon Kim, *>> > >> > > >> > >> > > >> > >> > > > > >> > > > > >> > > > > >> > > > -- > >> > > > *Sukwon Kim, * > >> > > > > >> > > > Senior Product Manager-Technical, > >> > > > Amazon Web Services (AWS) EC2 > >> > > > >> > > > >> > > >> > >> > >> > >> -- > >> Sandeep Krishnamurthy > >> > > > > > -- Sandeep Krishnamurthy
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 then one of the mentors can > add you to the blog :) > > Hen > > > On Tue, Oct 31, 2017 at 2:08 PM, sandeep krishnamurthy < > sandeep.krishn...@gmail.com> wrote: > >> 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 will be emailing to - " >> annou...@apache.org" and "dev@mxnet.incubator.apache.org" with the blog >> link. Correct? >> >> Regards, >> Sandeep >> >> On Mon, Oct 30, 2017 at 4:48 PM, Hen wrote: >> >> > Related question - which committer wants to publish the blog? It needs >> to >> > be a member of the project. >> > >> > On Mon, Oct 30, 2017 at 4:41 PM, Sally Khudairi wrote: >> > >> > > Thanks, Sukwon; hello Chris and MXNet pPMC. >> > > >> > > I have been discussing this with Sukwon and have agreed on the >> > > following tactics: >> > > 1) blog post published on blogs.apache.org/MXNet from the pPMC; >> > > 2) email sent to annou...@apache.org and the Apache MXNet >> (incubating) >> > >lists; and3) Sally will include in the Apache Weekly News Round-up >> > once >> > > the email >> > >to announce@ is in the archives >> > > There is no formal press activity surrounding this release, nor is >> there >> > > any official ASF publicity on this release, as the project is still >> > > undergoing incubation. >> > > Kind regards, >> > > Sally >> > > >> > > - - - >> > > Vice President Marketing & Publicity >> > > The Apache Software Foundation >> > > >> > > Tel +1 617 921 8656 >> > > Skype sallykhudairi >> > > >> > > >> > > On Mon, Oct 30, 2017, at 19:11, Suk Won Kim wrote: >> > > > Yes, >> > > > I have been in touch with Sally for this post, and she is aware >> > > > of this.> It will not be published via official press release. >> > > > >> > > > On Mon, Oct 30, 2017 at 4:10 PM, Chris Mattmann >> > > > wrote:>> Has this been in coordination with >> > > Sally? There’s a pretty hard and >> > > >> fast Incubator rule to not promote>> Podlings via official press >> > > channels – where will this be published?>> >> > > >> Cheers, >> > > >> Chris >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> On 10/30/17, 4:08 PM, "Suk Won Kim" wrote: >> > > >> >> > > >> Created a page in cwiki for a draft of blog post for MXNet >> v0.12 >> > > >> release. >> > > >> https://cwiki.apache.org/confluence/display/MXNET/ >> > > Draft+of+blog+post+for+MXNet+v0.12+release >> > > >> >> > > >> Thanks. >> > > >> -- >> > > >> >> > > >> *Sukwon Kim, *>> >> > > >> >> > > >> >> > > > >> > > > >> > > > >> > > > -- >> > > > *Sukwon Kim, * >> > > > >> > > > Senior Product Manager-Technical, >> > > > Amazon Web Services (AWS) EC2 >> > > >> > > >> > >> >> >> >> -- >> Sandeep Krishnamurthy >> > >
Re: Draft of blog post for MXNet v0.12 release
High level thoughts: * There's no "go to to download the new version" * I assume the title will be "Apache MXNet 0.12 released!" or some such; or if the first line is meant to be the title (*Apache MXNet Release Adds Support for New NVIDIA Volta GPUs and Sparse Tensor*), it could do with the version there too. * Perhaps include a tweet url in the blog and invite them to retweet? Not sure if that's too needy :) * After the two features are mentioned, I think there should be a summing up section. Something that invites the user to try out the new release (the go to link in my first thought) and then invites them to come contribute/chat (info on dev@ + Slack). A difference between an open source project and a company product is that your users are often the pool you source new project members from. So a release is both an invitation to them to try out the new version, and your recruiting pipeline. Hen On Mon, Oct 30, 2017 at 4:08 PM, Suk Won Kim wrote: > Created a page in cwiki for a draft of blog post for MXNet v0.12 release. > https://cwiki.apache.org/confluence/display/MXNET/ > Draft+of+blog+post+for+MXNet+v0.12+release > > Thanks. > -- > > *Sukwon Kim, * >
Re: Draft of blog post for MXNet v0.12 release
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 then one of the mentors can add you to the blog :) Hen On Tue, Oct 31, 2017 at 2:08 PM, sandeep krishnamurthy < sandeep.krishn...@gmail.com> wrote: > 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 will be emailing to - " > annou...@apache.org" and "dev@mxnet.incubator.apache.org" with the blog > link. Correct? > > Regards, > Sandeep > > On Mon, Oct 30, 2017 at 4:48 PM, Hen wrote: > > > Related question - which committer wants to publish the blog? It needs to > > be a member of the project. > > > > On Mon, Oct 30, 2017 at 4:41 PM, Sally Khudairi wrote: > > > > > Thanks, Sukwon; hello Chris and MXNet pPMC. > > > > > > I have been discussing this with Sukwon and have agreed on the > > > following tactics: > > > 1) blog post published on blogs.apache.org/MXNet from the pPMC; > > > 2) email sent to annou...@apache.org and the Apache MXNet (incubating) > > >lists; and3) Sally will include in the Apache Weekly News Round-up > > once > > > the email > > >to announce@ is in the archives > > > There is no formal press activity surrounding this release, nor is > there > > > any official ASF publicity on this release, as the project is still > > > undergoing incubation. > > > Kind regards, > > > Sally > > > > > > - - - > > > Vice President Marketing & Publicity > > > The Apache Software Foundation > > > > > > Tel +1 617 921 8656 > > > Skype sallykhudairi > > > > > > > > > On Mon, Oct 30, 2017, at 19:11, Suk Won Kim wrote: > > > > Yes, > > > > I have been in touch with Sally for this post, and she is aware > > > > of this.> It will not be published via official press release. > > > > > > > > On Mon, Oct 30, 2017 at 4:10 PM, Chris Mattmann > > > > wrote:>> Has this been in coordination with > > > Sally? There’s a pretty hard and > > > >> fast Incubator rule to not promote>> Podlings via official press > > > channels – where will this be published?>> > > > >> Cheers, > > > >> Chris > > > >> > > > >> > > > >> > > > >> > > > >> On 10/30/17, 4:08 PM, "Suk Won Kim" wrote: > > > >> > > > >> Created a page in cwiki for a draft of blog post for MXNet > v0.12 > > > >> release. > > > >> https://cwiki.apache.org/confluence/display/MXNET/ > > > Draft+of+blog+post+for+MXNet+v0.12+release > > > >> > > > >> Thanks. > > > >> -- > > > >> > > > >> *Sukwon Kim, *>> > > > >> > > > >> > > > > > > > > > > > > > > > > -- > > > > *Sukwon Kim, * > > > > > > > > Senior Product Manager-Technical, > > > > Amazon Web Services (AWS) EC2 > > > > > > > > > > > > -- > Sandeep Krishnamurthy >
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 will be emailing to - " annou...@apache.org" and "dev@mxnet.incubator.apache.org" with the blog link. Correct? Regards, Sandeep On Mon, Oct 30, 2017 at 4:48 PM, Hen wrote: > Related question - which committer wants to publish the blog? It needs to > be a member of the project. > > On Mon, Oct 30, 2017 at 4:41 PM, Sally Khudairi wrote: > > > Thanks, Sukwon; hello Chris and MXNet pPMC. > > > > I have been discussing this with Sukwon and have agreed on the > > following tactics: > > 1) blog post published on blogs.apache.org/MXNet from the pPMC; > > 2) email sent to annou...@apache.org and the Apache MXNet (incubating) > >lists; and3) Sally will include in the Apache Weekly News Round-up > once > > the email > >to announce@ is in the archives > > There is no formal press activity surrounding this release, nor is there > > any official ASF publicity on this release, as the project is still > > undergoing incubation. > > Kind regards, > > Sally > > > > - - - > > Vice President Marketing & Publicity > > The Apache Software Foundation > > > > Tel +1 617 921 8656 > > Skype sallykhudairi > > > > > > On Mon, Oct 30, 2017, at 19:11, Suk Won Kim wrote: > > > Yes, > > > I have been in touch with Sally for this post, and she is aware > > > of this.> It will not be published via official press release. > > > > > > On Mon, Oct 30, 2017 at 4:10 PM, Chris Mattmann > > > wrote:>> Has this been in coordination with > > Sally? There’s a pretty hard and > > >> fast Incubator rule to not promote>> Podlings via official press > > channels – where will this be published?>> > > >> Cheers, > > >> Chris > > >> > > >> > > >> > > >> > > >> On 10/30/17, 4:08 PM, "Suk Won Kim" wrote: > > >> > > >> Created a page in cwiki for a draft of blog post for MXNet v0.12 > > >> release. > > >> https://cwiki.apache.org/confluence/display/MXNET/ > > Draft+of+blog+post+for+MXNet+v0.12+release > > >> > > >> Thanks. > > >> -- > > >> > > >> *Sukwon Kim, *>> > > >> > > >> > > > > > > > > > > > > -- > > > *Sukwon Kim, * > > > > > > Senior Product Manager-Technical, > > > Amazon Web Services (AWS) EC2 > > > > > -- Sandeep Krishnamurthy
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, Eric Xie wrote: > 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 is the > ultimate guarantee of good code. > > Thanks, > Eric > > On 2017-10-31 12:38, Chris Olivier wrote: > > -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 wrote: > > > > > 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 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 > > > > the CI situation in parallel. > > > > > > > > Committer, > > > > Please vote if you are okay with disabling 'required status check' > for > > > > master. > > > > > > > > Once we have enough votes, I'll request a mentor to file a ticket > with > > > > infra. > > > > > > > > Thanks, > > > > Indu > > > > > > > > > >
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 "nightly tests running", disabling protected merge would be a better choice till we get stable CI in place. Thanks, Sandeep On Tue, Oct 31, 2017 at 1:17 PM, Eric Xie wrote: > 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 is the > ultimate guarantee of good code. > > Thanks, > Eric > > On 2017-10-31 12:38, Chris Olivier wrote: > > -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 wrote: > > > > > 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 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 > > > > the CI situation in parallel. > > > > > > > > Committer, > > > > Please vote if you are okay with disabling 'required status check' > for > > > > master. > > > > > > > > Once we have enough votes, I'll request a mentor to file a ticket > with > > > > infra. > > > > > > > > Thanks, > > > > Indu > > > > > > > > > > -- Sandeep Krishnamurthy
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 is the ultimate guarantee of good code. Thanks, Eric On 2017-10-31 12:38, Chris Olivier wrote: > -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 wrote: > > > 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 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 > > > the CI situation in parallel. > > > > > > Committer, > > > Please vote if you are okay with disabling 'required status check' for > > > master. > > > > > > Once we have enough votes, I'll request a mentor to file a ticket with > > > infra. > > > > > > Thanks, > > > Indu > > > > > >
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 wrote: > 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 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 > > the CI situation in parallel. > > > > Committer, > > Please vote if you are okay with disabling 'required status check' for > > master. > > > > Once we have enough votes, I'll request a mentor to file a ticket with > > infra. > > > > Thanks, > > Indu > > >
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 checks for now to not block or slow down development until we have a faster CI system. 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 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 > the CI situation in parallel. > > Committer, > Please vote if you are okay with disabling 'required status check' for > master. > > Once we have enough votes, I'll request a mentor to file a ticket with > infra. > > Thanks, > Indu > >
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 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 > the CI situation in parallel. > > Committer, > Please vote if you are okay with disabling 'required status check' for > master. > > Once we have enough votes, I'll request a mentor to file a ticket with > infra. > > Thanks, > Indu >
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 the CI situation in parallel. Committer, Please vote if you are okay with disabling 'required status check' for master. Once we have enough votes, I'll request a mentor to file a ticket with infra. Thanks, Indu
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 Xue : > Hi, > > Looking at https://mvnrepository.com/artifact/ml.dmlc.mxnet?sort=newest > it appears there are no new maven packages since Jun 3 2017. > > For using the mxnet scala api, is the standard solution to: > > 1. always build from github / source via > https://mxnet.incubator.apache.org/get_started/build_from_source.html > > or > > 2. there's some other repo to use? > > > Thanks, > --TongKe -- Yizhi Liu DMLC member Technical Manager Qihoo 360 Inc, Shanghai, China
