[ANNOUNCE] Apache MXNet (incubating) 0.12.0 Release

Hello All, The Apache MXNet (incubating) Community is happy to announce the availability of Apache MXNet (incubating) version 0.12! Contributors in the MXNet community have collaborated to bring such feature enhancements to users. With this release, MXNet adds two new important features: •

Re: Grant access to slack

Hi Matthias, Channels of interest for you might be #mxnet and #mxnet-builds. Best, Sebastian 2017-11-01 17:20 GMT+01:00 Suneel Marthi : > Invite sent > > Sent from my iPhone > > > On Nov 1, 2017, at 6:17 PM, Matthias Seeger wrote: > > > > Hello, > >

Re: [Proposal] Stabilizing Apache MXNet CI build system

Some inline thoughts. On Wed, Nov 1, 2017 at 9:41 AM, Bhavin Thaker wrote: > Few comments/suggestions: > > 1) Can we have this nice list of todo items on the Apache MXNet wiki page > to track them better? > > 2) Can we have a set of owners for each set of tests and

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

Thank you, Sebastian and Henry. Addressed your comments. Regards, Sandeep On Tue, Oct 31, 2017 at 10:08 PM, Sebastian wrote: > A few small things: > > In the paragraph about volta support, I'd rather talk about "users" than > "customers". Also the reference to the

Re: [Proposal] Stabilizing Apache MXNet CI build system

To point 7) I did a little bit of measure / profiling of our test runs a week or two ago and came to the same conclusion. I assumed the slow downs were mostly due to new tests which had recently been added. There were quite a few gluon tests for example added, and I think they're fairly resource

Re: [Proposal] Stabilizing Apache MXNet CI build system

Hi Bhavin Good suggestions. I wanted to respond to your point #5 The promotion of integration to master would be done automatically by jenkins once a commit passes the nightly tests. So it should not impose any additional burden on the developers, as there is no manual step involved / human

Re: [Proposal] Stabilizing Apache MXNet CI build system

Few comments/suggestions: 1) Can we have this nice list of todo items on the Apache MXNet wiki page to track them better? 2) Can we have a set of owners for each set of tests and source code directory? One of the problems I have observed is that when there is a test failure, it is difficult to

Re: Grant access to slack

Invite sent Sent from my iPhone > On Nov 1, 2017, at 6:17 PM, Matthias Seeger wrote: > > Hello, > > I got a few PRs merged into MXNet already (github mseeger). Could you grant > me access to slack, and give me details on the channel? > > > -- > Matthias Seeger

Re: [Proposal] Stabilizing Apache MXNet CI build system

+1 That would be great. On Mon, Oct 30, 2017 at 5:35 PM, Hen wrote: > How about we ask for a new mxnet repo to store all the config in? > > On Fri, Oct 27, 2017 at 05:30 Pedro Larroy > wrote: > >> Just to provide a high level overview of the