[Announce] Upcoming Apache MXNet (incubating) 1.4.0 release

Dear MXNet community, the agreed plan was to establish code freeze for 1.4.0 release today. As the 1.3.1 patch release is still ongoing I suggest to post-pone the code freeze to Friday 16th November 2018. Sergey Kolychev has agreed to act as co-release manager for all tasks which require committer

Re: [Question] Difference between "Feature" and "Feature request" labels in Github

Thanks guys for your prompt actions. I am so impressed！ Lin On Tue, Nov 13, 2018 at 5:33 PM Sheng Zha wrote: > I was in the middle of transferring all items labeled with "Feature" to the > "Feature request" label when "Feature" label was deleted. I'm not sure who > deleted the "Feature" label b

Re: [Question] Difference between "Feature" and "Feature request" labels in Github

I was in the middle of transferring all items labeled with "Feature" to the "Feature request" label when "Feature" label was deleted. I'm not sure who deleted the "Feature" label but it's gone now. -sz On Tue, Nov 13, 2018 at 5:05 PM Anirudh Acharya wrote: > This issue was raised before here -

Re: [Question] Difference between "Feature" and "Feature request" labels in Github

Thanks for doing this. - Anirudh On Nov 13, 2018 5:25 PM, Sheng Zha wrote: Oh, I see. I was moving the other 80 or so, so it was probably a race-condition. Anyway, thanks for being eager to help. -sz On Tue, Nov 13, 2018 at 5:24 PM Naveen Swamy wrote: > done now, removed the feature label, t

Re: [Question] Difference between "Feature" and "Feature request" labels in Github

Oh, I see. I was moving the other 80 or so, so it was probably a race-condition. Anyway, thanks for being eager to help. -sz On Tue, Nov 13, 2018 at 5:24 PM Naveen Swamy wrote: > done now, removed the feature label, there were 4 issues with that label > but also had Feature Request. > > On Tue,

Re: [Question] Difference between "Feature" and "Feature request" labels in Github

done now, removed the feature label, there were 4 issues with that label but also had Feature Request. On Tue, Nov 13, 2018 at 5:05 PM Anirudh Acharya wrote: > This issue was raised before here - > > https://lists.apache.org/thread.html/3e988e6bd82cb2d69ba20c21bf763952ed22a5732e61f6fba1f89ac8@%3

Re: [Question] Difference between "Feature" and "Feature request" labels in Github

there were a few more that had 'Feature' as label but didn't show up in the filter search, I manually applied the `Feature Request` on them On Tue, Nov 13, 2018 at 5:12 PM Naveen Swamy wrote: > done now, removed the feature label, there were 4 issues with that label > but also had Feature Reques

Re: [Question] Difference between "Feature" and "Feature request" labels in Github

This issue was raised before here - https://lists.apache.org/thread.html/3e988e6bd82cb2d69ba20c21bf763952ed22a5732e61f6fba1f89ac8@%3Cdev.mxnet.apache.org%3E We need someone with committer privileges to fix it. Thanks Anirudh On Tue, Nov 13, 2018 at 4:36 PM Lin Yuan wrote: > Dear Community,

[Question] Difference between "Feature" and "Feature request" labels in Github

Dear Community, I often see there are "Feature" and "Feature request" labels in Github issues. May I know the difference? If they are meant to be the same thing, can we only keep one of them? Thanks, Lin

Re: Nightly/Weekly tests for examples

Naveen - I agree with you there. Not every example should be moved to tutorials... just the ones that would be great to have on the site and to be tested regularly. I think that having examples of specific APIs will be useful on the website too. Ankit, there's a cost/benefit analysis for keeping b

Re: [VOTE] Release Apache MXNet (incubating) version 1.3.1.rc0

+1 - Clojure package tested fine with Scala jars On Mon, Nov 12, 2018 at 6:53 PM Anton Chernov wrote: > Dear MXNet community, > > This is the vote to release Apache MXNet (incubating) version 1.3.1. Voting > will start now, on Monday the 12th of November 2018 and close on 14:00 > Thursday the 15

Re: Nightly/Weekly tests for examples

We can start small consolidating few examples which are there in both tutorials/examples folder. One of such example is GradCAM implementation: In tutorials - https://github.com/apache/incubator-mxnet/blob/master/docs/tutorials/vision/cnn_visualization.md In examples- https://github.com/apache/

Re: MXNet - Gluon - Audio

Hi Gaurav, Thanks for starting this. I see the PR is out , left some initial reviews, good work! In addition to Sandeep's queries, I have the following: 1. Can we include some simple classic audio dataset for users to directly import and try o

Re: Nightly/Weekly tests for examples

Aaron, IMO tutorials have a specific purpose, to introduce concepts and APIs to the users and I think converting examples to tutorials would overwhelm the users, we should carefully choose which examples we want to turn into tutorials. I agree that today examples are graveyard of untested code, my

Re: MXNet - Gluon - Audio

Thanks, Gaurav for starting this initiative. The design document is detailed and gives all the information. Starting to add this in "Contrib" is a good idea while we expect a few rough edges and cleanups to follow. I had the following queries: 1. Is there any analysis comparing LibROSA with other

Re: Nightly/Weekly tests for examples

I've been actively promoting moving examples to tutorials during reviews. That way they fall under the testing umbrella and get added to the website. Many times there's not really a great distinction as to why something is in the examples folder, other than it's like a graveyard of untested sample