MXNet 1.3 release - call for volunteers

[Hagay Lupesko]

Hello community!

I'd like to kickstart the process for MXNet v1.3 release - and ask for a
volunteer to take on this release as a release manager. I am hoping the
release process can start next week or so.
The release scope is documented here: [1

]
The release process is documented here: [2]

Some of the involved tasks require committer privileges, and I can help
identifying a committer that will be available to help and mentor the
release manager. This is a great opportunity for someone to contribute,
ramp up further on the project, and help get the latest and greatest out to
MXNet users.

If you are interested - please reply and let me know!

Thanks, Hagay

[1]
https://cwiki.apache.org/confluence/display/MXNET/Project+Proposals+for+next+MXNet+Release
[2]
https://cwiki.apache.org/confluence/display/MXNET/Release+Process?src=contextnavpagetreemode

Disabling flaky tests

[Marco de Abreu]

Hello,

we currently have a false-failure rate of about 59% in our CI. This leads
to a lot of PRs failing due to flaky tests. We're currently in the process
to fix problematic tests, but we're still not at a point which we can
consider as stable.

A few colleagues proposed to disable tests temporarily to increase the
stability of the system. I know that this is heavily opposed by a lot of
people including myself, but we're pretty much stalling our development due
to these issues. Thus, I'd like to disable them for now and make them a
release requirement. We currently have 12 disabled tests (ranging back to
October 2017) and I'd like to add a few more.

To keep track of disabled tests, I have added a new label [1]. If a test
gets fixed, the issue will be closed and thus automatically disappear from
the list.

To address the concerns of the community about tests being disabled and
then forgotten, I'd like to make it a release requirement for 1.3 that no
tests are disabled. This means we will have reduced coverage temporarily,
but it will not impact our customers since they will be re-enabled for the
next release - this is basically a two-way door. On the other hand, we're
improving the turnaround time for PRs and reduce the frustration level.

By the way, we currently have an internal sprint running at Amazon which
leads to everybody focussing on addressing flaky tests. This means that
this state will not persist for long.

Best regards,
Marco

[1]:
https://github.com/apache/incubator-mxnet/issues?q=is%3Aopen+is%3Aissue+label%3A%22Disabled+test%22

Re: C++ api issue labeling

[Hagay Lupesko]

Thank you everyone for your suggestions.
I will work with a committer to get this updated ASAP.

On Mon, Jun 25, 2018 at 8:55 AM Marco de Abreu
 wrote:

> +1 to renaming to Backend
>
> On Mon, Jun 25, 2018 at 10:13 AM Hagay Lupesko  wrote:
>
> > Thanks Lin for your feedback.
> > Bumping again to get more feedback before concluding.
> >
> > On Fri, Jun 22, 2018 at 8:53 AM Lin Yuan  wrote:
> >
> > > I agree with Hagay. Using "Backend" as label makes it much easier to
> > track.
> > >  "C++" label only describes the language used in implementation,
> > "Backend"
> > > better describes the nature of the work (let's assume we change the
> > backend
> > > implementation from C++ to other languages in the future).
> > >
> > > Lin
> > >
> > > On Fri, Jun 22, 2018 at 1:09 AM Hagay Lupesko 
> wrote:
> > >
> > > > Thanks everyone for chiming in and clarifying.
> > > > It seems that the "C++" label name is confusing for our community
> since
> > > it
> > > > can be interpreted as both the CPP API and the backend...
> > > > As an anecdote, this issue [1
> > > > ] is labeled
> > as
> > > > "C++" but is about the CPP API, not the backend.
> > > >
> > > > Should we just rename "C++" to "Backend" to avoid confusion?
> > > >
> > > > [1] https://github.com/apache/incubator-mxnet/issues/10937
> > > >
> > > > On Thu, Jun 21, 2018 at 12:39 PM Pedro Larroy <
> > > > pedro.larroy.li...@gmail.com>
> > > > wrote:
> > > >
> > > > > Agree with Anirudh, they are different things. Maybe change the
> "C++"
> > > > label
> > > > > to "backend" would be more informative?
> > > > >
> > > > > On Thu, Jun 21, 2018 at 12:11 PM Anirudh 
> > > wrote:
> > > > >
> > > > > > Hi Hagay,
> > > > > >
> > > > > > I think we should keep these two labels seperate since they mean
> > > > > different
> > > > > > things.
> > > > > > The C++ label refers to the issue for MXNet backend and the CPP
> > > package
> > > > > > refers to the CPP language binding for mxnet.
> > > > > > We can still make C++ API great again irrespective by filtering
> out
> > > CPP
> > > > > > package issues :).
> > > > > >
> > > > > > Anirudh
> > > > > >
> > > > > >
> > > > > > On Thu, Jun 21, 2018 at 11:56 AM, Hagay Lupesko <
> lupe...@gmail.com
> > >
> > > > > wrote:
> > > > > >
> > > > > > > Hey community,
> > > > > > >
> > > > > > > I was going over the open GitHub issues for MXNet, and noticed
> > that
> > > > we
> > > > > > have
> > > > > > > two labels for the CPP API: "CPP package", "C++"
> > > > > > >
> > > > > > > Wanted to suggest we remove "CPP package" and just stick to
> "C++"
> > > > > > > This will make it easier for the community to classify issues
> and
> > > > focus
> > > > > > on
> > > > > > > making the C++ API great again ;)
> > > > > > >
> > > > > > > Let me know if someone has any concerns, otherwise I will find
> a
> > > > > > committer
> > > > > > > that I can work with to make this change.
> > > > > > >
> > > > > > > Thanks!
> > > > > > > Hagay
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Podling Report Reminder - July 2018

[jmclean]

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, 18 July 2018, 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, July 04).

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/July2018

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: Broken dependency in Caffe converter causes all CI runs to fail

[Marco de Abreu]

Thank you Chen and Thomas for fixing the test:
https://github.com/apache/incubator-mxnet/pull/11425

-Marco

On Wed, Jun 27, 2018 at 3:48 PM Chen HY  wrote:

> I found a replica from Google Image Search also.
> Hope it works.
>
>
> 

Slack channel invite

[Timur Shenkao]

Hello!

Could your invite me to MXNet Slack channels?

Re: Broken dependency in Caffe converter causes all CI runs to fail

[Chen HY]

I found a replica from Google Image Search also.
Hope it works.

Re: Broken dependency in Caffe converter causes all CI runs to fail

[Chen HY]

Is that the cat you need?

2018-06-27 13:03 GMT+01:00 Marco de Abreu <
marco.g.ab...@googlemail.com.invalid>:

> I have submitted a pull request [1] to temporarily disable the converter.
> Unfortunately, the entire test-suite depends on that image. Considering the
> entire CI is currently blocked, I'll take the liberty to merge the PR as
> soon as it passes CI unless somebody objects. Afterwards, I'd like to make
> sure that we re-enable this test before the next release.
>
> -Marco
>
> [1]: https://github.com/apache/incubator-mxnet/pull/11419
>
> On Wed, Jun 27, 2018 at 1:53 PM Marco de Abreu <
> marco.g.ab...@googlemail.com>
> wrote:
>
> > Hello,
> >
> > I have noticed an increased number of CI failures. The reason seems to be
> > https://github.com/apache/incubator-mxnet/issues/11407. A third party
> > dependency (a cat image) has been deleted from the webserver and thus
> > causes all our CI runs to fail. Is anybody familiar with that test and
> has
> > a backup of the image so we can upload it to S3? Otherwise, we'll have to
> > remove the test.
> >
> > Best regards,
> > Marco
> >
>



-- 
Chen Hanyang 陈涵洋

Re: Broken dependency in Caffe converter causes all CI runs to fail

[Marco de Abreu]

I have submitted a pull request [1] to temporarily disable the converter.
Unfortunately, the entire test-suite depends on that image. Considering the
entire CI is currently blocked, I'll take the liberty to merge the PR as
soon as it passes CI unless somebody objects. Afterwards, I'd like to make
sure that we re-enable this test before the next release.

-Marco

[1]: https://github.com/apache/incubator-mxnet/pull/11419

On Wed, Jun 27, 2018 at 1:53 PM Marco de Abreu 
wrote:

> Hello,
>
> I have noticed an increased number of CI failures. The reason seems to be
> https://github.com/apache/incubator-mxnet/issues/11407. A third party
> dependency (a cat image) has been deleted from the webserver and thus
> causes all our CI runs to fail. Is anybody familiar with that test and has
> a backup of the image so we can upload it to S3? Otherwise, we'll have to
> remove the test.
>
> Best regards,
> Marco
>

Re: Vote to stop using JIRA

[Marco de Abreu]

Hello Yasser,
I'd like to check back with you and ask if you need any assistance or if
there is anything else we can do. Please feel free to shoot me a private
email so we can set up a 1:1 to discuss ideas and solutions.
-Marco

On Wed, Jun 13, 2018 at 10:02 AM Yasser Zamani 
wrote:

>
>
> On 6/11/2018 8:53 PM, Marco de Abreu wrote:
> > How about you set up a personal instance of JIRA (let us know if the
> public
> > ones differ too much from the one we're running under Apache) and play
> > around a bit? We can then review the setup and migrate the necessary
> > changes after everything looks good.
>
> I'm pleased to say that fortunately it seems MXNet already has both
> Kanban [1] and Scrum [2] project management boards :)
>
> Regards.
>
> [1] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=237
> [2] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=211
>

Broken dependency in Caffe converter causes all CI runs to fail

[Marco de Abreu]

Hello,

I have noticed an increased number of CI failures. The reason seems to be
https://github.com/apache/incubator-mxnet/issues/11407. A third party
dependency (a cat image) has been deleted from the webserver and thus
causes all our CI runs to fail. Is anybody familiar with that test and has
a backup of the image so we can upload it to S3? Otherwise, we'll have to
remove the test.

Best regards,
Marco