Re: Discussing plans for next MXNet releases

[Sheng Zha]

Hi Hagay,

Thanks for taking the initiative. The proposed scope in this thread is in
my opinion too large to fit in a single thread, so I'd suggest that we
start separate threads for each individual release item. To elaborate on
the reasons based on each individual item:
- For 1.4.1 which is in the wiki page draft, I'd suggest refraining from
adding new features there since patch release should be about bug fixes.
- For 1.5, there are efforts such as AMP and general improvement for fp16
support in operators, quantization efforts, etc., that should be included.
I may have a bit more context on this so I'm happy to help initiate the
discussion.
- For 2.0, I think it would be more of a roadmap discussion at this stage.

I hope this makes sense. Would you mind starting a thread focusing on 1.4.1
patch release?

-sz


On Tue, Apr 2, 2019 at 5:06 PM Hagay Lupesko  wrote:

> Dear MXNet community,
>
> I wanted to initiate a discussion about the plan and scope for the next
> MXNet releases.
> I suggest we focus on three releases, and get the process going in
> parallel:
> (1) 1.4.1 - patch release on top of 1.4.0 to address some perf regressions
> and memory leaks I am aware of, such as the memory leak fixed on Scala [0
> ]. I went ahead and
> created a draft release proposal wiki [1
> <
> https://cwiki.apache.org/confluence/display/MXNET/%5BDRAFT+PROPOSAL%5D+Apache+MXNet+%28incubating%29+1.4.1+Release+Plan+and+Status
> >
> ].
> (2) 1.5.0 - a minor release to add new features introduced since 1.4.0
> release started (back in Nov 2018!), such as various performance
> improvements: aggregate SGD, in-place updates in optimizers, gpu support
> for image processing operators and many more features useful for MXNet’s
> users.
> (3) 2.0 - an exciting major release that will include major enhancements to
> MXNet.
>
> Timeframes will probably vary based on the scope. I think we should plan to
> start 1.4.1 release within a couple of weeks, 1.5.0 should target starting
> once we release 1.4.1, and 2.0 timeline is TBD - but such a major release
> will require more time to discuss and decide in the community.
>
> I was thinking to get started through:
> (1) Draft proposals on CWiki, where the community can add content and
> propose scope and features.
> (2) Setup online meetings, where anyone can dial into, from anywhere, where
> we will have a chance to discuss in voice+video.
> (3) With (1)+(2) have a scope and timeline that the community, in large,
> supports.
>
> Would be great to get the community's feedback and suggestions, and please
> reply if you would like to be involved in the effort of supporting the
> releases!
>
> MXNet is awesome, looking forward to working together to make it even
> better!
> Hagay
>
> [0] https://github.com/apache/incubator-mxnet/pull/14586
> [1]
>
> https://cwiki.apache.org/confluence/display/MXNET/%5BDRAFT+PROPOSAL%5D+Apache+MXNet+%28incubating%29+1.4.1+Release+Plan+and+Status
>

Re: Discussing plans for next MXNet releases

[Pedro Larroy]

Great initiative.

I would like to add the issue that tracks APIs that we would like to
break for 2.0 so we can take the chance to streamline and improve
customer facing code:

https://github.com/apache/incubator-mxnet/issues/9686

I would be happy to volunteer for 2.0 release with assistance from a comitter.

Pedro.

On Tue, Apr 2, 2019 at 5:06 PM Hagay Lupesko  wrote:
>
> Dear MXNet community,
>
> I wanted to initiate a discussion about the plan and scope for the next
> MXNet releases.
> I suggest we focus on three releases, and get the process going in parallel:
> (1) 1.4.1 - patch release on top of 1.4.0 to address some perf regressions
> and memory leaks I am aware of, such as the memory leak fixed on Scala [0
> ]. I went ahead and
> created a draft release proposal wiki [1
> 
> ].
> (2) 1.5.0 - a minor release to add new features introduced since 1.4.0
> release started (back in Nov 2018!), such as various performance
> improvements: aggregate SGD, in-place updates in optimizers, gpu support
> for image processing operators and many more features useful for MXNet’s
> users.
> (3) 2.0 - an exciting major release that will include major enhancements to
> MXNet.
>
> Timeframes will probably vary based on the scope. I think we should plan to
> start 1.4.1 release within a couple of weeks, 1.5.0 should target starting
> once we release 1.4.1, and 2.0 timeline is TBD - but such a major release
> will require more time to discuss and decide in the community.
>
> I was thinking to get started through:
> (1) Draft proposals on CWiki, where the community can add content and
> propose scope and features.
> (2) Setup online meetings, where anyone can dial into, from anywhere, where
> we will have a chance to discuss in voice+video.
> (3) With (1)+(2) have a scope and timeline that the community, in large,
> supports.
>
> Would be great to get the community's feedback and suggestions, and please
> reply if you would like to be involved in the effort of supporting the
> releases!
>
> MXNet is awesome, looking forward to working together to make it even
> better!
> Hagay
>
> [0] https://github.com/apache/incubator-mxnet/pull/14586
> [1]
> https://cwiki.apache.org/confluence/display/MXNET/%5BDRAFT+PROPOSAL%5D+Apache+MXNet+%28incubating%29+1.4.1+Release+Plan+and+Status

Re: Discussing plans for next MXNet releases

[kellen sunderland]

Release breakdown makes sense to me Hagay.  Thanks for initiating a
discussion.

Some features that I'm personally looking forward to that I hope can make
it into 1.5 (schedule permitting):
*  TensorRT being integrated with the subgraph API
*  VNNI MKLDNN support
*  AMP training in MXNet

I like the idea of having a call to align on features for the 1.5 release.
For those unable to dial in we have a rapporteur who can send notes around
after the meeting.

For the 2.0 release I wonder if we could start a thread that would have a
list of big changes/features people would like to see.  I know there's been
a few changes I've made that required sub-optimal implementations to avoid
a breaking change.  This could be a good opportunity to clean up prior
work.  It'd also be a good opportunity to prune our operators to those that
are well supported, and to make sure they're named and structured in an
understandable way for users and contributors.

-Kellen

On Tue, Apr 2, 2019 at 5:06 PM Hagay Lupesko  wrote:

> Dear MXNet community,
>
> I wanted to initiate a discussion about the plan and scope for the next
> MXNet releases.
> I suggest we focus on three releases, and get the process going in
> parallel:
> (1) 1.4.1 - patch release on top of 1.4.0 to address some perf regressions
> and memory leaks I am aware of, such as the memory leak fixed on Scala [0
> ]. I went ahead and
> created a draft release proposal wiki [1
> <
> https://cwiki.apache.org/confluence/display/MXNET/%5BDRAFT+PROPOSAL%5D+Apache+MXNet+%28incubating%29+1.4.1+Release+Plan+and+Status
> >
> ].
> (2) 1.5.0 - a minor release to add new features introduced since 1.4.0
> release started (back in Nov 2018!), such as various performance
> improvements: aggregate SGD, in-place updates in optimizers, gpu support
> for image processing operators and many more features useful for MXNet’s
> users.
> (3) 2.0 - an exciting major release that will include major enhancements to
> MXNet.
>
> Timeframes will probably vary based on the scope. I think we should plan to
> start 1.4.1 release within a couple of weeks, 1.5.0 should target starting
> once we release 1.4.1, and 2.0 timeline is TBD - but such a major release
> will require more time to discuss and decide in the community.
>
> I was thinking to get started through:
> (1) Draft proposals on CWiki, where the community can add content and
> propose scope and features.
> (2) Setup online meetings, where anyone can dial into, from anywhere, where
> we will have a chance to discuss in voice+video.
> (3) With (1)+(2) have a scope and timeline that the community, in large,
> supports.
>
> Would be great to get the community's feedback and suggestions, and please
> reply if you would like to be involved in the effort of supporting the
> releases!
>
> MXNet is awesome, looking forward to working together to make it even
> better!
> Hagay
>
> [0] https://github.com/apache/incubator-mxnet/pull/14586
> [1]
>
> https://cwiki.apache.org/confluence/display/MXNET/%5BDRAFT+PROPOSAL%5D+Apache+MXNet+%28incubating%29+1.4.1+Release+Plan+and+Status
>

Re: Podling Report Reminder - April 2019

[Sheng Zha]

Thanks for the reminder. I’m working on it and will post the draft back to the 
list, and would appreciate feedback from the community by then.

-sz

> On Apr 2, 2019, at 5:23 PM, Tianqi Chen  wrote:
> 
> It would be great if the PPMC coordinate and prepare the report
> 
>> On Tue, Apr 2, 2019 at 4:00 PM Hagay Lupesko  wrote:
>> 
>> Is anyone working on the podling report?
>> I'm happy to take care of that if no one else is planning to do it.
>> 
>> Cheers,
>> Hagay
>> 
>>> On Fri, Mar 29, 2019 at 4:06 PM  wrote:
>>> 
>>> Dear podling,
>>> 
>>> This email was sent by an automated system on behalf of the Apache
>>> Incubator PMC. It is an initial reminder to give you plenty of time to
>>> prepare your quarterly board report.
>>> 
>>> The board meeting is scheduled for Wed, 17 April 2019, 10:30 am PDT.
>>> The report for your podling will form a part of the Incubator PMC
>>> report. The Incubator PMC requires your report to be submitted 2 weeks
>>> before the board meeting, to allow sufficient time for review and
>>> submission (Wed, April 03).
>>> 
>>> Please submit your report with sufficient time to allow the Incubator
>>> PMC, and subsequently board members to review and digest. Again, the
>>> very latest you should submit your report is 2 weeks prior to the board
>>> meeting.
>>> 
>>> Candidate names should not be made public before people are actually
>>> elected, so please do not include the names of potential committers or
>>> PPMC members in your report.
>>> 
>>> Thanks,
>>> 
>>> The Apache Incubator PMC
>>> 
>>> Submitting your Report
>>> 
>>> --
>>> 
>>> Your report should contain the following:
>>> 
>>> *   Your project name
>>> *   A brief description of your project, which assumes no knowledge of
>>>the project or necessarily of its field
>>> *   A list of the three most important issues to address in the move
>>>towards graduation.
>>> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
>>>aware of
>>> *   How has the community developed since the last report
>>> *   How has the project developed since the last report.
>>> *   How does the podling rate their own maturity.
>>> 
>>> This should be appended to the Incubator Wiki page at:
>>> 
>>> https://wiki.apache.org/incubator/April2019
>>> 
>>> Note: This is manually populated. You may need to wait a little before
>>> this page is created from a template.
>>> 
>>> Mentors
>>> ---
>>> 
>>> Mentors should review reports for their project(s) and sign them off on
>>> the Incubator wiki page. Signing off reports shows that you are
>>> following the project - projects that are not signed may raise alarms
>>> for the Incubator PMC.
>>> 
>>> Incubator PMC
>>> 
>> 

Re: Podling Report Reminder - April 2019

[Tianqi Chen]

It would be great if the PPMC coordinate and prepare the report

On Tue, Apr 2, 2019 at 4:00 PM Hagay Lupesko  wrote:

> Is anyone working on the podling report?
> I'm happy to take care of that if no one else is planning to do it.
>
> Cheers,
> Hagay
>
> On Fri, Mar 29, 2019 at 4:06 PM  wrote:
>
> > Dear podling,
> >
> > This email was sent by an automated system on behalf of the Apache
> > Incubator PMC. It is an initial reminder to give you plenty of time to
> > prepare your quarterly board report.
> >
> > The board meeting is scheduled for Wed, 17 April 2019, 10:30 am PDT.
> > The report for your podling will form a part of the Incubator PMC
> > report. The Incubator PMC requires your report to be submitted 2 weeks
> > before the board meeting, to allow sufficient time for review and
> > submission (Wed, April 03).
> >
> > Please submit your report with sufficient time to allow the Incubator
> > PMC, and subsequently board members to review and digest. Again, the
> > very latest you should submit your report is 2 weeks prior to the board
> > meeting.
> >
> > Candidate names should not be made public before people are actually
> > elected, so please do not include the names of potential committers or
> > PPMC members in your report.
> >
> > Thanks,
> >
> > The Apache Incubator PMC
> >
> > Submitting your Report
> >
> > --
> >
> > Your report should contain the following:
> >
> > *   Your project name
> > *   A brief description of your project, which assumes no knowledge of
> > the project or necessarily of its field
> > *   A list of the three most important issues to address in the move
> > towards graduation.
> > *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> > aware of
> > *   How has the community developed since the last report
> > *   How has the project developed since the last report.
> > *   How does the podling rate their own maturity.
> >
> > This should be appended to the Incubator Wiki page at:
> >
> > https://wiki.apache.org/incubator/April2019
> >
> > Note: This is manually populated. You may need to wait a little before
> > this page is created from a template.
> >
> > Mentors
> > ---
> >
> > Mentors should review reports for their project(s) and sign them off on
> > the Incubator wiki page. Signing off reports shows that you are
> > following the project - projects that are not signed may raise alarms
> > for the Incubator PMC.
> >
> > Incubator PMC
> >
>

Discussing plans for next MXNet releases

[Hagay Lupesko]

Dear MXNet community,

I wanted to initiate a discussion about the plan and scope for the next
MXNet releases.
I suggest we focus on three releases, and get the process going in parallel:
(1) 1.4.1 - patch release on top of 1.4.0 to address some perf regressions
and memory leaks I am aware of, such as the memory leak fixed on Scala [0
]. I went ahead and
created a draft release proposal wiki [1

].
(2) 1.5.0 - a minor release to add new features introduced since 1.4.0
release started (back in Nov 2018!), such as various performance
improvements: aggregate SGD, in-place updates in optimizers, gpu support
for image processing operators and many more features useful for MXNet’s
users.
(3) 2.0 - an exciting major release that will include major enhancements to
MXNet.

Timeframes will probably vary based on the scope. I think we should plan to
start 1.4.1 release within a couple of weeks, 1.5.0 should target starting
once we release 1.4.1, and 2.0 timeline is TBD - but such a major release
will require more time to discuss and decide in the community.

I was thinking to get started through:
(1) Draft proposals on CWiki, where the community can add content and
propose scope and features.
(2) Setup online meetings, where anyone can dial into, from anywhere, where
we will have a chance to discuss in voice+video.
(3) With (1)+(2) have a scope and timeline that the community, in large,
supports.

Would be great to get the community's feedback and suggestions, and please
reply if you would like to be involved in the effort of supporting the
releases!

MXNet is awesome, looking forward to working together to make it even
better!
Hagay

[0] https://github.com/apache/incubator-mxnet/pull/14586
[1]
https://cwiki.apache.org/confluence/display/MXNET/%5BDRAFT+PROPOSAL%5D+Apache+MXNet+%28incubating%29+1.4.1+Release+Plan+and+Status

Re: Podling Report Reminder - April 2019

[Hagay Lupesko]

Is anyone working on the podling report?
I'm happy to take care of that if no one else is planning to do it.

Cheers,
Hagay

On Fri, Mar 29, 2019 at 4:06 PM  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 17 April 2019, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, April 03).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://wiki.apache.org/incubator/April2019
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

Re: [DISCUSS] Rebrand Gluon to MXNet imperative or something MXNet.

[Lieven Govaerts]

Hi,


On Thu, 28 Mar 2019 at 22:08, Mu Li  wrote:

> The name Gluon is originally used for a collaboration project between
> Amazon and Microsoft [1].
> I pinged both Apache and Amazon legal teams later, they confirmed Gluon is
> not considered as a trademark.
>
> [1]
>
> https://aws.amazon.com/blogs/aws/introducing-gluon-a-new-library-for-machine-learning-from-aws-and-microsoft/
>
> the outcome of that collaboration project as a separate API to multiple
backends seems to be effectively abandoned:

https://github.com/gluon-api/gluon-api

The code ends up in the Apache MXNet codebase, but is never integrated in
Microsoft's CNTK.

https://github.com/Microsoft/CNTK/issues/3049


If the Gluon name is important to the ASF we should treat it as a brand and
at least check if no one else owns the rights to that name. (Microsoft
maybe?)


What was the original plan with GluonCV and GluonNLP?

https://github.com/dmlc/gluon-nlp

https://github.com/dmlc/gluon-cv

While these are separate projects, they share the same Gluon name
with MXNet Gluon, are hosted on MXNet.io, and besides using the ALv2
license the code is also licensed to the ASF:
# Licensed to the Apache Software Foundation (ASF) under one
# or more contributor license agreements.

Are these projects on their way to being integrated in the MXNet project?
Or are they going in the other direction?

regards,

Lieven


> On Thu, Mar 28, 2019 at 2:04 PM Isabel Drost-Fromm 
> wrote:
>
> >
> >
> > Am 28. März 2019 21:53:16 MEZ schrieb Mu Li :
> > >
> > >The reason why we call it GluonCV instead of MXNetCV is because MXNet
> > >is a
> > >trademark owned by Apache, while Gluon doesn't have this issue.
> >
> > Who's the "we" in that sentence?
> >
> > If it doesn't belong to Apache, who owns the Gluon trademark?
> >
> > Isabel
> >
> >
> > --
> > Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
> >
>

Re: [Announcement] New Committer - Alex Zai

[Alex Zai]

Thanks everyone. Looking forward to helping mxnet continue to grow.
Best,Alex  





On Mon, Apr 1, 2019 1:38 AM, Lin Yuan apefor...@gmail.com  wrote:
Congrats, Alex! Hope your book is going well :)
Lin
On Sun, Mar 31, 2019 at 6:18 PM Zhao, Patric  wrote:
Congratulation, Alex. 

Thank you to your helps for MKLDNN backend including tests, coverage, CI :)

Looking forward more cooperation together.


> -Original Message-
> From: Steffen Rochel [mailto:steffenroc...@gmail.com]
> Sent: Monday, April 1, 2019 8:56 AM
> To: dev@mxnet.incubator.apache.org
> Cc: Alex Zai 
> Subject: Re: [Announcement] New Committer - Alex Zai
> 
> Congratulation Alex!
> 
> On Sun, Mar 31, 2019 at 4:17 PM Carin Meier 
> wrote:
> 
> > Welcome and congrats!
> >
> > On Sun, Mar 31, 2019 at 12:48 PM Anirudh Subramanian <
> > anirudh2...@gmail.com>
> > wrote:
> >
> > > Hi all,
> > >
> > > Please join me to welcome Alex Zai as a new committer of Apache
> > > (incubating) MXNet!
> > >
> > > Alex has been instrumental in brining MKLDNN from experimental to
> > > making
> > it
> > > default on MXNet master. This involved adding Python and C++ unit
> > > tests, improving CI coverage for MKLDNN, testing MKLDNN on different
> > > platforms
> > and
> > > working on issues related to MKLDNN.
> > >
> > > PRs:
> > >
> > >
> > https://github.com/apache/incubator-
> mxnet/pulls?utf8=%E2%9C%93=is%3A
> > pr+author%3Aazai91+
> > >
> > > Issues:
> > >
> > >
> > https://github.com/apache/incubator-
> mxnet/issues?utf8=%E2%9C%93=is%3
> > Aissue+involves%3Aazai91
> > >
> > > Reviews:
> > >
> > >
> > https://github.com/apache/incubator-
> mxnet/pulls?page=1=is%3Apr+revie
> > wed-by%3Aazai91=%E2%9C%93
> > >
> > > Dev:
> > > https://lists.apache.org/list.html?d...@mxnet.apache.org:lte=3y:azai9
> > > 1
> > >
> > > Thanks,
> > >
> > > Anirudh
> > >
> >