Re: Release plan - MXNET 1.3

Hi, I have created a wiki for tracking MXNet 1.3 release with the timeline. Please take a look here: https://cwiki.apache.org/confluence/display/MXNET/Apache+MXNet+%28incubating%29+1.3.0+Release+Status I am still waiting for following 2 PRs to get merged: TRT integration: https://github.com/apach

Seattle meetup

Hi, I just found this Meetup invite: https://www.meetup.com/Apache-MXNet-Seattle-meetup/events/253104242/ Best regards, Marco

Re: [DISCUSS] improve MXNet Scala release process

Upon offline discussion with Marco, He proposed a plan that can actually help us conduct 3): 1. This job will not be trigger when PR runs and strictly limit that only committer can run the restricted job. 2. The code being run in there will only covers the code from the branch yo

Re: Requesting slack access

Hi Juan - welcome to the MXNet community. Please check out how to get involved . What are your working on? Regards, Steffen On Mon, Jul 30, 2018 at 11:16 PM Juan Vercellone wrote: > -- > -- .- > VERCELLONE, Juan. > (also known

Re: Requesting slack access

Hi Leonardo - welcome to the MXNet community. Please check out how to get involved . What are your working on? Regards, Steffen On Tue, Jul 31, 2018 at 1:12 AM leonardo espinosa wrote: > Hi there, > > I'm working in some projects usi

Re: Release blocker: non-determinstic forward in gluon

I'd agree that we should have a repeatable process for generating artifacts. It would be useful for Apache release reviewers to be able to double check the results we get in CI, and it would help give a consistent experience for users. I'm a little uncomfortable with the idea of generating the ac

Requesting slack access

Hi there, I'm working in some projects using MXNet, and perhaps (if I get some extra free time) I'm thinking to add part of my research on the main branch. Thanks in advance, Leonardo --- Dr. Leonardo Espinosa *about me:* http://www.espinosaleal.me