Pylint Undefined variable/name error

2018-07-26 Thread Vandana Kannan
Hi All,

On enabling the option "undefined-variable" in pylint (in pylintrc) and 
executing on the latest code, 52 errors show up (most of them from the example 
folder). These could lead to Python NameError at runtime. The errors are 
documented in https://github.com/apache/incubator-mxnet/issues/11904. 

Currently, this Pylint option is disabled in CI and pylint is not executed on 
the example folder.

Would it be a good idea to enable the option in CI to catch these errors, and 
in the meantime, fix the backlog? 

Thanks,
Vandana


Updated invitation with note: MXNet hangout (II / Americas) @ Fri Aug 3, 2018 02:00 - 03:00 (CEST) (dev@mxnet.incubator.apache.org)

2018-07-26 Thread pedro . larroy . lists
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20180803T00Z
DTEND:20180803T01Z
DTSTAMP:20180726T202628Z
ORGANIZER;CN=Pedro Larroy:mailto:pedro.larroy.li...@gmail.com
UID:4fi8kbc55k49bucunfs3c64...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dev@mxnet.incubator.apache.org;X-NUM-GUESTS=0:mailto:d...@mxnet.incu
 bator.apache.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Pedro Larroy;X-NUM-GUESTS=0:mailto:pedro.larroy.li...@gmail.com
CREATED:20180726T202240Z
DESCRIPTION:\n\n\n\n\n\n\n\nFixed time...\n\n\n   Dial in instructions:\n  
  -\n\n  https://chime.aws/8536075882\n\n  Meeting ID: 8536 07 5882\
 n\n  United States Toll-Free: +1 855-552-4463  Meeting PIN: 8536 07 588
 2\n\n  One-click Mobile Dial-in (United States (1)): +1\n  206-462-
 5569\,\,8536075882#\n\n  International: https://chime.aws/dialinnumbers
 /\n  -\n\n   Agenda:\n   - TBD\n\n\nPlease feel free to add agenda item
 s to hangout wiki page\n\n\n-::~:~::~:~:~:~:~:~:~
 :~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\nPlease 
 do not edit this section of the description.\n\nView your event at https://
 www.google.com/calendar/event?action=VIEW=NGZpOGtiYzU1azQ5YnVjdW5mczNjN
 jRsbmcgZGV2QG14bmV0LmluY3ViYXRvci5hcGFjaGUub3Jn=MjgjcGVkcm8ubGFycm95Lmx
 pc3RzQGdtYWlsLmNvbTA0ODlkZGQ5NmVkYzhlYzAzMjMwODI0MDAwOWI0YjMxODRmYTgyMTU
 z=Europe%2FBerlin=en=0.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20180726T202628Z
LOCATION:
SEQUENCE:2
STATUS:CONFIRMED
SUMMARY:MXNet hangout (II / Americas)
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics


Canceled event: MXNet hangout (II / Americas) @ Thu Aug 2, 2018 02:00 - 03:00 (CEST) (dev@mxnet.incubator.apache.org)

2018-07-26 Thread pedro . larroy . lists
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VEVENT
DTSTART:20180802T00Z
DTEND:20180802T01Z
DTSTAMP:20180726T203037Z
ORGANIZER;CN=Pedro Larroy:mailto:pedro.larroy.li...@gmail.com
UID:4fi8kbc55k49bucunfs3c64...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=de
 v...@mxnet.incubator.apache.org;X-NUM-GUESTS=0:mailto:d...@mxnet.incubator.apac
 he.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;CN=Pedro 
 Larroy;X-NUM-GUESTS=0:mailto:pedro.larroy.li...@gmail.com
CREATED:20180726T202240Z
DESCRIPTION:Invitation in behalf of Steffen Rochel:https://
 lists.apache.org/thread.html/f0a2677bf5f34c051b1d1701558895f2752e1def00de3c
 065c017a09@%3Cdev.mxnet.apache.org%3EThis time with the right t
 ime and timezone.\;\;\;Dial in instructions:
 \;\;\;-\;\;\;\;\;\;https://chime.aws/8536075882;>https://chime.aws/8536075882\;\;\;\;\;\;Meeting ID: 8536 07 5882
 \;\;\;\;\;\;United States Toll-Free: +1 855-5
 52-4463  Meeting PIN: 8536 07 5882\;\;\;\;
 \;\;One-click Mobile Dial-in (United States (1)): +1\;\;
 \;\;\;\;206-462-5569\,\,8536075882#\;
 \;\;\;\;\;International: https://chime.aws/dia
 linnumbers/">https://chime.aws/dialinnumbers/\;\;\;&
 nbsp\;\;\;-\;\;\;Agenda:\;\;
 \;- TBDPlease feel free to add agenda items to hangout wik
 i page\;https://cwiki.apache.org/confluence/display/MXNET/M
 eetups+and+Hangouts#Meetups+and+Hangouts-2018Aug">https://cwiki.apache.org/
 confluence/display/MXNET/Meetups+and+Hangouts#Meetups+and+Hangouts-2018Aug<
 /a>\;
LAST-MODIFIED:20180726T203036Z
LOCATION:
SEQUENCE:4
STATUS:CANCELLED
SUMMARY:MXNet hangout (II / Americas)
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics


Pylint Undefined variable/name error

2018-07-26 Thread Vandana Kannan
Hi All,

On enabling the option "undefined-variable" in pylint (in pylintrc) and
executing on the latest code, 52 errors show up (most of them from the
example folder). These could lead to Python NameError at runtime. The
errors are documented in
https://github.com/apache/incubator-mxnet/issues/11904.

Currently, this Pylint option is disabled in CI and pylint is not executed
on the example folder.

Would it be a good idea to enable the option in CI to catch these errors,
and in the meantime, fix the backlog?

Thanks,
Vandana


Updated invitation: MXNet hangout (II / Americas) @ Thu Aug 2, 2018 02:00 - 03:00 (CEST) (dev@mxnet.incubator.apache.org)

2018-07-26 Thread pedro . larroy . lists
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20180802T00Z
DTEND:20180802T01Z
DTSTAMP:20180726T202749Z
ORGANIZER;CN=Pedro Larroy:mailto:pedro.larroy.li...@gmail.com
UID:4fi8kbc55k49bucunfs3c64...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dev@mxnet.incubator.apache.org;X-NUM-GUESTS=0:mailto:d...@mxnet.incu
 bator.apache.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Pedro Larroy;X-NUM-GUESTS=0:mailto:pedro.larroy.li...@gmail.com
CREATED:20180726T202240Z
DESCRIPTION:Invitation in behalf of Steffen Rochel:https://
 lists.apache.org/thread.html/f0a2677bf5f34c051b1d1701558895f2752e1def00de3c
 065c017a09@%3Cdev.mxnet.apache.org%3EThis time with the right t
 ime and timezone.\;\;\;Dial in instructions:
 \;\;\;-\;\;\;\;\;\;https://chime.aws/8536075882;>https://chime.aws/8536075882\;\;\;\;\;\;Meeting ID: 8536 07 5882
 \;\;\;\;\;\;United States Toll-Free: +1 855-5
 52-4463  Meeting PIN: 8536 07 5882\;\;\;\;
 \;\;One-click Mobile Dial-in (United States (1)): +1\;\;
 \;\;\;\;206-462-5569\,\,8536075882#\;
 \;\;\;\;\;International: https://chime.aws/dia
 linnumbers/">https://chime.aws/dialinnumbers/\;\;\;&
 nbsp\;\;\;-\;\;\;Agenda:\;\;
 \;- TBDPlease feel free to add agenda items to hangout wik
 i page\;https://cwiki.apache.org/confluence/display/MXNET/M
 eetups+and+Hangouts#Meetups+and+Hangouts-2018Aug">https://cwiki.apache.org/
 confluence/display/MXNET/Meetups+and+Hangouts#Meetups+and+Hangouts-2018Aug<
 /a>\;\n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 :~:~:~:~:~:~:~:~::~:~::-\nPlease do not edit this section of the descriptio
 n.\n\nView your event at https://www.google.com/calendar/event?action=VIEW;
 eid=NGZpOGtiYzU1azQ5YnVjdW5mczNjNjRsbmcgZGV2QG14bmV0LmluY3ViYXRvci5hcGFjaGU
 ub3Jn=MjgjcGVkcm8ubGFycm95Lmxpc3RzQGdtYWlsLmNvbTA0ODlkZGQ5NmVkYzhlYzAzM
 jMwODI0MDAwOWI0YjMxODRmYTgyMTU=Europe%2FBerlin=en=0.\n-::~:~::~:~
 :~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::
 -
LAST-MODIFIED:20180726T202749Z
LOCATION:
SEQUENCE:3
STATUS:CONFIRMED
SUMMARY:MXNet hangout (II / Americas)
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics


Re: Pylint Undefined variable/name error

2018-07-26 Thread Hagay Lupesko
+1 - thanks Vandana!

On Thu, Jul 26, 2018 at 8:05 PM sandeep krishnamurthy <
sandeep.krishn...@gmail.com> wrote:

> Thanks Vandana for picking up this issue. I think this is important to be
> fixed and enabled in CI. Please let us know effort required to fix these
> issues and we all can jump in and help you.
>
> On Thu, Jul 26, 2018, 7:27 PM Vandana Kannan  wrote:
>
> > Hi All,
> >
> > On enabling the option "undefined-variable" in pylint (in pylintrc) and
> > executing on the latest code, 52 errors show up (most of them from the
> > example folder). These could lead to Python NameError at runtime. The
> > errors are documented in
> > https://github.com/apache/incubator-mxnet/issues/11904.
> >
> > Currently, this Pylint option is disabled in CI and pylint is not
> executed
> > on the example folder.
> >
> > It might be better to enable this option in CI to catch these errors
> early
> > on, and also work on fixing the errors. Any thoughts/suggestions?
> >
> > Thanks,
> > Vandana
> >
>


Re: Pylint Undefined variable/name error

2018-07-26 Thread sandeep krishnamurthy
Thanks Vandana for picking up this issue. I think this is important to be
fixed and enabled in CI. Please let us know effort required to fix these
issues and we all can jump in and help you.

On Thu, Jul 26, 2018, 7:27 PM Vandana Kannan  wrote:

> Hi All,
>
> On enabling the option "undefined-variable" in pylint (in pylintrc) and
> executing on the latest code, 52 errors show up (most of them from the
> example folder). These could lead to Python NameError at runtime. The
> errors are documented in
> https://github.com/apache/incubator-mxnet/issues/11904.
>
> Currently, this Pylint option is disabled in CI and pylint is not executed
> on the example folder.
>
> It might be better to enable this option in CI to catch these errors early
> on, and also work on fixing the errors. Any thoughts/suggestions?
>
> Thanks,
> Vandana
>


Pylint Undefined variable/name error

2018-07-26 Thread Vandana Kannan
Hi All,

On enabling the option "undefined-variable" in pylint (in pylintrc) and 
executing on the latest code, 52 errors show up (most of them from the example 
folder). These could lead to Python NameError at runtime. The errors are 
documented in https://github.com/apache/incubator-mxnet/issues/11904. 

Currently, this Pylint option is disabled in CI and pylint is not executed on 
the example folder.

It might be better to enable this option in CI to catch these errors early on, 
and also work on fixing the errors. Any thoughts/suggestions?

Thanks,
Vandana


Re: Release blocker: non-determinstic forward in gluon

2018-07-26 Thread Sheng Zha
Dear users and developers of Apache MXNet (Incubating),

Thanks to Tong's dedication, the root cause for this issue was identified
to be instability in OpenBLAS's latest stable version 0.3.1. For details,
see Tong's comment

.

Since both the nightly build and the 1.2.1 wheels are affected, we
recommend that we stay on OpenBLAS last known stable version 0.2.20 that
we've been using. I will assume lazy consensus and prepare the fix
(1.2.1.post0).

-sz

On Tue, Jul 24, 2018 at 3:35 PM, Tong He  wrote:

> Recently there's an issue regarding the inconsistent result from gluon
> forward:
>
> https://github.com/apache/incubator-mxnet/issues/11853
>
> Given a constant input image and loaded pretrained parameters, we expect a
> deterministic output from arbitrary repeats of forwards. However from the
> issue I see that the forwarded result is non-determinstic. It is harmful as
> it makes the results from experments/benchmarks/inference meaningless.
>
> Therefore I propose to block the 1.3 release before it gets resolved.
>


Re: Release plan - MXNET 1.3

2018-07-26 Thread Pedro Larroy
I would like to get these PR merged:

https://github.com/apache/incubator-mxnet/pull/11636
https://github.com/apache/incubator-mxnet/pull/11562

How much longer until the code freeze?

On Thu, Jul 26, 2018 at 1:44 AM Roshani Nagmote 
wrote:

> Hi all,
>
> PRs waiting to be merged for 1.3 release:
> https://github.com/apache/incubator-mxnet/pull/11325
>
> Are there any other PRs waiting to get merged? Please let me know.
>
> Release blocker issue:
> https://github.com/apache/incubator-mxnet/issues/11853
>
> @Marco, @Kellen, Thanks for bringing up the important topic. I agree with
> you and we(internal Amazon team) will be working on fixing the disabled
> tests.
> Currently, my colleague, Hao Jin is working on compiling the list of
> disabled tests and leading the effort to fix them in the next few days.
>
> Thanks,
> Roshani
>
> On Mon, Jul 23, 2018 at 6:39 PM kellen sunderland <
> kellen.sunderl...@gmail.com> wrote:
>
> > Thanks again for organizing Roshani.  I believe the TensorRT work is
> ready
> > for a merge.  Thanks to Marek and all the NVIDIA people for iterating on
> > it.  If possible could a committer review, make sure it meets their
> > expectations and then merge?  PR is here:
> > https://github.com/apache/incubator-mxnet/pull/11325
> >
> > To Marco's point.  I'd recommend we review some of those disabled tests
> and
> > see how likely they are to affect users before we cut a release.  Many of
> > them are obviously not too important from a user's point of view (e.g.
> > downloading a sometimes-offline image in a test).  One idea would be to
> try
> > and address as many of the customer impacting issues as possible between
> > code freeze and the RC0 vote.
> >
> > On Mon, Jul 23, 2018 at 1:23 PM Marco de Abreu
> >  wrote:
> >
> > > Hello Roshani,
> > >
> > > frequent releases are good and I'm supportive for this in general in
> > order
> > > to provide our users with the latest features and improvements. But at
> > the
> > > moment, I'm slightly concerned about the test coverage due to [1]. I
> want
> > > us to be conscious about cutting a release even though not all tests
> are
> > > enabled (29 disabled tests [2] as of today). However, I acknowledge
> that
> > we
> > > have improved by a lot lately thanks to everybody participating and
> > leading
> > > the efforts around improving flaky tests. From a retrospective point of
> > > view, we could say that these efforts have actually revealed some quite
> > > interesting bugs and thus the time was well spent and yielded good
> > results.
> > >
> > > What does the community think about making another sprint of
> improvements
> > > around tests followed up by a period of 1-2 weeks during which we
> observe
> > > the failures closely to ensure that no critical paths are impacted? If
> we
> > > are in a good shape by then, we could continue the release process and
> at
> > > the same time have the advantage of giving contributors more lead time
> to
> > > finish their work to ensure it gets into the release in the desired
> > > quality.
> > >
> > > Again, thanks to everybody for their efforts during the last weeks to
> > > improve the usability and stability of MXNet. This is great community
> > > effort and a good example of a community working together towards a
> > unified
> > > goal!
> > >
> > > Best regards,
> > > Marco
> > >
> > > [1]:
> > >
> > >
> >
> https://lists.apache.org/thread.html/d6d81401de796a96677a112d6cd0b074b01f46564194ea89b86c6a3e@%3Cdev.mxnet.apache.org%3E
> > > [2]:
> > >
> > >
> >
> https://github.com/apache/incubator-mxnet/issues?q=is%3Aopen+is%3Aissue+label%3A%22Disabled+test%22
> > >
> > > On Mon, Jul 23, 2018 at 8:34 PM Roshani Nagmote <
> > roshaninagmo...@gmail.com
> > > >
> > > wrote:
> > >
> > > > Hi all,
> > > >
> > > > As mentioned before, code freeze date is today July 23rd. Please try
> to
> > > get
> > > > your ongoing PRs merged by today.
> > > > Please let me know if there are any concerns or need more time.
> > > >
> > > > Thanks,
> > > > Roshani
> > > >
> > > > On Thu, Jul 19, 2018 at 1:16 PM Anirudh Acharya <
> anirudhk...@gmail.com
> > >
> > > > wrote:
> > > >
> > > > > @sandeep krishnamurthy  the bug fixes
> > in
> > > > the
> > > > > R-package is something we have just begun, there will not be
> anything
> > > > > significant to announce before the v1.3 code freeze.
> > > > >
> > > > > On Wed, Jul 18, 2018 at 10:08 PM Steffen Rochel <
> > > steffenroc...@gmail.com
> > > > >
> > > > > wrote:
> > > > >
> > > > > > To make it easier to find the discussions related to project
> > > proposals
> > > > I
> > > > > > added a column with a link to the thread on dev@ for most
> > projects.
> > > > > > Appreciate for the project owners to fill in the blanks and to
> > check
> > > > > that I
> > > > > > got the right threads.
> > > > > >
> > > > > > Regards,
> > > > > > Steffen
> > > > > >
> > > > > > On Wed, Jul 18, 2018 at 7:11 PM Roshani Nagmote <
> > > > > roshaninagmo...@gmail.com
> > > > > > >
> > > > > > 

Invitation: MXNet hangout II / Americas (fixed time & TZ) @ Thu Aug 2, 2018 02:00 - 03:00 (CEST) (dev@mxnet.incubator.apache.org)

2018-07-26 Thread Pedro Larroy
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20180802T00Z
DTEND:20180802T01Z
DTSTAMP:20180726T203140Z
ORGANIZER;CN=Pedro Larroy:mailto:pedro.larroy.li...@gmail.com
UID:3rod9ia8d7pru4f2plfp1js...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dev@mxnet.incubator.apache.org;X-NUM-GUESTS=0:mailto:d...@mxnet.incu
 bator.apache.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Pedro Larroy;X-NUM-GUESTS=0:mailto:pedro.larroy.li...@gmail.com
CREATED:20180726T203139Z
DESCRIPTION:\n\n\n\nInvitation in behalf of Steffen Rochel:\n\n\nhttps://li
 sts.apache.org/thread.html/f0a2677bf5f34c051b1d1701558895f2752e1def00de3c06
 5c017a09@%3Cdev.mxnet.apache.org%3E\n\n\nThis time with the right time and 
 timezone.\n\n\n   Dial in instructions:\n   -\n\n  https://chime.aws/85
 36075882\n\n  Meeting ID: 8536 07 5882\n\n  United States Toll-Free
 : +1 855-552-4463 Meeting PIN: 8536 07 5882\n\n  One-click Mobile Dial-
 in (United States (1)): +1\n  206-462-5569\,\,8536075882#\n\n  Inte
 rnational: https://chime.aws/dialinnumbers/\n  -\n\n   Agenda:\n   - TB
 D\n\n\nPlease feel free to add agenda items to hangout wiki page\n\n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\nPlease do not edit this section of the d
 escription.\n\nView your event at https://www.google.com/calendar/event?act
 ion=VIEW=M3JvZDlpYThkN3BydTRmMnBsZnAxanNscjkgZGV2QG14bmV0LmluY3ViYXRvci
 5hcGFjaGUub3Jn=MjgjcGVkcm8ubGFycm95Lmxpc3RzQGdtYWlsLmNvbWViZGU0ZDViN2Uw
 NDQ1YTFkM2Y2MTRiYTVmNmZkMjdjNzM1MzQxMGQ=Europe%2FBerlin=en=1.\n-:
 :~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 :~::~:~::-
LAST-MODIFIED:20180726T203139Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:MXNet hangout II / Americas (fixed time & TZ)
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics


Invitation: MXNet hangout (II / Americas) @ Thu Aug 2, 2018 02:00 - 03:00 (CEST) (dev@mxnet.incubator.apache.org)

2018-07-26 Thread Pedro Larroy
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20180802T00Z
DTEND:20180802T01Z
DTSTAMP:20180726T202241Z
ORGANIZER;CN=Pedro Larroy:mailto:pedro.larroy.li...@gmail.com
UID:4fi8kbc55k49bucunfs3c64...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dev@mxnet.incubator.apache.org;X-NUM-GUESTS=0:mailto:d...@mxnet.incu
 bator.apache.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Pedro Larroy;X-NUM-GUESTS=0:mailto:pedro.larroy.li...@gmail.com
CREATED:20180726T202240Z
DESCRIPTION:\n\n\n\n\n\n\n\nFixed time...\n\n\n   Dial in instructions:\n  
  -\n\n  https://chime.aws/8536075882\n\n  Meeting ID: 8536 07 5882\
 n\n  United States Toll-Free: +1 855-552-4463  Meeting PIN: 8536 07 588
 2\n\n  One-click Mobile Dial-in (United States (1)): +1\n  206-462-
 5569\,\,8536075882#\n\n  International: https://chime.aws/dialinnumbers
 /\n  -\n\n   Agenda:\n   - TBD\n\n\nPlease feel free to add agenda item
 s to hangout wiki page\n\n\n-::~:~::~:~:~:~:~:~:~
 :~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\nPlease 
 do not edit this section of the description.\n\nView your event at https://
 www.google.com/calendar/event?action=VIEW=NGZpOGtiYzU1azQ5YnVjdW5mczNjN
 jRsbmcgZGV2QG14bmV0LmluY3ViYXRvci5hcGFjaGUub3Jn=MjgjcGVkcm8ubGFycm95Lmx
 pc3RzQGdtYWlsLmNvbTA0ODlkZGQ5NmVkYzhlYzAzMjMwODI0MDAwOWI0YjMxODRmYTgyMTU
 z=Europe%2FBerlin=en=1.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20180726T202240Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:MXNet hangout (II / Americas)
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics


Re: How should MXNet treat nan values?

2018-07-26 Thread Leonard Lausen
Thanks to everyone who made their opinion known. So far the consensus
is that any nan handling in MXNet should not affect performance, at
least not by default.

This still leaves the question open if we should aim for documenting the
behavior of MXNet operators under presence of nan values. For example,
should we include a sentence in the argmax and topk documentation?
Should the 1.3 release notes note the changed behavior of topk?

So far this has not been done. Instead any change of operator behavior
with respect to nan values is treated as implementation change that is
not worth noting to the user.

As this can decrease user experience, I advocate for documenting the
current behavior and possible future changes.

In case there are no objections, is there any way to edit the changelog
for the upcoming release?


Re: ApacheCon is just 60 days away. Are you ready?

2018-07-26 Thread Naveen Swamy
I suggest to add it as a temporary banner on the home page to let it get
lot more traffic
+1 for 3)

Can we assume Lazy consensus after 72 hours(Sat+Sunday = 24 hrs) have
passed if there are no objections to this?

-Naveen

On Thu, Jul 26, 2018 at 11:10 AM, Aaron Markham 
wrote:

> Floating a couple ideas about this...
> 1) could add it to the home page in the space to the right of "learn more".
>
> 2) could add it to a news page or events page (after creating said page)
>
> 3) should definitely add it to the meetups and events page in the wiki
>
> On Jul 26, 2018 10:16, "Naveen Swamy"  wrote:
>
> Hi All, ApacheCon Organizers are requesting to spread the word about
> ApacheCon. What do you guys think of adding the banner(temporarily) on
> Apache MXNet website?
>
> -- Forwarded message --
> From: Rich Bowen 
> Date: Thu, Jul 26, 2018 at 6:00 AM
> Subject: ApacheCon is just 60 days away. Are you ready?
> To: nsw...@apache.org
>
>
> A few things you need to do before you pack your bags
> View this email in your browser
> <
> https://mailchi.mp/0e024bf0b8da/apachecon-is-just-60-days-away-are-you-
> ready?e=a7dd8ac6e6
> >
> ApacheCon is just 60 days away!
>
> Thanks again for speaking at ApacheCon. This event can't happen without
> you, and we're enormously grateful for your hard work and preparation.
>
> We need some help in these last two months leading up to the event. You are
> the most effective spokesperson for the event - people are coming because
> of you.
>
> Here's what you can do to help spread the word.
>
> * Follow us on Twitter - @apachecon
> <
> https://apachecon.us17.list-manage.com/track/click?u=
> 40e225eb9c5953fb65d73f7bd=cc26150dad=a7dd8ac6e6
> >
> - and amplify the messages that we're sending there.
>
> * Tell your friends, coworkers, and, most importantly, the people involved
> with the Apache projects you're speaking about (ie, your dev@ and users@
> mailing lists), that you'll be speaking, and encourage them to come.
>
> * Put one (or more!) of our ad banners on your website, and link it to
> http://apachecon.com/acna18
> <
> https://apachecon.us17.list-manage.com/track/click?u=
> 40e225eb9c5953fb65d73f7bd=5ff3820cd9=a7dd8ac6e6
> >
> . You can find those banners here: http://www.apachecon.com/
> acna18/banners/
> <
> https://apachecon.us17.list-manage.com/track/click?u=
> 40e225eb9c5953fb65d73f7bd=86cfcc5a6a=a7dd8ac6e6
> >
> These are suitable for your personal site, your company sites, and your
> project sites.
>
> * Register! Yes, I know, most of you have registered, but a few of you
> still haven't. Use the speaker registration code we sent you earlier, or
> contact us - h...@apachecon.com - if you've lost it. Register here
> <
> https://apachecon.us17.list-manage.com/track/click?u=
> 40e225eb9c5953fb65d73f7bd=d3c9557e38=a7dd8ac6e6
> >
> .
>
> * Book your hotel room. The hotel block closes on August 24th. Details
> here: http://apachecon.com/acna18/venue.html
> <
> https://apachecon.us17.list-manage.com/track/click?u=
> 40e225eb9c5953fb65d73f7bd=ec041c990e=a7dd8ac6e6
> >
>
>
> Finally, I know a few of you have, unfortunately, had to drop your speaking
> slots. If that's you, I apologize for sending you this message - although
> we would still appreciate any promotion you can do on our behalf. But
> please see the unsubscribe link at the bottom if you're not interested in
> hearing from us any more.
>
> Thanks again, and we'll see you in Montreal!
>
> Rich, for the ApacheCon Planners.
> <
> https://apachecon.us17.list-manage.com/track/click?u=
> 40e225eb9c5953fb65d73f7bd=1831ad868f=a7dd8ac6e6
> >
> <
> https://apachecon.us17.list-manage.com/track/click?u=
> 40e225eb9c5953fb65d73f7bd=6aa75aa21b=a7dd8ac6e6
> >
> <
> https://apachecon.us17.list-manage.com/track/click?u=
> 40e225eb9c5953fb65d73f7bd=89b0fe9629=a7dd8ac6e6
> >
> *Copyright © 2018 The Apache Software Foundation, All rights reserved.*
> You're on my list of speakers for ApacheCon North America 2018
>
> *Our mailing address is:*
> The Apache Software Foundation
> 3864 Grassy Creek Dr
> <
> https://maps.google.com/?q=3864+Grassy+Creek+Dr+
> Lexington+,++KY+40514=gmail=g
> >
> Lexington
> <
> https://maps.google.com/?q=3864+Grassy+Creek+Dr+
> Lexington+,++KY+40514=gmail=g
> >,
> <
> https://maps.google.com/?q=3864+Grassy+Creek+Dr+
> Lexington+,++KY+40514=gmail=g
> >
> KY
> <
> https://maps.google.com/?q=3864+Grassy+Creek+Dr+
> Lexington+,++KY+40514=gmail=g
> >
> 40514
> <
> https://maps.google.com/?q=3864+Grassy+Creek+Dr+
> Lexington+,++KY+40514=gmail=g
> >
> -1059
>
> Add us to your address book
>  apachecon.us17.list-manage.com/vcard?u=40e225eb9c5953fb65d73f7bd=
> 79c3a26c13
> >
>
>
> Want to change how you receive these emails?
> You can update your preferences
> <
> https://apachecon.us17.list-manage.com/profile?u=
> 40e225eb9c5953fb65d73f7bd=79c3a26c13=a7dd8ac6e6
> >
> or unsubscribe from this list
> <
> https://apachecon.us17.list-manage.com/unsubscribe?u=
> 

Request to join developing PR Best practice guidelines

2018-07-26 Thread Naveen Swamy
Hi All,

As a part of my job I am looking for ways to improve PR response time,
participation, and PR quality. On asking a few committers/contributors near
by(Andrea, Hagay, Mu Li, Steffen) and their feedback was that some PRs do
not have enough details and only those who collaborate closely can review
the PR. This could be because developers for various reasons, they might
forget due to time-pressure, other priorities and the current guidelines
might not be(IMO) enough.
I would like to volunteer to enhance the existing PR Checklist created by
the community members, and I request members to join this effort so we can
collaborate and come up with a good set of guidelines and propose here on
the dev@, please reach out to me on Slack or here if you are interested to
contribute.

Currently I am thinking of splitting this effort into
1) PR Best Practices for authors.
2) PR Checklist for reviewers.
3) Coding Guidelines.

Thanks, Naveen


Re: ApacheCon is just 60 days away. Are you ready?

2018-07-26 Thread Aaron Markham
Floating a couple ideas about this...
1) could add it to the home page in the space to the right of "learn more".

2) could add it to a news page or events page (after creating said page)

3) should definitely add it to the meetups and events page in the wiki

On Jul 26, 2018 10:16, "Naveen Swamy"  wrote:

Hi All, ApacheCon Organizers are requesting to spread the word about
ApacheCon. What do you guys think of adding the banner(temporarily) on
Apache MXNet website?

-- Forwarded message --
From: Rich Bowen 
Date: Thu, Jul 26, 2018 at 6:00 AM
Subject: ApacheCon is just 60 days away. Are you ready?
To: nsw...@apache.org


A few things you need to do before you pack your bags
View this email in your browser
<
https://mailchi.mp/0e024bf0b8da/apachecon-is-just-60-days-away-are-you-ready?e=a7dd8ac6e6
>
ApacheCon is just 60 days away!

Thanks again for speaking at ApacheCon. This event can't happen without
you, and we're enormously grateful for your hard work and preparation.

We need some help in these last two months leading up to the event. You are
the most effective spokesperson for the event - people are coming because
of you.

Here's what you can do to help spread the word.

* Follow us on Twitter - @apachecon
<
https://apachecon.us17.list-manage.com/track/click?u=40e225eb9c5953fb65d73f7bd=cc26150dad=a7dd8ac6e6
>
- and amplify the messages that we're sending there.

* Tell your friends, coworkers, and, most importantly, the people involved
with the Apache projects you're speaking about (ie, your dev@ and users@
mailing lists), that you'll be speaking, and encourage them to come.

* Put one (or more!) of our ad banners on your website, and link it to
http://apachecon.com/acna18
<
https://apachecon.us17.list-manage.com/track/click?u=40e225eb9c5953fb65d73f7bd=5ff3820cd9=a7dd8ac6e6
>
. You can find those banners here: http://www.apachecon.com/acna18/banners/
<
https://apachecon.us17.list-manage.com/track/click?u=40e225eb9c5953fb65d73f7bd=86cfcc5a6a=a7dd8ac6e6
>
These are suitable for your personal site, your company sites, and your
project sites.

* Register! Yes, I know, most of you have registered, but a few of you
still haven't. Use the speaker registration code we sent you earlier, or
contact us - h...@apachecon.com - if you've lost it. Register here
<
https://apachecon.us17.list-manage.com/track/click?u=40e225eb9c5953fb65d73f7bd=d3c9557e38=a7dd8ac6e6
>
.

* Book your hotel room. The hotel block closes on August 24th. Details
here: http://apachecon.com/acna18/venue.html
<
https://apachecon.us17.list-manage.com/track/click?u=40e225eb9c5953fb65d73f7bd=ec041c990e=a7dd8ac6e6
>


Finally, I know a few of you have, unfortunately, had to drop your speaking
slots. If that's you, I apologize for sending you this message - although
we would still appreciate any promotion you can do on our behalf. But
please see the unsubscribe link at the bottom if you're not interested in
hearing from us any more.

Thanks again, and we'll see you in Montreal!

Rich, for the ApacheCon Planners.
<
https://apachecon.us17.list-manage.com/track/click?u=40e225eb9c5953fb65d73f7bd=1831ad868f=a7dd8ac6e6
>
<
https://apachecon.us17.list-manage.com/track/click?u=40e225eb9c5953fb65d73f7bd=6aa75aa21b=a7dd8ac6e6
>
<
https://apachecon.us17.list-manage.com/track/click?u=40e225eb9c5953fb65d73f7bd=89b0fe9629=a7dd8ac6e6
>
*Copyright © 2018 The Apache Software Foundation, All rights reserved.*
You're on my list of speakers for ApacheCon North America 2018

*Our mailing address is:*
The Apache Software Foundation
3864 Grassy Creek Dr
<
https://maps.google.com/?q=3864+Grassy+Creek+Dr+Lexington+,++KY+40514=gmail=g
>
Lexington
<
https://maps.google.com/?q=3864+Grassy+Creek+Dr+Lexington+,++KY+40514=gmail=g
>,
<
https://maps.google.com/?q=3864+Grassy+Creek+Dr+Lexington+,++KY+40514=gmail=g
>
KY
<
https://maps.google.com/?q=3864+Grassy+Creek+Dr+Lexington+,++KY+40514=gmail=g
>
40514
<
https://maps.google.com/?q=3864+Grassy+Creek+Dr+Lexington+,++KY+40514=gmail=g
>
-1059

Add us to your address book



Want to change how you receive these emails?
You can update your preferences
<
https://apachecon.us17.list-manage.com/profile?u=40e225eb9c5953fb65d73f7bd=79c3a26c13=a7dd8ac6e6
>
or unsubscribe from this list
<
https://apachecon.us17.list-manage.com/unsubscribe?u=40e225eb9c5953fb65d73f7bd=79c3a26c13=a7dd8ac6e6=c7faa91e41
>.


[image: Email Marketing Powered by MailChimp]
<
http://www.mailchimp.com/monkey-rewards/?utm_source=freemium_newsletter_medium=email_campaign=monkey_rewards=40e225eb9c5953fb65d73f7bd=1
>


Fwd: ApacheCon is just 60 days away. Are you ready?

2018-07-26 Thread Naveen Swamy
Hi All, ApacheCon Organizers are requesting to spread the word about
ApacheCon. What do you guys think of adding the banner(temporarily) on
Apache MXNet website?

-- Forwarded message --
From: Rich Bowen 
Date: Thu, Jul 26, 2018 at 6:00 AM
Subject: ApacheCon is just 60 days away. Are you ready?
To: nsw...@apache.org


A few things you need to do before you pack your bags
View this email in your browser

ApacheCon is just 60 days away!

Thanks again for speaking at ApacheCon. This event can't happen without
you, and we're enormously grateful for your hard work and preparation.

We need some help in these last two months leading up to the event. You are
the most effective spokesperson for the event - people are coming because
of you.

Here's what you can do to help spread the word.

* Follow us on Twitter - @apachecon

- and amplify the messages that we're sending there.

* Tell your friends, coworkers, and, most importantly, the people involved
with the Apache projects you're speaking about (ie, your dev@ and users@
mailing lists), that you'll be speaking, and encourage them to come.

* Put one (or more!) of our ad banners on your website, and link it to
http://apachecon.com/acna18

. You can find those banners here: http://www.apachecon.com/acna18/banners/

These are suitable for your personal site, your company sites, and your
project sites.

* Register! Yes, I know, most of you have registered, but a few of you
still haven't. Use the speaker registration code we sent you earlier, or
contact us - h...@apachecon.com - if you've lost it. Register here

.

* Book your hotel room. The hotel block closes on August 24th. Details
here: http://apachecon.com/acna18/venue.html



Finally, I know a few of you have, unfortunately, had to drop your speaking
slots. If that's you, I apologize for sending you this message - although
we would still appreciate any promotion you can do on our behalf. But
please see the unsubscribe link at the bottom if you're not interested in
hearing from us any more.

Thanks again, and we'll see you in Montreal!

Rich, for the ApacheCon Planners.



*Copyright © 2018 The Apache Software Foundation, All rights reserved.*
You're on my list of speakers for ApacheCon North America 2018

*Our mailing address is:*
The Apache Software Foundation
3864 Grassy Creek Dr

Lexington
,

KY

40514

-1059

Add us to your address book



Want to change how you receive these emails?
You can update your preferences

or unsubscribe from this list
.


[image: Email Marketing Powered by MailChimp]



Re: Publish MXNet images to DockerHub

2018-07-26 Thread kellen sunderland
Awesome.  Thanks Meghna.

On Wed, Jul 25, 2018, 11:08 PM Meghna Baijal 
wrote:

> Hi Anirudh,
> Thanks for bringing this up.
> The Python Images are being actively released for each MXNet version. Until
> last release I was using the script Mu has pointed out but from 1.2.1 I
> replaced these dockerfiles to use the pip binaries instead of building from
> source.
> Images for all other language bindings were being released only until MXNet
> 0.12.0 since they were not being maintained. I think there are a couple of
> github issues open to track broken dockerfiles.
>
> Kellen,
>
> I can help you publish the docker images to dockerhub.
>
>
> Thanks,
>
> Meghna Baijal
>
>
>
>
> On Tue, Jul 24, 2018 at 4:45 PM Anirudh Acharya 
> wrote:
>
> > Yes that would be good. Also I just noticed that in the Installation
> > instructions page only python has docker image installation instruction
> > here -
> >
> >
> http://mxnet.incubator.apache.org/install/index.html?platform=Linux=Python=CPU
> > Similar instructions need to be there for other bindings too.
> >
> > On Tue, Jul 24, 2018 at 4:04 PM kellen sunderland <
> > kellen.sunderl...@gmail.com> wrote:
> >
> > > I was actually interested in pushing a version of MXNet with TensorRT
> > > enabled some time in the next few weeks just so that people can
> > experiment
> > > with the feature without worrying about installing the right protoc and
> > > onnx versions.  If people here think it's a good idea I can open a PR
> > with
> > > a runtime-docker folder with the intent that this work could be a
> > template
> > > for others who want to contribute runtime Dockerfiles?  If a few
> > > contributors do put together an Dockerfile with TensorRT enabled, would
> > it
> > > be possible to get that image pushed to the MXNet Dockerhub repo by a
> > > committer?
> > >
> > > On Sun, Jul 22, 2018 at 3:57 PM Anirudh Acharya  >
> > > wrote:
> > >
> > > > @Naveen No, I meant in general, for all bindings. Irrespective of
> > whether
> > > > we use a package management repository, being able to pull an image
> > from
> > > > docker hub would be convenient for anyone wanting to get started on
> > MXNet
> > > > or run services( as Kellen said).
> > > >
> > > >
> > > > On Sun, Jul 22, 2018 at 11:20 AM kellen sunderland <
> > > > kellen.sunderl...@gmail.com> wrote:
> > > >
> > > > > I think it's a good idea Anirudh.  It should help users easily get
> > > MXNet
> > > > up
> > > > > and running whether they're running services, following tutorials,
> > etc.
> > > > >
> > > > > On Sun, Jul 22, 2018 at 8:10 AM Naveen Swamy 
> > > wrote:
> > > > >
> > > > > > I don't think we need for JVM languages, they have a good
> > dependency
> > > > > > management through Maven Central. We weren't publishing regularly
> > to
> > > > > Maven,
> > > > > > now we do.
> > > > > >
> > > > > > Anirudh, I am guessing you are interested docker for R language,
> If
> > > > the R
> > > > > > packages were published to CRAN do you still see a need for
> docker
> > ?
> > > > > Could
> > > > > > you elaborate how this would be helpful and easy if they were to
> > use
> > > > > other
> > > > > > packages in CRAN?
> > > > > >
> > > > > > On Sat, Jul 21, 2018 at 10:51 PM, Anirudh Acharya <
> > > > anirudhk...@gmail.com
> > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Yes, correct cu90 is indeed there, thanks for pointing it.
> > > > > > >
> > > > > > > So the question, should we be publishing to Docker Hub as part
> of
> > > the
> > > > > > > release process so that bindings other than python are also
> > > published
> > > > > and
> > > > > > > there is a policy on what cuda versions we publish?
> > > > > > >
> > > > > > >
> > > > > > > Thanks
> > > > > > > ANirudh
> > > > > > >
> > > > > > > On Sat, Jul 21, 2018 at 9:56 PM Mu Li 
> > wrote:
> > > > > > >
> > > > > > > > cu90 and cu90mkl are also available, see
> > > > > > > > https://hub.docker.com/r/mxnet/python/tags/
> > > > > > > >
> > > > > > > > On Sat, Jul 21, 2018 at 9:51 PM, Anirudh Acharya <
> > > > > > anirudhk...@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > The python binding that is actively maintained is
> > > > > > > > >
> > > > > > > > > mxnet-mkl  1.2.1
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Other versions that use CUDA like mxnet-cu and
> > > > mxnet-cumkl
> > > > > > are
> > > > > > > > not
> > > > > > > > > actively maintained.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > -
> > > > > > > > >
> > > > > > > > > Anirudh
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Sat, Jul 21, 2018 at 9:09 PM Mu Li 
> > > > wrote:
> > > > > > > > >
> > > > > > > > > > Surprisingly only the python binding is actively
> > maintained.
> > > I
> > > > > > > remember
> > > > > > > > > we
> > > > > > > > > > can easily push all bindings into docker hub through the
> > > script
> > > > > in
> > > > > > > > > >
> > 

Re: Publish MXNet images to DockerHub

2018-07-26 Thread Meghna Baijal
Hi Anirudh,
Thanks for bringing this up.
The Python Images are being actively released for each MXNet version. Until
last release I was using the script Mu has pointed out but from 1.2.1 I
replaced these dockerfiles to use the pip binaries instead of building from
source.
Images for all other language bindings were being released only until MXNet
0.12.0 since they were not being maintained. I think there are a couple of
github issues open to track broken dockerfiles.

Kellen,

I can help you publish the docker images to dockerhub.


Thanks,

Meghna Baijal




On Tue, Jul 24, 2018 at 4:45 PM Anirudh Acharya 
wrote:

> Yes that would be good. Also I just noticed that in the Installation
> instructions page only python has docker image installation instruction
> here -
>
> http://mxnet.incubator.apache.org/install/index.html?platform=Linux=Python=CPU
> Similar instructions need to be there for other bindings too.
>
> On Tue, Jul 24, 2018 at 4:04 PM kellen sunderland <
> kellen.sunderl...@gmail.com> wrote:
>
> > I was actually interested in pushing a version of MXNet with TensorRT
> > enabled some time in the next few weeks just so that people can
> experiment
> > with the feature without worrying about installing the right protoc and
> > onnx versions.  If people here think it's a good idea I can open a PR
> with
> > a runtime-docker folder with the intent that this work could be a
> template
> > for others who want to contribute runtime Dockerfiles?  If a few
> > contributors do put together an Dockerfile with TensorRT enabled, would
> it
> > be possible to get that image pushed to the MXNet Dockerhub repo by a
> > committer?
> >
> > On Sun, Jul 22, 2018 at 3:57 PM Anirudh Acharya 
> > wrote:
> >
> > > @Naveen No, I meant in general, for all bindings. Irrespective of
> whether
> > > we use a package management repository, being able to pull an image
> from
> > > docker hub would be convenient for anyone wanting to get started on
> MXNet
> > > or run services( as Kellen said).
> > >
> > >
> > > On Sun, Jul 22, 2018 at 11:20 AM kellen sunderland <
> > > kellen.sunderl...@gmail.com> wrote:
> > >
> > > > I think it's a good idea Anirudh.  It should help users easily get
> > MXNet
> > > up
> > > > and running whether they're running services, following tutorials,
> etc.
> > > >
> > > > On Sun, Jul 22, 2018 at 8:10 AM Naveen Swamy 
> > wrote:
> > > >
> > > > > I don't think we need for JVM languages, they have a good
> dependency
> > > > > management through Maven Central. We weren't publishing regularly
> to
> > > > Maven,
> > > > > now we do.
> > > > >
> > > > > Anirudh, I am guessing you are interested docker for R language, If
> > > the R
> > > > > packages were published to CRAN do you still see a need for docker
> ?
> > > > Could
> > > > > you elaborate how this would be helpful and easy if they were to
> use
> > > > other
> > > > > packages in CRAN?
> > > > >
> > > > > On Sat, Jul 21, 2018 at 10:51 PM, Anirudh Acharya <
> > > anirudhk...@gmail.com
> > > > >
> > > > > wrote:
> > > > >
> > > > > > Yes, correct cu90 is indeed there, thanks for pointing it.
> > > > > >
> > > > > > So the question, should we be publishing to Docker Hub as part of
> > the
> > > > > > release process so that bindings other than python are also
> > published
> > > > and
> > > > > > there is a policy on what cuda versions we publish?
> > > > > >
> > > > > >
> > > > > > Thanks
> > > > > > ANirudh
> > > > > >
> > > > > > On Sat, Jul 21, 2018 at 9:56 PM Mu Li 
> wrote:
> > > > > >
> > > > > > > cu90 and cu90mkl are also available, see
> > > > > > > https://hub.docker.com/r/mxnet/python/tags/
> > > > > > >
> > > > > > > On Sat, Jul 21, 2018 at 9:51 PM, Anirudh Acharya <
> > > > > anirudhk...@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > The python binding that is actively maintained is
> > > > > > > >
> > > > > > > > mxnet-mkl  1.2.1
> > > > > > > >
> > > > > > > >
> > > > > > > > Other versions that use CUDA like mxnet-cu and
> > > mxnet-cumkl
> > > > > are
> > > > > > > not
> > > > > > > > actively maintained.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > -
> > > > > > > >
> > > > > > > > Anirudh
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Sat, Jul 21, 2018 at 9:09 PM Mu Li 
> > > wrote:
> > > > > > > >
> > > > > > > > > Surprisingly only the python binding is actively
> maintained.
> > I
> > > > > > remember
> > > > > > > > we
> > > > > > > > > can easily push all bindings into docker hub through the
> > script
> > > > in
> > > > > > > > >
> https://github.com/apache/incubator-mxnet/tree/master/docker
> > .
> > > > > > > > >
> > > > > > > > > On Sat, Jul 21, 2018 at 5:03 PM, Anirudh Acharya <
> > > > > > > anirudhk...@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Hi,
> > > > > > > > > >
> > > > > > > > > > Docker Hub( https://hub.docker.com/u/mxnet/ ) currently
> > > hosts
> > > > > > images
> > > > > > > > of
> > > >