Re: Release plan - MXNET 1.3

[Divakaruni, Dominic]

Hi all, We tested resnet50 on MXNet built from master branch on Friday and were 
seeing degraded performance on GPU - about 50% slower compared to these values 
here https://mxnet.incubator.apache.org/faq/perf.html. FWIW this slowdown was 
seen for both MXNet as well as the TRT integrated MXNet. 

Something for you all to verify before or after you cut the RC.

Thx!

On 8/13/18, 4:34 AM, "kellen sunderland"  wrote:

Hey Roshani,

Has a RC branch already been cut?  If so, a quick heads up that I think
this commit should probably get into RC0 for 1.3.

https://github.com/apache/incubator-mxnet/commit/ee8755a2531b322fec29c9c3d2aa3b8738da41f3

It won't cause issues for users, but from a versioning compatibility
perspective it's probably better that we remove these functions in this
release. This way we don't have to worry about major bumps in the next
release if they're removed.

-Kellen


On Fri, Aug 10, 2018 at 7:24 PM Roshani Nagmote 
wrote:

> Thanks Kellen and everyone else for working to get TensorRT PR merged!
> @Sina, I will be keeping track of that issue and fixes to get in the
> release.
>
> We are starting code freeze for 1.3 release today. A release candidate 
will
> be cut on 08/17.
> Feel free to add any other comments/suggestions.
>
> Thanks,
> Roshani
>
> On Fri, Aug 10, 2018 at 5:39 AM kellen sunderland <
> kellen.sunderl...@gmail.com> wrote:
>
> > All merged and ready to go from my side Roshani (the TensorRT PR).
> >
> > I agree with Sina that issue 12116 looks it's a blocker.  I'll try and
> > reproduce it locally to get another datapoint.
> >
> > On Fri, Aug 10, 2018 at 3:15 AM Afrooze, Sina 
> wrote:
> >
> > > Hi Roshani - I think this regression issue is a release blocker:
> > > https://github.com/apache/incubator-mxnet/issues/12116  - Sina
> > >
> > >
> > > On 8/8/18, 12:40 PM, "Roshani Nagmote" 
> > wrote:
> > >
> > > Thanks, Kellen for letting me know.
> > >
> > > On Wed, Aug 8, 2018 at 12:09 PM kellen sunderland <
> > > kellen.sunderl...@gmail.com> wrote:
> > >
> > > > Hey Roshani, I think it should be ready by Friday.
> > > >
> > > > On Tue, Aug 7, 2018, 10:20 PM Roshani Nagmote <
> > > roshaninagmo...@gmail.com>
> > > > wrote:
> > > >
> > > > > Thanks Kellen. Yes, we were treating this PR as a release
> > blocker.
> > > Do you
> > > > > have any ETA by which it will be completed? Approximate time
> will
> > > also
> > > > > work.
> > > > > @zhi, Thanks for bringing this PR into notice. I will keep a
> > track
> > > of it.
> > > > >
> > > > > -Roshani
> > > > >
> > > > > On Tue, Aug 7, 2018 at 11:30 AM Joshua Z. Zhang <
> > > cheungc...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > I strongly suggest to track this PR
> > > > > > https://github.com/apache/incubator-mxnet/pull/11908 <
> > > > > > https://github.com/apache/incubator-mxnet/pull/11908> in 1.3
> > > release
> > > > > > which fixed the usability issue for lower end machines that
> > > don’t have
> > > > as
> > > > > > large shared memory space as ec2 instances.
> > > > > >
> > > > > > Best,
> > > > > >
> > > > > > - Zhi
> > > > > >
> > > > > > > On Aug 7, 2018, at 9:05 AM, Roshani Nagmote <
> > > > roshaninagmo...@gmail.com
> > > > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > Hi all,
> > > > > > >
> > > > > > > Right now, we are delaying MXNet 1.3 release for pending
> > > TensorRT PR
> > > > (
> > > > > > > https://github.com/apache/incubator-mxnet/pull/11325 ).
> > > > > > >
> > > > > > > I wanted to ask everyone for their opinions if we should
> > delay
> > > the
> > > > > > release
> > > > > > > to get tensorRT integration in or we should go ahead with
> the
> > > release
> > > > > and
> > > > > > > include tensorRT in next release. Please provide
> suggestions.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Roshani
> > > > > > >
> > > > > > > On Mon, Aug 6, 2018 at 12:45 AM Hagay Lupesko <
> > > lupe...@gmail.com>
> > > > > wrote:
> > > > > > >
> > > > > > >> Some thoughts: why not keep it out of 1.3, and merge it
> into
> > > master
> > > > so
> > > > > > it
> > > > > > >> can go out with 1.4 instead?
> > > > > > >> Pros:
> > > > > > >> - Reduce quality risks for 1.3
> > > > > > >> - More time to test and get feedback before release
> > > > > > >> - Avoid further delays 

Re: Podling Report Reminder - April 2017

[Divakaruni, Dominic]

Hello MXNet members,

Here is a draft report proposal for the April report. Please do weigh in with 
any comments, clarifications and additional context that you may want to add:





MXNet



A Flexible and Efficient Library for Deep Learning



MXNet has been incubating since 2017-01-23.



Three most important issues to address in the move towards graduation:



  1. Move the code and website to Apache Infrastructure.

  2. Establish a formal release process and schedule, allowing for dependable 
release cycles in line with Apache development process.

  3.



Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?



Contributors of the project are kicking off a focused effort towards completing 
the initial setup, including code and website migration to Apache 
infrastructure and moving past that quickly towards the first release. The 
project’s contributors look to the ASF for best practices related to moving the 
infrastructure of a large active project while maintaining user experience.



How has the community developed since the last report?



While the infrastructure of the project is still under DMLC, the contributors 
are making headway on documentation quality and bug fixes towards a stability 
release. Target for this release is May 15. The committers will look to make 
this the first release under ASF guidelines.



How has the project developed since the last report?

  Development is active under the original project (DMLC/MXNet).



How would you assess the podling's maturity?



  [X] Initial setup

  [ ] Working towards first release

  [ ] Community building

  [ ] Nearing graduation

  [ ] Other:



Date of last release:



No Apache Release yet



When were the last committers or PPMC members elected?



  Project is being set up with the initial set of committers.



Thanks!

Dom







On 4/9/17, 8:19 PM, "Henri Yandell" <bay...@apache.org> wrote:



I doubt we'll get it in btw - I think this month it'll flag as "Did not

report", however if we can put together a late report I can at least

include that in the board notes as a comment.



On Sun, Apr 9, 2017 at 7:23 PM, Henri Yandell <bay...@apache.org> wrote:



> Can't hurt :)

>

> On Sun, Apr 9, 2017 at 19:23 Divakaruni, Dominic <ddiva...@amazon.com>

> wrote:

>

>> My apologies, I didn’t catch the 4/5 date. I was shooting for 4/19. Is

>> there still time to send this in tomorrow?

>>

>>

>>

>> On 4/3/17, 8:13 PM, "Henri Yandell" <bay...@apache.org> wrote:

>>

>> Thank you Dom, that would be very much appreciated :)

>>

>> https://wiki.apache.org/incubator/April2017 shows the template

>> (search for

>> MXNet).

>>

>> If you look at the last couple of Incubator reports,

>> https://wiki.apache.org/incubator/February2017 +

>> https://wiki.apache.org/incubator/March2017 - you can find the 2

>> previous

>> reports.

>>

>> If you'd like to propose something to the mailing list, that would be

>> great. One of the mentors can add to the wiki once we have some text.

>>

>>     Thanks - personal-life items have been filling my weekend/week so 
this

>> wasn't flagging for me,

>>

>> Hen

>>

>> On Sat, Apr 1, 2017 at 11:51 PM, Divakaruni, Dominic <

>> ddiva...@amazon.com>

>> wrote:

>>

>> > Hello,

>> > Is anyone taking this?

>> >

>> > If not sent me a template for one that's been done in the past and

>> I can

>> > help.

>> >

>> > Regards,

>> > Dom

>> >

>> >

>> > > On Apr 1, 2017, at 6:42 PM, "johndam...@apache.org" <

>> > johndam...@apache.org> 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, 19 April 2017, 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

>&

Re: Podling Report Reminder - April 2017

[Divakaruni, Dominic]

Hello,
Is anyone taking this?

If not sent me a template for one that's been done in the past and I can help.

Regards,
Dom


> On Apr 1, 2017, at 6:42 PM, "johndam...@apache.org"  
> 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, 19 April 2017, 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 05).
> 
> 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.
> 
> 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/April2017
> 
> 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