Re: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc1

[Tao Lv]

+1 (binding)



- Untar the source code package;

- Build from source code with makefile, USE_BLAS=mkl, USE_MKLDNN=1;

- Check mx.__version__;

- Run benchmark_score.py under examples/image-classification.

On Wed, Jul 22, 2020 at 3:13 PM Patrick Mu  wrote:

> + 1
>
> Test custom operators: all examples using custom operators are passing, no
> error or regression found
>
> Ziyi
>
> On 2020/07/22 06:56:46, Kshitij Kalambarkar 
> wrote:
> > + 1
> >
> > * Built from source on Ubuntu 18.04 with CUDA, CUDNN
> > * Verified test_higher_order_grad.py
> >
> > Great job!
> >
> > On Wed, Jul 22, 2020 at 12:02 PM Chaitanya Bapat 
> > wrote:
> >
> > > +1
> > >
> > > - Built from source on Ubuntu18 with CUDA ON, USE_INT64_TENSOR_SIZE ON
> > > - Verified large tensor tests work as expected on a p3.16xl instance
> [with
> > > 8 Tesla V100 GPUs]
> > > - Verified OpPerf utility works as expected.
> > >
> > > Steps followed:
> > > https://gist.github.com/ChaiBapchya/8a5131932693d4ca47281368c752b726
> > >
> > > Thanks Ciyong for leading with the releases. Incredible job.
> > >
> > > Regards,
> > > Chai
> > >
> > >
> > > On Tue, 21 Jul 2020 at 23:05, Karan Jariwala  >
> > > wrote:
> > >
> > > > +1
> > > >
> > > > Build from source on Ubuntu 18 with CUDA/CUDNN/NCCL ON and verified
> with
> > > > Horovod 0.19.5 by running unittest and integration tests.
> > > >
> > > > Thanks,
> > > > Karan
> > > >
> > > > On Tue, Jul 21, 2020 at 10:23 PM Sheng Zha 
> wrote:
> > > >
> > > > > +1. I checked:
> > > > >
> > > > > [x] Are release files in correct location? Yes
> > > > > [x] Do release files have the word incubating in their name? Yes
> > > > > [x] Are the digital signature and hashes correct? Yes
> > > > > [x] Does DISCLAIMER file exist? Yes, DISCLAIMER-WIP
> > > > > [x] Do LICENSE and NOTICE files exists? Yes
> > > > > [x] Is the LICENSE and NOTICE text correct?
> > > > > Yes, though the license still reads "Copyright [] [name of
> > > copyright
> > > > > owner]", which needs correction.
> > > > >
> > > > > [x] Is the NOTICE year correct? Yes
> > > > > [x] Un-included software dependencies are not mentioned in LICENSE
> or
> > > > > NOTICE?
> > > > > No. mshadow is now contributed to MXNet via software grant and
> should
> > > be
> > > > > removed from NOTICE.
> > > > >
> > > > > [x] License information is not mentioned in NOTICE? Confirmed
> > > > >
> > > > > Is there any 3rd party code contained inside the release? If so:
> > > > > [x] Does the software have a compatible license? Yes. Minor issue:
> > > > > Dual license in cmake/Modules/FindJeMalloc.cmake.
> > > > >
> > > > > [x] Are all software licenses mentioned in LICENSE? Yes
> > > > > [x] Is the full text of the licenses (or pointers to it) in
> LICENSE?
> > > Yes
> > > > >
> > > > > Is any of this code Apache licensed? Do they have NOTICE files? If
> so:
> > > > > [x] Have relevant parts of those NOTICE files been added to this
> NOTICE
> > > > > file?
> > > > > No. TVM NOTICE file hasn't been included.
> > > > >
> > > > > [x] Do all source files have ASF headers?
> > > > > Yes, except those in 3rdparty folder and those mentioned in
> license.
> > > > > [x] Do the contents of the release match with what's tagged in
> version
> > > > > control? Yes
> > > > > [x] Are there any unexpected binary files in the release? No
> > > > > [x] Can you compile from source? Are the instruction clear? Yes,
> > > Makefile
> > > > > is present and is straightforward.
> > > > > Is the issue minor? Yes
> > > > > Could it possibly be fixed in the next release? Yes
> > > > >
> > > > > I vote with:
> > > > > [x] +1 release the software
> > > > >
> > > > >
> > > > > On 2020/07/20 17:25:50, "Skalicky, Sam"  >
> > > > > wrote:
> > > > > > +1
> > > > > >
> > > > > > Tested:
> > > > > > - Make flow building from source, verified all
> example/extensions/*
> > > > work
> > > > > correctly
> > > > > > - staticbuild flow cpu & cu102 variants producing the pip wheels,
> > > > tested
> > > > > with custom extension library
> > > > > >
> > > > > > Sam
> > > > > >
> > > > > > On 7/20/20, 4:07 AM, "Chen, Ciyong" 
> wrote:
> > > > > >
> > > > > > CAUTION: This email originated from outside of the
> organization.
> > > Do
> > > > > not click links or open attachments unless you can confirm the
> sender
> > > and
> > > > > know the content is safe.
> > > > > >
> > > > > >
> > > > > >
> > > > > > Thanks Aston, Patric for the vote.
> > > > > >
> > > > > > Hi Community,
> > > > > >
> > > > > > I would like to call for action to test/validate/vote for the
> > > > > release candidate (1.7.0.rc1).
> > > > > > As we've not reached the quorum, I would like to extend the
> > > voting
> > > > > process to July 22, 23:59:59 PST.
> > > > > > Please prepare your time and provide feedback if you've tried
> > > with
> > > > > the pre-released code base, thanks!
> > > > > >
> > > > > > Best Regards,
> > > > > > Ciyong
> > > > > >
> > > > > > -Original Message-
> > > > > > 

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

[Tao Lv]

+1 (binding)

I did:
- Verify the key and signature;
- Untar the source code package;
- Build from source code with makefile, USE_BLAS=mkl, USE_MKLDNN=1;
- Check mx.__version__;
- Run benchmark_score.py under examples/image-classification.

-tao

On Fri, Jul 10, 2020 at 2:18 PM Chen, Ciyong  wrote:

> Hi Community,
>
> I would like to call for action to test/validate/vote for the release
> candidate (1.7.0.rc0)
> As there's not any voting result during the scheduled time window, I would
> like to extend the time windows to July 13, 23:59:59 PST.
> Please prepare your time and provide feedback if you've tried with the
> pre-release code bases, thanks!
>
> Best regards,
> Ciyong
>
> -Original Message-
> From: Chen, Ciyong 
> Sent: Monday, July 6, 2020 10:48 PM
> To: d...@mxnet.apache.org
> Cc: Bob Paulin ; Henri Yandell ; Jason
> Dai ; Markus Weimer ; Michael
> Wall 
> Subject: RE: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc0
>
> For the language bindings and windows platform, may I have your support to
> help verify these features? Thanks!
>
> @lanking520 to help verify the Scala/Java @gigasquid to help verify the
> Clojure
> @hetong007 to help verify the R
> @yajiedesign to help verify the windows platform
>
> Best regards,
> Ciyong Chen
>
> -Original Message-
> From: Chen, Ciyong 
> Sent: Monday, July 6, 2020 10:39 PM
> To: d...@mxnet.apache.org
> Cc: Bob Paulin ; Henri Yandell ; Jason
> Dai ; Markus Weimer ; Michael
> Wall 
> Subject: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc0
>
> Dear MXNet community,
>
> This is the vote to release Apache MXNet (incubating) version 1.7.0.
> Voting will start July 6, 23:59:59 PST and close on July 9, 23:59:59 PST.
>
> Link to release notes:
> https://cwiki.apache.org/confluence/display/MXNET/1.7.0+Release+notes
>
> Link to release candidate:
> https://github.com/apache/incubator-mxnet/releases/tag/1.7.0.rc0
>
> Link to source and signatures on apache dist server:
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.7.0.rc0<
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.7.0.rc0/>
>
> Please remember to TEST first before voting accordingly:
> +1 = approve
> +0 = no opinion
> -1 = disapprove (provide reason)
>
> Additional notes:
>
>   *   There was an issue and discussion[1] regarding on a few numpy
> operators failed due to numpy 1.19.0 released on Jun 20, 2020, which exists
> in all branches (works with numpy <= 1.18.5). As numpy operator is still an
> experimental feature in 1.7.0 release and mainly targeting in MXNet 2.0
> release, so I decided to not block the voting and instead let the Community
> decide whether this is a blocker for the release.
>
> [1] https://github.com/apache/incubator-mxnet/issues/18600
>
> Best regards,
> Ciyong Chen
>
>

Re: [Lazy consensus] Turn on Branch Protection for Release branches and v1.x

[Tao Lv]

+1

On Sat, Jun 20, 2020 at 7:01 AM Sheng Zha  wrote:

> Hi,
>
> I'd like to propose that we turn on branch protection and CI check
> enforcement that's consistent with our master branch for all release
> branches and v1.x. So far we only have branch protection and enforce CI
> checks on master branch, while allowing force push without CI checks on
> release branches.
>
> Feel free to reply if you have questions or concerns, or otherwise I will
> wait for 96hrs before proceeding with changes.
>
> -sz
>

Re: [Announce] Upcoming Apache MXNet (incubating) 1.7.0 release

[Tao Lv]

Hi dev,

Because we have master branch for 2.0 development and v1.x branch for 1.x
development, please make sure your new features, bug fixes and improvements
are properly picked to v1.x branch before the code rebase, if you want them
to be included into v1.7 release.

thanks,
-tao

On Tue, Apr 7, 2020 at 4:08 AM Chaitanya Bapat  wrote:

> Hi Ciyong,
> Awesome news!
> Thanks for driving 1.7.0 release!
> Looking forward to collaboration.
>
> Cheers,
> Chai
>
> On Mon, 6 Apr 2020 at 02:51, Chen, Ciyong  wrote:
>
> >  Hi MXNet Community,
> >
> >
> >
> > As the 1.6.0 release is done (many thanks to Przemek) for a while, it's
> > time to prepare for the next minor release of MXNet 1.7.0.
> >
> >
> >
> > Thanks to Patric (pengzhao-intel@github) who had created the GitHub
> > issue[1] to discuss and collect the major features for 1.7.0. Please add
> > any features/enhancements/bugfixes that you want included there.
> >
> >
> >
> > I (ciyongch@github) would like to be the release manager for the
> upcoming
> > 1.7.0 release. It's my first time to drive a release for MXNet, really
> > thanks to Tao(TaoLv@github) who will guide me to go through the process
> > and already helped to create the Release plan and status page[2] on
> cwiki.
> > I will keep updating the issues and PRs mentioned in issues[1] to the
> cwiki
> > page[2] to track the release process.
> >
> >
> >
> > We're proposing to do the release in May, and rebase the code of v1.7.x
> to
> > latest v1.x on April 10th PST, the code freeze date will be April 20th
> PST.
> > Please let me know whether this timeline is suitable to you or not, or
> want
> > an extension. So your timely response will be highly appreciated!
> >
> >
> >
> > Feel free to add any other comments/suggestions.
> >
> >
> >
> > Thanks,
> >
> > Ciyong
> >
> >
> >
> > [1] https://github.com/apache/incubator-mxnet/issues/16864
> >
> > [2]
> >
> https://cwiki.apache.org/confluence/display/MXNET/1.7.0+Release+Plan+and+Status
> >
> >
> >
>
> --
> *Chaitanya Prakash Bapat*
> *+1 (973) 953-6299*
>
> [image: https://www.linkedin.com//in/chaibapat25]
> [image: https://www.facebook.com/chaibapat
> ]
> [image:
> https://twitter.com/ChaiBapchya] [image:
> https://www.linkedin.com//in/chaibapat25]
> 
>

Re: MXNet Bot Demo

[Tao Lv]

Is it possible for re-triggering a single job to be abused? For example,
the author spends two days re-triggering a flaky job to make it pass. But
other jobs which have passed the validation may be broken by other commits
during the two day without being noticed. And finally the PR is merged with
underlying problems.

On Fri, Mar 13, 2020 at 6:19 AM Marco de Abreu 
wrote:

> In the end it only comes down to money, considering that the system is auto
> scaling, making the execution time constant.
>
> If we're trading money for usability, I certainly would prefer usability.
> I'd rather recommend to spend time on parallelizing test execution or
> getting rid of integration tests in the PR stage instead reducing the costs
> by making people not use it. But taking a step back to requiring people to
> manually trigger CI again doesn't feel right.
>
> I'm happy to see that bot deployed, but I do not agree with removing the
> auto trigger functionality for new commits.
>
> -Marco
>
> Chaitanya Bapat  schrieb am Do., 12. März 2020,
> 22:47:
>
> > @Marco Thanks for pointing that out.
> > Tomorrow i.e. Friday, March 13, 2020 at 3:00 PM - 3:30 PM in (UTC-08:00)
> > Pacific Time (US & Canada).
> >
> > > When do we expect this bot to be deployed?
> > @Lin If all goes well in the next week I can deploy it to public Apache
> > (provided I get permissions from Apache Infra)
> >
> > @Marco Thanks for your feedback.
> > > CI system has to support the community without requiring people to
> > constantly shepherd every single run
> > We have data for the number of times CI was triggered unnecessarily which
> > includes
> > - Entire build triggered instead of specific build
> > - CI triggered when PR is still work in progress or not yet ready (say -
> > intermediate commits)
> > At the end its a trade-off
> > Money, Resources, Time to build for each and every commit vs Pain of
> > triggering builds
> >
> >
> > >  Scan trigger plugin would poll SCM. Can we use plugin at scale?
> >
> > 1. I haven't tested it on scale. But I think with the current scale of
> > MXNet repo (191 open PRs i.e. checking for changes to 191 branches - It
> > should be manageable)
> > 2. What's the purpose of the plugin? tldr; Branch discovery or branch
> > indexing.
> > Scan trigger plugin comes into the picture only once per PR per job
> (i.e. 8
> > times per PR for 8 jobs). It is basically done when a new PR is made and
> > the job (say unix-cpu hasn't discovered the new PR branch yet). That's
> it.
> > So it shouldn't be a problem for public MXNet repo.
> >
> > Thanks,
> > Chai
> >
> >
> > On Thu, 12 Mar 2020 at 14:22, Marco de Abreu 
> > wrote:
> >
> > > Btw you forgot to set a date and time for the metting
> > >
> > >
> > > On Thu, Mar 12, 2020 at 10:18 PM Marco de Abreu <
> marco.g.ab...@gmail.com
> > >
> > > wrote:
> > >
> > > > Thanks Chai, I generally like the idea of the bot. But I'm not a
> > > supporter
> > > > of the idea to disable any automatic triggering (disabling the
> webhook
> > is
> > > > also not an option, considering that this will disable master
> > triggers).
> > > > The CI system has to support the community without requiring people
> to
> > > > constantly shepherd every single run. Disabling automatic triggering
> > > seems
> > > > like a step back to me.
> > > >
> > > > Instead, I'd recommend that CI gets triggered upon every commit as
> > usual,
> > > > but people have the possibility to call a "command" (i.e. make a
> > message
> > > > which results in the bot setting a label) to disable CI until they
> > revoke
> > > > it. But the standard should still be that a new commit triggers a new
> > CI
> > > > run.
> > > >
> > > > https://plugins.jenkins.io/multibranch-scan-webhook-trigger/  seems
> > like
> > > > this would poll SCM. This will incur high quota restrictions. Are you
> > > sure
> > > > that you can use that plugin at scale?
> > > >
> > > > -Marco
> > > >
> > > >
> > > > On Thu, Mar 12, 2020 at 10:04 PM Lin Yuan 
> wrote:
> > > >
> > > >> Chai,
> > > >>
> > > >> Awesome work. When do we expect this bot to be deployed?
> > > >>
> > > >> Best,
> > > >>
> > > >> Lin
> > > >>
> > > >> On Thu, Mar 12, 2020 at 2:00 PM Chaitanya Bapat <
> chai.ba...@gmail.com
> > >
> > > >> wrote:
> > > >>
> > > >> > Hello MXNet community,
> > > >> >
> > > >> > I have built an MXNet Bot  that
> > allows
> > > PR
> > > >> > Authors, Committers and Jenkins Admins to trigger CI manually.
> > > >> > It handles 2 problems
> > > >> > 1. Manual CI trigger instead of existing automated CI trigger
> > > >> > 2. Gives permissions to PR Authors (in addition to MXNet
> Committers
> > > and
> > > >> > Jenkins Admins)
> > > >> >
> > > >> > Design Doc :
> > > >> > https://cwiki.apache.org/confluence/display/MXNET/MXNet+CI+Bot
> > > >> >
> > > >> > I urge you all to attend the demonstration meeting and lend your
> > views
> > > >> on
> > > >> > the same.
> > > >> >
> > > >> > Thank you,
> > > >> > Chai
> > > >> >
> > > >> > 

Re: [apache/incubator-mxnet] [RFC] MXNet 2.0 API Deprecation (#17676)

[Tao Lv]

We have `v1` and `v2` APIs like:
https://mxnet.incubator.apache.org/api/python/docs/search.html?q=v1
https://mxnet.incubator.apache.org/api/python/docs/search.html?q=v2

Do we need cover them in the RFC? How to deprecate or unify these APIs?


-- 
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-mxnet/issues/17676#issuecomment-594984804

Re: [apache/incubator-mxnet] [RFC] New Branches for MXNet 1.x, 1.7.x, and 2.x (#17701)

[Tao Lv]

Nice. It's an essential step towards MXNet 2.0. Curious to know that do we 
still encourage contributors to create PR against the master branch? And in 
what strategy we need pick a commit to branch 1.x? Or they need create two PRs 
against two branches simultaneously?

-- 
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-mxnet/issues/17701#issuecomment-592947107

Re: [apache/incubator-mxnet] [RFC] MXNet 2.0 API Deprecation (#17676)

[Tao Lv]

What about those v1, v2 APIs?

-- 
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-mxnet/issues/17676#issuecomment-591754890

Re: Update on upcoming changes to the MXNet CI: Jenkins

[Tao Lv]

Can someone educate me how to re-trigger a single test suite in CI?

On Thu, Feb 13, 2020 at 5:10 AM Lausen, Leonard 
wrote:

> Hi Denis,
>
> pipeline may be the wrong word, job may be the correct one. For example,
> commiters can currently access a job page like
>
> http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-gpu/detail/PR-17521/5/
>  , press "Login" and then the restart button to only retrigger that job,
> obtaining
>
> http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-gpu/detail/PR-17521/6/
>
> This is correctly reported to Github and the status will change from
> failed to
> passed once depending on the result of the new job.
>
> Best regards
> Leonard
>
> On Wed, 2020-02-12 at 20:23 +, Davydenko, Denis wrote:
> > This might or might not work given that GH PR is failed or not given
> overall
> > CI run status, not just few builds from it. But it is a good suggestion
> to try
> > out, we will evaluate whether it could be accomplished. Thanks!
> >
> >
> >
> > On 2/12/20, 11:05 AM, "Lausen, Leonard" 
> wrote:
> >
> > Thank you Denis for taking up this initiative. With respect to
> "Introduce
> > per-PR
> > CI bot" and the "[mxnet-ci] run" command. Would it make sense to add
> > "retriggering only failed pipelines" to the scope? For example users
> could
> > be
> > asked to specify the name of the pipeline, or have "[mxnet-ci] run
> all"
> > and
> > "[mxnet-ci] run failed".
> >
> > In the current state, when retriggering all pipelines, it's likely
> that
> > one of
> > them will fail. Only by retriggering the failed pipeline alone there
> is a
> > higher
> >  chance to arrive at a state where all pipelines have succeeded.
> >
> > On Wed, 2020-02-12 at 10:12 -0800, Davydenko, Denis wrote:
> > > Hello, MXNet dev community,
> > > As you all know, the experience with CI infrastructure isn’t ideal
> in
> > spite of
> > > its high cost. For this reason, we’re proposing the following
> changes to
> > > improve stability, reduce cost, and grant more control to
> contributors.
> > As we
> > > work in a refresh of CI, we believe these changes will reduce the
> pain
> > we all
> > > suffer when we try to push a PR through the system.
> > >
> > > Following is the list of changes:
> > > Fix missing status reports between GH and Jenkins
> > > Update Jenkins permission groups to re-trigger builds
> > > Introduce per-PR CI bot
> > > Details:
> > >
> > > - Fix missing status reports
> > > Currently, once commit gets added to PR - the CI is run on that
> added
> > commit.
> > > Sometimes, CI run status is missing from the commit in Github
> despite
> > having
> > > completed in Jenkins. Example: CI run:
> > >
> >
> http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-cpu/detail/PR-17376/17/pipeline
> > > , commit status in github (missing unix-cpu, unix-gpu and
> windows-gpu
> > > statuses):
> > >
> >
> https://github.com/apache/incubator-mxnet/pull/17376#partial-pull-merging.
> > > Problem: There seems to be a bug where some status reports are
> missing
> > on
> > > Github. The hypothesis is that there is some issue with Github
> Hooks.
> > >
> > > - Update Jenkins permission groups to re-trigger builds
> > > Problem: Currently, only MXNet Committers and selected people from
> AWS
> > have
> > > the ability to re-trigger CI runs on PRs. This leaves the PR
> Authors
> > waiting
> > > for authorized users to re-trigger their PRs for them.
> > > Solution : Allow these membership categories Jenkins Admins, MXNet
> > Committers,
> > > and PR Authors to re-trigger PR builds.
> > >
> > > - Introduce per-PR CI bot
> > > Problem: As of date, MXNet CI is automated. It runs every time a
> commit
> > is
> > > pushed onto your Github PR. This results in lot of unnecessary CI
> runs
> > apart
> > > from added costs.
> > > Solution: Switch to Manual Trigger. Users from authorized groups
> (1 of
> > the 3
> > > categories mentioned above) can trigger CI run by adding a simple
> > comment to
> > > PR: “[mxnet-ci] run”.
> > >
> > > --
> > > Thank you,
> > >
> > > AWS MXNet team
> > >
> > >
> > >
> >
> >
>

Re: Join request for MXNet Swift support

[Tao Lv]

Hi Rahul,

Invite is sent to rahulbhal...@protonmail.com. Welcome to the community and
looking forward to your contribution.

-tao

On Mon, Feb 10, 2020 at 1:10 PM Rahul 
wrote:

> Hello,
>
> As per the conversation with [Pedro Larroy](https://twitter.com/plarroy)
> on [Twitter thread](https://twitter.com/plarroy/status/1226408543621771264)
> I would like to join this Slack channel for contributing to MXNet in Swift.
>
> Regards
> Rahul Bhalley
> [ORCID](https://orcid.org/-0002-4574-0390)

Re: [VOTE] Release Apache MXNet (incubating) version 1.6.0.rc2

[Tao Lv]

+1

I tested below items:
1. download artifacts from Apache dist repo;
2. the signature looks good;
3. build from source code with MKL-DNN and MKL on centos;
4. run fp32 and int8 inference of ResNet50 under /example/quantization/.

thanks,
-tao

On Sun, Feb 2, 2020 at 11:00 AM Tao Lv  wrote:

> I see. I was looking at this page:
> https://github.com/apache/incubator-mxnet/releases/tag/1.6.0.rc2
>
> On Sun, Feb 2, 2020 at 4:54 AM Przemysław Trędak 
> wrote:
>
>> Hi Tao,
>>
>> Could you tell me where did you look for it and did not find it? I just
>> checked and both
>> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.6.0.rc2/ and
>> draft of the release on GitHub have them.
>>
>> Thank you
>> Przemek
>>
>> On 2020/02/01 14:23:11, Tao Lv  wrote:
>> > It seems the src tar and signature are missing from the tag.
>> >
>> > On Fri, Jan 31, 2020 at 11:09 AM Przemysław Trędak 
>> > wrote:
>> >
>> > > Dear MXNet community,
>> > >
>> > > This is the vote to release Apache MXNet (incubating) version 1.6.0.
>> > > Voting starts today and will close on Monday 2/3/2020 23:59 PST.
>> > >
>> > > Link to release notes:
>> > > https://cwiki.apache.org/confluence/display/MXNET/1.6.0+Release+notes
>> > >
>> > > Link to release candidate:
>> > > https://github.com/apache/incubator-mxnet/releases/tag/1.6.0.rc2
>> > >
>> > > Link to source and signatures on apache dist server:
>> > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.6.0.rc2/
>> > >
>> > > The differences comparing to previous release candidate 1.6.0.rc1:
>> > >  * Fixes for license issues (#17361, #17375, #17370, #17460)
>> > >  * Bugfix for saving LSTM layer parameter (#17288)
>> > >  * Bugfix for downloading the model from model zoo from multiple
>> processes
>> > > (#17372)
>> > >  * Fixed a symbol.py in AMP for GluonNLP (#17408)
>> > >
>> > >
>> > > Please remember to TEST first before voting accordingly:
>> > > +1 = approve
>> > > +0 = no opinion
>> > > -1 = disapprove (provide reason)
>> > >
>> > >
>> > > Best regards,
>> > > Przemyslaw Tredak
>> > >
>> >
>>
>

Re: [VOTE] Release Apache MXNet (incubating) version 1.6.0.rc2

[Tao Lv]

I see. I was looking at this page:
https://github.com/apache/incubator-mxnet/releases/tag/1.6.0.rc2

On Sun, Feb 2, 2020 at 4:54 AM Przemysław Trędak  wrote:

> Hi Tao,
>
> Could you tell me where did you look for it and did not find it? I just
> checked and both
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.6.0.rc2/ and
> draft of the release on GitHub have them.
>
> Thank you
> Przemek
>
> On 2020/02/01 14:23:11, Tao Lv  wrote:
> > It seems the src tar and signature are missing from the tag.
> >
> > On Fri, Jan 31, 2020 at 11:09 AM Przemysław Trędak 
> > wrote:
> >
> > > Dear MXNet community,
> > >
> > > This is the vote to release Apache MXNet (incubating) version 1.6.0.
> > > Voting starts today and will close on Monday 2/3/2020 23:59 PST.
> > >
> > > Link to release notes:
> > > https://cwiki.apache.org/confluence/display/MXNET/1.6.0+Release+notes
> > >
> > > Link to release candidate:
> > > https://github.com/apache/incubator-mxnet/releases/tag/1.6.0.rc2
> > >
> > > Link to source and signatures on apache dist server:
> > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.6.0.rc2/
> > >
> > > The differences comparing to previous release candidate 1.6.0.rc1:
> > >  * Fixes for license issues (#17361, #17375, #17370, #17460)
> > >  * Bugfix for saving LSTM layer parameter (#17288)
> > >  * Bugfix for downloading the model from model zoo from multiple
> processes
> > > (#17372)
> > >  * Fixed a symbol.py in AMP for GluonNLP (#17408)
> > >
> > >
> > > Please remember to TEST first before voting accordingly:
> > > +1 = approve
> > > +0 = no opinion
> > > -1 = disapprove (provide reason)
> > >
> > >
> > > Best regards,
> > > Przemyslaw Tredak
> > >
> >
>

Re: [VOTE] Release Apache MXNet (incubating) version 1.6.0.rc2

[Tao Lv]

It seems the src tar and signature are missing from the tag.

On Fri, Jan 31, 2020 at 11:09 AM Przemysław Trędak 
wrote:

> Dear MXNet community,
>
> This is the vote to release Apache MXNet (incubating) version 1.6.0.
> Voting starts today and will close on Monday 2/3/2020 23:59 PST.
>
> Link to release notes:
> https://cwiki.apache.org/confluence/display/MXNET/1.6.0+Release+notes
>
> Link to release candidate:
> https://github.com/apache/incubator-mxnet/releases/tag/1.6.0.rc2
>
> Link to source and signatures on apache dist server:
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.6.0.rc2/
>
> The differences comparing to previous release candidate 1.6.0.rc1:
>  * Fixes for license issues (#17361, #17375, #17370, #17460)
>  * Bugfix for saving LSTM layer parameter (#17288)
>  * Bugfix for downloading the model from model zoo from multiple processes
> (#17372)
>  * Fixed a symbol.py in AMP for GluonNLP (#17408)
>
>
> Please remember to TEST first before voting accordingly:
> +1 = approve
> +0 = no opinion
> -1 = disapprove (provide reason)
>
>
> Best regards,
> Przemyslaw Tredak
>

Re: Stopping nightly releases to Pypi

[Tao Lv]

Hi Sam,

Can you simply change the check on L21 in SortTable from `if (x > y)` to
`if (x < y)`? Seems then we can have the newest build at the top of table.

Thanks,
-tao

On Tue, Jan 14, 2020 at 7:07 AM Lin Yuan  wrote:

> Awesome work! It's really convenient to have this page.
>
> Two cents:
> (1) create a link on mxnet page to this one
> (2) reorder the nightly as Tao suggested. Newest first.
>
> On Mon, Jan 13, 2020 at 10:25 AM Skalicky, Sam  >
> wrote:
>
> > Hi All,
> >
> > The html page source is available at the link (view source, its all in a
> > single html file), if someone wants to make modifications I’ll be happy
> to
> > help integrate those changes and get the latest version published in the
> S3
> > bucket. Whenever the final location of the nightly builds is identified
> we
> > can move/modify the script appropriately.
> >
> > Sam
> >
> > > On Jan 12, 2020, at 5:41 PM, Tao Lv  wrote:
> > >
> > > Thank you for the effort, Sam. One minor suggestion: can we sort and
> put
> > > the latest build at the top of the table?
> > >
> > > -tao
> > >
> > > On Mon, Jan 13, 2020 at 7:03 AM Marco de Abreu <
> marco.g.ab...@gmail.com>
> > > wrote:
> > >
> > >> Hi Sam,
> > >>
> > >> that's a great idea, thanks! Can you please adjust the script so it
> uses
> > >> the artifacts that will be published once Shengs PR gets merged?
> > >>
> > >> Best regards,
> > >> Marco
> > >>
> > >> Skalicky, Sam  schrieb am So., 12. Jan.
> > 2020,
> > >> 23:23:
> > >>
> > >>> Hi dev,
> > >>>
> > >>> I made an html page that generates the links to the nightly builds
> > >>> available in the public S3 bucket so you don’t have to log into AWS
> to
> > >> see
> > >>> them.
> > >>>
> > >>> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/index.html
> > >>>
> > >>> Keep in mind we only have builds from January 2020 and December 2019
> so
> > >>> far.
> > >>>
> > >>> Sam
> > >>>
> > >>> On Jan 10, 2020, at 3:05 AM, Sheng Zha  > >>> zhash...@apache.org>> wrote:
> > >>>
> > >>> Size of a change doesn't necessarily reflect the time one spends on
> the
> > >>> navigating the code base and finding the solution. Also, I tend to
> > >> believe
> > >>> that everyone genuinely wants what's best for the project, just from
> > >>> different perspectives.
> > >>>
> > >>> Let's focus on improving the CD solution so that security concerns
> can
> > be
> > >>> addressed too.
> > >>>
> > >>> -sz
> > >>>
> > >>> On 2020/01/09 21:57:30, Chris Olivier   > >>> cjolivie...@apache.org>> wrote:
> > >>> If this tiny fix is representative of the bulk of the reasoning
> behind
> > >> all
> > >>> the the CD churn recently, then this seems to be of some concern.
> > >>>
> > >>> -Chris
> > >>>
> > >>> On Thu, Jan 9, 2020 at 6:32 AM Marco de Abreu <
> marco.g.ab...@gmail.com
> > >>> <mailto:marco.g.ab...@gmail.com>>
> > >>> wrote:
> > >>>
> > >>> Great, thanks a lot sheng!
> > >>>
> > >>> -Marco
> > >>>
> > >>> Sheng Zha mailto:zhash...@apache.org>> schrieb
> am
> > >>> Do., 9. Jan. 2020, 14:28:
> > >>>
> > >>> I'm fixing the CD pipeline in
> > >>> https://github.com/apache/incubator-mxnet/pull/17259/files and will
> > >>> update the s3 publish path so that it's friendly for automatically
> > >>> generating such page.
> > >>>
> > >>> -sz
> > >>>
> > >>> On 2020/01/06 18:19:52, "Lausen, Leonard"  > >>> <mailto:lau...@amazon.com.INVALID>>
> > >>> wrote:
> > >>> Consider a user finds a bug in a nightly version but we can't narrow
> > >>> down the
> > >>> version of mxnet used as the name is constant over time. Or users
> wan't
> > >>> to
> > >>> revert back to the previous nightly version installed but don't know

Re: Stopping nightly releases to Pypi

[Tao Lv]

dist/2019-12-07/dist/mxnet_cu92-1.6.0b20191207-py2.py3-none-manylinux1_x86_64.whl
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2019-12-07/dist/mxnet_cu100-1.6.0b20191207-py2.py3-none-manylinux1_x86_64.whl
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2019-12-07/dist/mxnet_cu101-1.6.0b20191207-py2.py3-none-manylinux1_x86_64.whl
> > (mxnet-cuXXXmkl
> > <
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2019-12-07/dist/mxnet_cu101-1.6.0b20191207-py2.py3-none-manylinux1_x86_64.whl(mxnet-cuXXXmkl
> >
> > <
> >
> >
> >
> >
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2019-12-07/dist/mxnet_cu101-1.6.0b20191207-py2.py3-none-manylinux1_x86_64.whl(mxnet-cuXXXmkl
> >
> > <
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2019-12-07/dist/mxnet_cu101-1.6.0b20191207-py2.py3-none-manylinux1_x86_64.whl(mxnet-cuXXXmkl
> >
> > )
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2019-12-07/dist/mxnet_cu90mkl-1.6.0b20191207-py2.py3-none-manylinux1_x86_64.whl
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2019-12-07/dist/mxnet_cu92mkl-1.6.0b20191207-py2.py3-none-manylinux1_x86_64.whl
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2019-12-07/dist/mxnet_cu100mkl-1.6.0b20191207-py2.py3-none-manylinux1_x86_64.whl
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2019-12-07/dist/mxnet_cu101mkl-1.6.0b20191207-py2.py3-none-manylinux1_x86_64.whl
> >
> > You can easily install these pip wheels in your system either by
> > downloading them to your machine first and then installing by
> > doing:
> >
> > pip install /path/to/downloaded/wheel.whl
> >
> > Or you can install directly by just giving the link to pip like
> > this:
> >
> > pip install
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> https://apache-mxnet.s3-us-west-2.amazonaws.com/dist/2019-12-07/dist/mxnet-1.6.0b20191207-py2.py3-none-manylinux1_x86_64.whl
> >
> > Credit goes to everyone involved (in no particular order) Rakesh
> > Vasudevan
> > Zach Kimberg Manu Seth Sheng Zha Jun Wu Pedro Larroy Chaitanya
> > Bapat
> >
> > Thanks!
> > Sam
> >
> >
> > On Dec 5, 2019, at 1:16 AM, Lausen, Leonard
> >  > <mailto:lau...@amazon.com.INVALID>  > lau...@amazon.com.INVALID
> >
> > wrote:
> >
> > We don't loose pip by hosting on S3. We just don't host nightly
> > releases
> > on Pypi servers and mirror them to several hundred mirrors
> > immediately
> > after each build is published which is very expensive for the Pypi
> > project..
> > People
> > can
> > still
> > install the nightly builds with pip by specifying the -f option.
> >
> > Uploading weekly releases to Pypi will reduce the cost for Pypi by
> > ~75%
> > [1]. It may be acceptable to Pypi, but does it make sense for us?
> > I'm not
> > convinced weekly release on Pypi is a good idea. Consider one
> > release is
> > buggy, users will need to wait for 7 days for a fix. It doesn't
> > provide
> > good user experience.
> > If someone has a stronger conviction about the value of weekly
> > releases on
> > Pypi, that person shall please go ahead and propose it in a
> > separate
> > discussion thread.
> >
> > Currently we don't have generally working nightly builds to Pypi
> > and
> > as a
> > matter of fact we know that we can't have them due to Pypi's policy
> > and our
> > apparent need for large binaries. Given this fact and that no
> > objection was
> > raised by
> > 2019-12-05 at 05:42 UTC, I conclude we have lazy consensus on
> > stopping
> > upload attempts of nightly builds to Pypi.
> >
> > With consensus established, we can change the CI job to stop trying
> > to
> > upload

Re: [apache/incubator-mxnet] [RFC] Apache MXNet 2.0 Roadmap (#16167)

[Tao Lv]

> 3.1. C-API Clean-up
C-API is the foundational API in MXNet that all language bindings depend on.

@szha I'm looking at the item 3.1.2. Could you please explain the scope of 
C-API? Do you mean those APIs sit in the src/c_api/ folder?


-- 
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-mxnet/issues/16167#issuecomment-569850102

Re: [apache/incubator-mxnet] [RFC] Apache MXNet 2.0 Roadmap (#16167)

[Tao Lv]

+1 for using master branch for 2.0 development. I think we need 3 branches at 
least:
1. master branch: for 2.0 development
2. v1.x:  for 1.x development and maintenance
3. v1.7.x: for 1.7.x release

-- 
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-mxnet/issues/16167#issuecomment-569271730

Re: Join the mailing list

[Tao Lv]

Hi Guanxin,

To subscribe the dev@ mail list, you need send request to
dev-subscr...@mxnet.apache.org .
More details here:
https://mxnet.incubator.apache.org/community/contribute#mxnet-dev-communications

Thanks,
-tao

On Fri, Dec 13, 2019 at 11:40 PM Qiao, Guanxin 
wrote:

> Hi,
>
> I am Guanxin from MXNet team. Please add me to the mailing list.
>
> Thanks.
> Guanxin
>

Re: Slack Access

[Tao Lv]

Invitation sent to jd...@amazon.com. Welcome to the community!

-tao

On Fri, Dec 13, 2019 at 11:40 PM Desai, Jay 
wrote:

> Hi please add me on slack, I have high interest in mxnet for contribution
> and research. Thanks
>

Re: Performance regression from removing libiomp5.so

[Tao Lv]

Hi Chris,

>From the licensing standpoint, llvm omp is indeed a choice. But previously
we noticed that building mxnet with cmake and the llvm omp under 3rdparty
folder will cause two runtimes linked to libmxnet.so [1]. Do you think
that's still a problem?

Also with the current two build systems, linking llvm omp means we need
move the binary release process from make to cmake, which i think need more
discussion in the community. It's not likely we can finish that within the
schedule of 1.6.0 release.

[1]
https://github.com/apache/incubator-mxnet/issues/11417#issuecomment-555413002

On Thu, Dec 12, 2019 at 10:28 PM Chris Olivier 
wrote:

> Hi Patric,
>
> The llvm openmp we compile (originally from same Intel source as we all
> know) seems to be Apache 2.0 licensed. Could we use that instead from a
> licensing standpoint?
>
> On Wed, Dec 11, 2019 at 10:36 PM Zhao, Patric 
> wrote:
>
> > Thanks, Sam.
> >
> > The root cause is from different OpenMP library. Intel OpenMP will
> provide
> > better performance as your data shown.
> >
> > Regarding release, since the license issue[1], we can't ship Intel OpenMP
> > in the binary, but the most of performance boost from MKLDNN is still
> > available.
> > I think it should be acceptable to release 1.6 with MKLDNN  + GNU OpenMP
> > for suboptimal performance.
> >
> > To achieve the best performance, user should build from source to enable
> > more advanced features like Intel MKL, Intel OpenMP, AVX512.
> >
> > Thanks,
> >
> > --Patric
> >
> > [1] https://www.apache.org/legal/resolved.html#category-x
> >
> >
> >
> > > -Original Message-
> > > From: Skalicky, Sam 
> > > Sent: Wednesday, December 11, 2019 1:36 PM
> > > To: dev@mxnet.incubator.apache.org
> > > Cc: Keshavan, Arjuna ; Harish, Nihal
> > > 
> > > Subject: Performance regression from removing libiomp5.so
> > >
> > > Hi MXNet community,
> > >
> > > I would like to bring your attention to the performance regression that
> > was
> > > found [1] between 1.5.1 and 1.6.0 due to removing the libiomp5.so
> library
> > > due to licensing issues. This change was made since this library has a
> > category
> > > x license [2] that is not compatible with the MXNet Apache
> > > license/distribution.
> > >
> > > We found that using OpenBLAS instead of MKL BLAS caused a regression
> > > from 1500 samples/sec to 1300 samples/sec a 13.3% regression in
> training
> > > speed for a resnet18 training benchmark on a C5.18xlarge EC2 instance
> > (with
> > > 72 cores). Rebuilding with MKL BLAS showed an increase in performance
> to
> > > 1600 samples/sec in the 1.6.0 branch.
> > >
> > > Please provide your feedback on the licensing issue (are there any
> work-
> > > arounds) and the tradeoff in performance (is the benefit worth trying
> to
> > > include back into MXNet builds).
> > >
> > > Thanks to the efforts of the following folks for working on this issue
> > (in no
> > > particular order):
> > > Patric Zhao
> > > Amol Lele
> > > Tao Lv A
> > > Pedro Larroy
> > > Nihal Harish
> > > Chai Bapat
> > > Arjuna Keshavan
> > > Rong Zhang
> > >
> > > Thanks!
> > > Sam
> > >
> > > [1] https://github.com/apache/incubator-mxnet/issues/16891
> > > [2] https://www.apache.org/legal/resolved.html#category-x
> >
>

Re: Stopping nightly releases to Pypi

[Tao Lv]

* For pypi, we can use mirrors.

On Tue, Dec 3, 2019 at 9:28 PM Tao Lv  wrote:

> As we have many users in China, I'm considering the accessibility of S3.
> For pip, we can mirrors.
>
> On Tue, Dec 3, 2019 at 3:24 PM Lausen, Leonard 
> wrote:
>
>> I would like to remind everyone that lazy consensus is assumed if no
>> objections
>> are raised before 2019-12-05 at 05:42 UTC. There has been some discussion
>> about
>> the proposal, but to my understanding no objections were raised.
>>
>> If the proposal is accepted, MXNet releases would be installed via
>>
>>pip install mxnet
>>
>> And release candidates via
>>
>>   pip install --pre mxnet
>>
>> (or with the respective cuda version specifier appended etc.)
>>
>> To obtain releases built automatically from the master branch, users
>> would need
>> to specify something like "-f
>> http://mxnet.s3.amazonaws.com/mxnet-X/nightly.html; option to pip.
>>
>> Best regards
>> Leonard
>>
>> On Mon, 2019-12-02 at 05:42 +, Lausen, Leonard wrote:
>> > Hi MXNet Community,
>> >
>> > since more than 2 months our binary Python nightly releases published
>> on Pypi
>> > are broken. The problem is that our binaries exceed Pypi's size limit.
>> > Decreasing the binary size by adding compression breaks third-party
>> libraries
>> > loading libmxnet.so
>> https://github.com/apache/incubator-mxnet/issues/16193
>> >
>> > Sheng requested Pypi to increase their size limit:
>> > https://github.com/pypa/pypi-support/issues/50
>> >
>> > Currently "the biggest cost for PyPI from [the many MXNet binaries with
>> > nightly
>> > release to Pypi] is the bandwidth consumed when several hundred mirrors
>> > attempt
>> > to mirror each release immediately after it's published". So Pypi is not
>> > inclined to allow us to upload even larger binaries on a nightly
>> schedule.
>> > Their compromise is to allow it on a weekly cadence.
>> >
>> > However, I would like the community to revisit the necessity of
>> releasing pre-
>> > release binaries to Pypi on a nightly (or weekly) cadence. Instead, we
>> can
>> > release nightly binaries ONLY to a public S3 bucket and instruct users
>> to
>> > install from there. On our side, we only need to prepare a html
>> document that
>> > contains links to all released nightly binaries.
>> > Finally users will install the nightly releases via
>> >
>> >   pip install --pre mxnet-cu101 -f
>> http://mxnet.s3.amazonaws.com/mxnet-cu101/
>> > nightly.html
>> >
>> > Instead of
>> >
>> >   pip install --pre mxnet-cu101
>> >
>> > Of course proper releases and release candidates should still be made
>> > available
>> > via Pypi. Thus releases would be installed via
>> >
>> >   pip install mxnet-cu101
>> >
>> > And release candidates via
>> >
>> >   pip install --pre mxnet-cu101
>> >
>> > This will substantially reduce the costs of the Pypi project and in fact
>> > matches
>> > the installation experience provided by PyTorch. I don't think the
>> benefit of
>> > not including "-f
>> http://mxnet.s3.amazonaws.com/mxnet-cu101/nightly.html;
>> > matches the costs we currently externalize to the Pypi team.
>> >
>> > This suggestion seems uncontroversial to me. Thus I would like to start
>> lazy
>> > consensus. If there are no objections, I will assume lazy consensus on
>> > stopping
>> > nightly releases to Pypi in 72hrs.
>> >
>> > Best regards
>> > Leonard
>>
>

Re: Stopping nightly releases to Pypi

[Tao Lv]

As we have many users in China, I'm considering the accessibility of S3.
For pip, we can mirrors.

On Tue, Dec 3, 2019 at 3:24 PM Lausen, Leonard 
wrote:

> I would like to remind everyone that lazy consensus is assumed if no
> objections
> are raised before 2019-12-05 at 05:42 UTC. There has been some discussion
> about
> the proposal, but to my understanding no objections were raised.
>
> If the proposal is accepted, MXNet releases would be installed via
>
>pip install mxnet
>
> And release candidates via
>
>   pip install --pre mxnet
>
> (or with the respective cuda version specifier appended etc.)
>
> To obtain releases built automatically from the master branch, users would
> need
> to specify something like "-f
> http://mxnet.s3.amazonaws.com/mxnet-X/nightly.html; option to pip.
>
> Best regards
> Leonard
>
> On Mon, 2019-12-02 at 05:42 +, Lausen, Leonard wrote:
> > Hi MXNet Community,
> >
> > since more than 2 months our binary Python nightly releases published on
> Pypi
> > are broken. The problem is that our binaries exceed Pypi's size limit.
> > Decreasing the binary size by adding compression breaks third-party
> libraries
> > loading libmxnet.so
> https://github.com/apache/incubator-mxnet/issues/16193
> >
> > Sheng requested Pypi to increase their size limit:
> > https://github.com/pypa/pypi-support/issues/50
> >
> > Currently "the biggest cost for PyPI from [the many MXNet binaries with
> > nightly
> > release to Pypi] is the bandwidth consumed when several hundred mirrors
> > attempt
> > to mirror each release immediately after it's published". So Pypi is not
> > inclined to allow us to upload even larger binaries on a nightly
> schedule.
> > Their compromise is to allow it on a weekly cadence.
> >
> > However, I would like the community to revisit the necessity of
> releasing pre-
> > release binaries to Pypi on a nightly (or weekly) cadence. Instead, we
> can
> > release nightly binaries ONLY to a public S3 bucket and instruct users to
> > install from there. On our side, we only need to prepare a html document
> that
> > contains links to all released nightly binaries.
> > Finally users will install the nightly releases via
> >
> >   pip install --pre mxnet-cu101 -f
> http://mxnet.s3.amazonaws.com/mxnet-cu101/
> > nightly.html
> >
> > Instead of
> >
> >   pip install --pre mxnet-cu101
> >
> > Of course proper releases and release candidates should still be made
> > available
> > via Pypi. Thus releases would be installed via
> >
> >   pip install mxnet-cu101
> >
> > And release candidates via
> >
> >   pip install --pre mxnet-cu101
> >
> > This will substantially reduce the costs of the Pypi project and in fact
> > matches
> > the installation experience provided by PyTorch. I don't think the
> benefit of
> > not including "-f http://mxnet.s3.amazonaws.com/mxnet-cu101/nightly.html
> "
> > matches the costs we currently externalize to the Pypi team.
> >
> > This suggestion seems uncontroversial to me. Thus I would like to start
> lazy
> > consensus. If there are no objections, I will assume lazy consensus on
> > stopping
> > nightly releases to Pypi in 72hrs.
> >
> > Best regards
> > Leonard
>

Re: Proposal to make MKLDNN as default CPU backend

[Tao Lv]

Regarding the cases listed by Marco:
- AMD CPU
>From my architecture knowledge, what works on C4 instances (with AVX2
support) should also work well on m5a, right? I think mxnet-mkl and
mxnet-cuxxmkl packages have been fully validated on AVX2 machines.
Also, we didn't perform any validation on AMD CPU before, why we need do
that for this time?

- ARM CPU
I don't know we're releasing any convenience binaries for ARM CPU. This
proposal mainly targets those pypi packages.

- Windows
Already validated by CI. We're also releasing mxnet-mkl packages for Win.

- GPU and MKLDNN enabled
Already validated by CI and mxnet-cuxxmkl packages have been released for
several versions.

- Fully reproducible results (medical and financial sector requested that
and we have some flags for cuda)
Not sure I understand this case. We already have MKL-DNN backend for a
while. Functionality and correctness of it have been verified by MXNet
users.

-tao

On Tue, Nov 19, 2019 at 4:41 AM Marco de Abreu 
wrote:

> Sorry, my intent with the "non-standard" phrase was not about general MXNet
> but rather from MKLDNNs point of view, considering that it's being
> developed by Intel, I assumed that MKLDNN might consider non-intel
> use-cases non standard.
>
> -Marco
>
> Skalicky, Sam  schrieb am Mo., 18. Nov. 2019,
> 21:34:
>
> > Thanks Alfredo, if you can create a GitHub issue with notes/steps we can
> > add this to the todo list for integrating with the MXNet CI to test on
> m5a
> > instances too. Then we can start tracking this on a regular basis. It
> would
> > be great to actually test on ARM instances now that AWS has A1 instances
> > too…..ill add it to the wish list ;-D
> >
> > Sam
> >
> > > On Nov 18, 2019, at 12:32 PM, Alfredo Luque  .INVALID>
> > wrote:
> > >
> > > Happy to run some benchmarks on an AWS m5a instance (Epyc) and first
> > > generation AMD Threadripper Gen 1 if someone has something easy to run
> > and
> > > representative.
> > >
> > > On November 18, 2019 at 12:29:31 PM, Skalicky, Sam (
> > > sska...@amazon.com.invalid) wrote:
> > >
> > > Thanks a good idea Alfredo, are you able to help test on AMD CPUs? Or
> is
> > > there someone else in the mxnet dev@ community who can help?
> > >
> > > Sam
> > >
> > >> On Nov 18, 2019, at 12:27 PM, Alfredo Luque
> > >  wrote:
> > >>
> > >> Verifying that there isn’t a slowdown on AMD CPUs (eg; Ryzen / Epyc)
> > > would
> > >> definitely make sense as a requirement. It seems odd to classify that
> as
> > > a
> > >> “nonstandard” use case.
> > >>
> > >> On November 18, 2019 at 12:20:33 PM, Skalicky, Sam (
> > >> sska...@amazon.com.invalid) wrote:
> > >>
> > >> Thanks Patric & team for your work over the years to make MXNet fast
> > with
> > >> MKLDNN!
> > >>
> > >> I think it would be great to make MKLDNN enabled by default. We will
> > need
> > >> to continue producing variants without MKLDNN for those who don’t want
> > it
> > >> (Marco enumerated some use cases). How do you propose to identify the
> > pip
> > >> wheels with/without MKLDNN? Previously we had: mxnet-mkl and
> > > mxnet-cu101mkl
> > >> with MKLDNN. If the plain “mxnet” pip wheel now contains MKLDNN what
> do
> > > you
> > >> propose we call the build without MKLDNN? mxnet-nomkl?
> > >>
> > >> Thanks!
> > >> Sam
> > >>
> > >>> On Nov 18, 2019, at 11:08 AM, Marco de Abreu <
> marco.g.ab...@gmail.com>
> > >> wrote:
> > >>>
> > >>> Hi Patric,
> > >>>
> > >>> First of all, thanks a lot to you and your team for all the effort on
> > >> MXNet
> > >>> and mkldnn!
> > >>>
> > >>> Generally I'm inclined towards your proposal, but I'm thinking about
> > the
> > >>> non-standard use cases:
> > >>> - AMD CPU
> > >>> - ARM CPU
> > >>> - Windows
> > >>> - GPU and MKLDNN enabled
> > >>> - Fully reproducible results (medical and financial sector requested
> > > that
> > >>> and we have some flags for cuda)
> > >>>
> > >>> Is mkldnn fully compatible with these use cases? If not, what would
> > >> happen?
> > >>> If yes, do we have performance numbers?
> > >>>
> > >>> Best regards,
> > >>> Marco
> > >>>
> > >>> Zhao, Patric  schrieb am Mo., 18. Nov. 2019,
> > >> 14:00:
> > >>>
> >  Hi MXNet community,
> > 
> >  From the first MKLDNN backend integrated in release 1.2, the
> community
> > >> is
> >  continuously improving the quality and performance of MKLDNN CPU
> > >> backend.
> >  Nowadays, the MKLDNN backend is widely used for the inference,
> > >> especially
> >  for INT8 inference, and we got lots of very positive feedbacks from
> > >> MXNet
> >  users.
> > 
> >  Achieved milestones as below:
> > 
> >  - MKLDNN integrated into Apache MXNet from release 1.2, Feb, 2018
> [1]
> >  - MKLDNN backend as default CPU backend from source building, Jan,
> > 2019
> > >> [2]
> >  - MKLDNN subgraph optimization as default for the inference, Jul,
> 2019
> > >> [3]
> >  - MKLDNN major version upgrade in release 1.6, Oct, 2019 [4]
> > 
> >  To make more successful and technical 

[ANNOUNCE] Release Apache MXNet (incubating) version 1.5.1

[Tao Lv]

Hi all,

The Apache MXNet (incubating) community is happy to announce Apache MXNet
(incubating) version 1.5.1!

Apache MXNet (incubating) is a deep learning framework designed for both
efficiency and flexibility. It allows you to mix symbolic and imperative
programming to maximize efficiency and productivity.

1.5.1 is a maintenance release incorporating important bug fixes and
important performance improvements.

A full list of the changes in this release can be found in the release
notes:
https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Notes

A link to the download can be found here:
http://mxnet.incubator.apache.org/get_started/download

If you prefer to build from source and experiment with various compile-time
configuration options, use this link to get the instructions:
http://mxnet.incubator.apache.org/get_started/ubuntu_setup.html

http://mxnet.incubator.apache.org/get_started/centos_setup.html

 Or you can download and play with MXNet easily using one of the options
below:

1. The Pip packages can be found here:
https://pypi.python.org/pypi/mxnet

2. The Docker Images can be found here:
https://hub.docker.com/r/mxnet/python/

Links in Maven to the published Scala packages:

https://repository.apache.org/content/repositories/releases/org/apache/mxnet/
https://repository.apache.org/#nexus-search;quick~org.apache.mxnet

and to the experimental Clojure packages:
https://repository.apache.org/content/repositories/releases/org/apache/mxnet/contrib/clojure/

The Release Tag:
https://github.com/apache/incubator-mxnet/tree/1.5.
1

MXNet Resources
- Our discussion forum (https://discuss.mxnet.io)
- MXNet user mailing list (
https://lists.apache.org/list.html?u...@mxnet.apache.org)
- MXNet dev mailing list (
https://lists.apache.org/list.html?d...@mxnet.apache.org)
- StackOverflow mxnet tag (https://stackoverflow.com/questions/tagged/mxnet)
- MXNet website (https://mxnet.incubator.apache.org)
- Github issues (https://github.com/apache/incubator-mxnet/issues)
- Wiki (https://cwiki.apache.org/confluence/display/MXNET)

Attend one of the regular user groups meetings:
https://cwiki.apache.org/confluence/x/7BY0BQ

For more information on Apache MXNet (incubating), please see:
https://mxnet.incubator.apache.org/


Best regards,
Apache MXNet (incubating) Team

___

DISCLAIMER:

Apache MXNet (incubating) is an effort undergoing incubation at The Apache
Software Foundation (ASF), sponsored by the name of Apache Incubator PMC.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other successful
ASF projects. While incubation status is not necessarily a reflection of
the completeness or stability of the code, it does indicate that the
project has yet to be fully endorsed by the ASF.

https://cwiki.apache.org/confluence/x/BINjB

Re: MXNet 1.6.0 release

[Tao Lv]

Hi Przemek,

Thank you for volunteering!

I remember Jun (reminisce@github) has already been working on 1.6.0. You
might need check with him to avoid duplicate effort.

Thanks,
-tao


On Fri, Oct 11, 2019 at 8:00 AM Przemysław Trędak 
wrote:

> Hi MXNet Community,
>
> As the 1.5.1 patch release is done (many thanks Tao!), it is time to
> prepare for the next minor release of MXNet - 1.6.0.
>
> I (ptrendx@github / ptredak@mxnet Slack) would like to manage the release
> of 1.6.0. As it will be the first time for me to manage a release, Sam
> (samskalicky) and Lin (apeforest) agreed to help guiding me through the
> process.
>
> Thanks to Sheng there is a GitHub issue[1] listing major features that
> should go into the 1.6.0, please add any features that you want included
> there.
>
> That said, as we target November for the release, to accommodate for
> extensive testing and bugfixing, the code freeze date is set to October
> 24th 23:59PST. Please reach out to me as soon as possible if you feel that
> you will need an extension of that deadline for your feature.
>
> Sheng created a page on cwiki[2] about the release, I will populate it
> with the information and tracked issues and PRs.
>
> Thank you and let's make the great 1.6.0 release together!
> Przemek
>
> [1] https://github.com/apache/incubator-mxnet/issues/15589
> [2]
> https://cwiki.apache.org/confluence/display/MXNET/1.6.0+Release+Plan+and+Status
>

Re: [REVIEW][ANNOUNCE] Release Apache MXNet (incubating) version 1.5.1

[Tao Lv]

Okay, looks like there is no objections. I will send the announcement to
announce@ and general@ soon.

Thanks,
-tao

On Wed, Oct 9, 2019 at 10:35 AM Tao Lv  wrote:

> Dear community,
>
> This is to review the announcement for 1.5.1 release according to the
> section 3.4 in release process.
>
> ===
>
> The Apache MXNet (incubating) community is happy to announce Apache MXNet
> (incubating) version 1.5.1!
>
> Apache MXNet (incubating) is a deep learning framework designed for both
> efficiency and flexibility. It allows you to mix symbolic and imperative
> programming to maximize efficiency and productivity.
>
> 1.5.1 is a maintenance release incorporating important bug fixes and
> important performance improvements.
>
> A full list of the changes in this release can be found in the release
> notes:
> https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Notes
>
> A link to the download can be found here:
> http://mxnet.incubator.apache.org/get_started/download
>
> If you prefer to build from source and experiment with various
> compile-time configuration options, use this link to get the instructions:
> http://mxnet.incubator.apache.org/get_started/ubuntu_setup.html
>
> http://mxnet.incubator.apache.org/get_started/centos_setup.html
>
>  Or you can download and play with MXNet easily using one of the options
> below:
>
> 1. The Pip packages can be found here:
> https://pypi.python.org/pypi/mxnet
>
> 2. The Docker Images can be found here:
> https://hub.docker.com/r/mxnet/python/
>
> Links in Maven to the published Scala packages:
>
>
> https://repository.apache.org/content/repositories/releases/org/apache/mxnet/
> https://repository.apache.org/#nexus-search;quick~org.apache.mxnet
>
> and to the experimental Clojure packages:
>
> https://repository.apache.org/content/repositories/releases/org/apache/mxnet/contrib/clojure/
>
> The Release Tag:
> https://github.com/apache/incubator-mxnet/tree/1.5.
> <https://github.com/apache/incubator-mxnet/tree/1.5.1>1
>
> MXNet Resources
> - Our discussion forum (https://discuss.mxnet.io)
> - MXNet user mailing list (
> https://lists.apache.org/list.html?u...@mxnet.apache.org)
> - MXNet dev mailing list (
> https://lists.apache.org/list.html?d...@mxnet.apache.org)
> - StackOverflow mxnet tag (
> https://stackoverflow.com/questions/tagged/mxnet)
> - MXNet website (https://mxnet.incubator.apache.org)
> - Github issues (https://github.com/apache/incubator-mxnet/issues)
> - Wiki (https://cwiki.apache.org/confluence/display/MXNET)
>
> Attend one of the regular user groups meetings:
> https://cwiki.apache.org/confluence/x/7BY0BQ
>
> For more information on Apache MXNet (incubating), please see:
> https://mxnet.incubator.apache.org/
>
>
> Best regards,
> Apache MXNet (incubating) Team
>
> ___
>
> DISCLAIMER:
>
> Apache MXNet (incubating) is an effort undergoing incubation at The Apache
> Software Foundation (ASF), sponsored by the name of Apache Incubator PMC.
> Incubation is required of all newly accepted projects until a further
> review indicates that the infrastructure, communications, and decision
> making process have stabilized in a manner consistent with other successful
> ASF projects. While incubation status is not necessarily a reflection of
> the completeness or stability of the code, it does indicate that the
> project has yet to be fully endorsed by the ASF.
>
> https://cwiki.apache.org/confluence/x/BINjB
>

[REVIEW][ANNOUNCE] Release Apache MXNet (incubating) version 1.5.1

[Tao Lv]

Dear community,

This is to review the announcement for 1.5.1 release according to the
section 3.4 in release process.

===

The Apache MXNet (incubating) community is happy to announce Apache MXNet
(incubating) version 1.5.1!

Apache MXNet (incubating) is a deep learning framework designed for both
efficiency and flexibility. It allows you to mix symbolic and imperative
programming to maximize efficiency and productivity.

1.5.1 is a maintenance release incorporating important bug fixes and
important performance improvements.

A full list of the changes in this release can be found in the release
notes:
https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Notes

A link to the download can be found here:
http://mxnet.incubator.apache.org/get_started/download

If you prefer to build from source and experiment with various compile-time
configuration options, use this link to get the instructions:
http://mxnet.incubator.apache.org/get_started/ubuntu_setup.html

http://mxnet.incubator.apache.org/get_started/centos_setup.html

 Or you can download and play with MXNet easily using one of the options
below:

1. The Pip packages can be found here:
https://pypi.python.org/pypi/mxnet

2. The Docker Images can be found here:
https://hub.docker.com/r/mxnet/python/

Links in Maven to the published Scala packages:

https://repository.apache.org/content/repositories/releases/org/apache/mxnet/
https://repository.apache.org/#nexus-search;quick~org.apache.mxnet

and to the experimental Clojure packages:
https://repository.apache.org/content/repositories/releases/org/apache/mxnet/contrib/clojure/

The Release Tag:
https://github.com/apache/incubator-mxnet/tree/1.5.
1

MXNet Resources
- Our discussion forum (https://discuss.mxnet.io)
- MXNet user mailing list (
https://lists.apache.org/list.html?u...@mxnet.apache.org)
- MXNet dev mailing list (
https://lists.apache.org/list.html?d...@mxnet.apache.org)
- StackOverflow mxnet tag (https://stackoverflow.com/questions/tagged/mxnet)
- MXNet website (https://mxnet.incubator.apache.org)
- Github issues (https://github.com/apache/incubator-mxnet/issues)
- Wiki (https://cwiki.apache.org/confluence/display/MXNET)

Attend one of the regular user groups meetings:
https://cwiki.apache.org/confluence/x/7BY0BQ

For more information on Apache MXNet (incubating), please see:
https://mxnet.incubator.apache.org/


Best regards,
Apache MXNet (incubating) Team

___

DISCLAIMER:

Apache MXNet (incubating) is an effort undergoing incubation at The Apache
Software Foundation (ASF), sponsored by the name of Apache Incubator PMC.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other successful
ASF projects. While incubation status is not necessarily a reflection of
the completeness or stability of the code, it does indicate that the
project has yet to be fully endorsed by the ASF.

https://cwiki.apache.org/confluence/x/BINjB

Re: new website, docs code freeze

[Tao Lv]

I just sent out the announcement of 1.5.1 release for review. But still not
sure how to change  http://mxnet.incubator.apache.org/get_started and
http://mxnet.incubator.apache.org/get_started/download to accommodate.

Can anyone help on that?

thanks,
-tao

On Wed, Oct 9, 2019 at 10:24 AM Zhao, Patric  wrote:

> Thanks, Thomas, it's good to have a site-wide search bar 
>
>
>
> FYI, the similar thing in https://pytorch.org/
>
>
>
> --Patric
>
>
>
> > -Original Message-
>
> > From: Thomas DELTEIL 
>
> > Sent: Wednesday, October 9, 2019 1:41 AM
>
> > To: dev@mxnet.incubator.apache.org
>
> > Subject: Re: new website, docs code freeze
>
> >
>
> > Hi Patric,
>
> >
>
> > The search bar is available in the python docs:
>
> > https://mxnet.apache.org/api/python/docs/api/ (on the top right). Since
> the
>
> > homepage is not built by sphinx anymore there are no more search bar
> there.
>
> > We are considering using an external plugin to maintain a site-wide
> index and
>
> > provide better search experience than the sphinx one.
>
> > btw you were asking about the mkldnn tutorials, they are now here:
>
> > https://mxnet.apache.org/api/python/docs/tutorials/performance/backend
>
> > /mkldnn/index.html
>
> >
>
> > All the best,
>
> >
>
> > Thomas Delteil
>
> >
>
> > Le lun. 7 oct. 2019 à 19:58, Zhao, Patric  a
> écrit :
>
> >
>
> > > I find there is no "search bar" in the website today.
>
> > >
>
> > > Could anyone check it?
>
> > >
>
> > > Thanks,
>
> > >
>
> > > --Patric
>
> > >
>
> > > > -Original Message-
>
> > > > From: Thomas DELTEIL 
>
> > > > Sent: Saturday, October 5, 2019 3:41 AM
>
> > > > To: dev@mxnet.incubator.apache.org
>
> > > > Subject: Re: new website, docs code freeze
>
> > > >
>
> > > > Hi Haibin,
>
> > > >
>
> > > > We are currently working with Soji on overhauling the way the python
>
> > > > docs are organized to get better and more consistent docs with full
>
> > > > coverage,
>
> > > the
>
> > > > current system is a brittle and hard to browse. We hope to finish
>
> > > > our dev work by tonight, ETA for early next week.
>
> > > > There is no ETA on bringing back the old docs, though that's the
>
> > > > next
>
> > > highest
>
> > > > priority feature on the list after improving the coverage of the
>
> > > > python
>
> > > API.
>
> > > >
>
> > > > All the best,
>
> > > >
>
> > > > Thomas Delteil
>
> > > >
>
> > > > On Fri, Oct 4, 2019, 12:34 Haibin Lin 
> wrote:
>
> > > >
>
> > > > > Yes, that is the correct one.
>
> > > > >
>
> > > > > On a separate note, are we removing documentation versioning from
>
> > > > > the website? How do we switch between the master/nightly version
>
> > > > > and the stable version for the python API doc? Maybe there's a
>
> > > > > switch somewhere but I cannot find it.
>
> > > > >
>
> > > > > Also, I find that the API doc for many methods are missing, for
>
> > > > > example, the Dataset.transform function has detailed documentation
>
> > > > > on input and output types, but the doc only shows the one-line
>
> > > > > description of the method
>
> > > > >
>
> > > > >
>
> > > >
>
> > https://mxnet.apache.org/api/python/docs/api/gluon/_autogen/mxnet.gl
>
> > > > u
>
> > > > o
>
> > > > > n.data.Dataset.html?highlight=dataset#
>
> > > > > .
>
> > > > > Same for other methods such as filter, shard, etc.
>
> > > > >
>
> > > > > Thanks.
>
> > > > >
>
> > > > > Best,
>
> > > > > Haibin
>
> > > > >
>
> > > > >
>
> > > > > On Thu, Oct 3, 2019 at 7:59 AM Aaron Markham
>
> > > > > 
>
> > > > > wrote:
>
> > > > >
>
> > > > > > Hi Haibin, you mean this one?
>
> > > > > >
>
> > > > > >
>
> > > > > https://github.com/apache/incubator-
>
> > > > mxnet/blob/master/docs/static_site
>
> > > > > /src/pages/api/faq/distributed_training.md
>
> > > > > > If so, it looks like a link update is needed.
>
> > > > > >
>
> > > > > > On Wed, Oct 2, 2019 at 9:42 PM Haibin Lin
>
> > > > > > 
>
> > > > > > wrote:
>
> > > > > > >
>
> > > > > > > I find that the 'distributed training with KVStore' tutorial
>
> > > > > > > is
>
> > > gone.
>
> > > > > Are
>
> > > > > > > we adding it back?
>
> > > > > > >
>
> > > > > >
>
> > > > >
>
> > > >
>
> > https://mxnet.apache.org/api/python/docs/tutorials/performance/index
>
> > > > .h
>
> > > > > tml?highlight=distributed#distributed-training
>
> > > > > > >
>
> > > > > > >
>
> > > > > > > On Tue, Oct 1, 2019 at 4:54 AM Marco de Abreu
>
> > > > > > > 
> > > > > >
>
> > > > > > > wrote:
>
> > > > > > >
>
> > > > > > > > Thanks for the update, great job!
>
> > > > > > > >
>
> > > > > > > > Are the lighthouse results accessible somewhere? I'd be
> curious.
>
> > > > > > > >
>
> > > > > > > > -Marco
>
> > > > > > > >
>
> > > > > > > > Thomas DELTEIL  schrieb am Di.,
> 1.
>
> > > Okt.
>
> > > > > > 2019,
>
> > > > > > > > 13:49:
>
> > > > > > > >
>
> > > > > > > > > Update on the website:
>
> > > > > > > > >
>
> > > > > > > > > Highlights:
>
> > > > > > > > > - Broken links: a good amount of them have been fixed in
>
> > > > > > > > > this
>
> 

Update for 1.5.1 patch release

[Tao Lv]

Hi dev,

I'm glad to say that the rc0 of 1.5.1 patch release has passed the vote on
general@. Please find the voting thread at:
https://lists.apache.org/thread.html/282f7911768dab61ddf8f70adcce34ef0afb285046093b3ff0bafb7e@%3Cgeneral.incubator.apache.org%3E


Now I'm proceeding the release process and have several questions there.
Hope someone can help to answer:

1. Change the 1.5.1.rc0 tag to formal 1.5.1. Seems the step 3.1.1 on the
cwiki page [1] doesn't work. It says:

"Go to the GitHub repo’s “releases” tab

Click “Draft a new release”

Provide the release tag in the form of “..”
Select the commit by clicking Target: master > the passing release
candidate tag"

But I cannot find "the passing release candidate tag" in the drop list.
There're branches and recent commits. Once I create a new tag, how about
the old tag of 1.5.1.rc0?

2. Step 3.1.2 is also confusing to me. Not sure what should be done at step
3 and what need to be uploaded at step 4.

3. As we have a new website now, I guess there are some changes for the
step 3.2. Can anyone help to clarify this?

Thanks,
-tao

[1] https://cwiki.apache.org/confluence/display/MXNET/Release+Process

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

[Tao Lv]

Hi Mike,

Thank you for raising the issue. I will change the link to the new website:
https://mxnet.incubator.apache.org/get_started

Thanks,
-tao

On Wed, Sep 25, 2019 at 6:42 AM Michael Wall  wrote:

> Cc'ing dev@mxnet.i.a.o this time
>
> Mike
>
> On Tue, Sep 24, 2019, 17:47 Michael Wall  wrote:
>
> > FYI, the release notes link to
> > https://mxnet.incubator.apache.org/install/index.html which is returning
> > a 404.  Maybe related to the new website?  Same for
> > https://mxnet.incubator.apache.org/versions/master/install/index.html
> which
> > is the first result of my Google search for 'install mxnet'.
> >
> > Mike
> >
> > On Tue, Sep 24, 2019 at 1:26 AM Tao Lv  wrote:
> >
> >> Thank you Mike! I'm sorry for missing your vote on dev@.
> >>
> >> To other MXNet mentors, may I have your opinion on this vote?
> >>
> >> Thanks,
> >> -tao
> >>
> >> On Sun, Sep 22, 2019 at 11:54 PM Michael Wall 
> wrote:
> >>
> >> > +1 (binding)
> >> >
> >> > - Built from src without opencv
> >> > - sha512 signature are good
> >> > - gpg key for release manager in
> >> >   https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS and gpg
> >> > --verify
> >> >   passes
> >> > - many but not all of the license issues from the 1.5.0 release have
> >> been
> >> >   addressed, see
> >> >
> >> >
> >>
> https://lists.apache.org/thread.html/5365cdab7dee08d220e32decc76fd54aa05e29bc891c416828cb64d2@%3Cgeneral.incubator.apache.org%3E
> >> >   Ticket tracking these is
> >> >   https://github.com/apache/incubator-mxnet/issues/15542
> >> >   where all the license issues are being tracked for the 1.6 release
> >> >
> >> >
> >> > On Sun, Sep 22, 2019 at 11:34 AM Tao Lv  wrote:
> >> >
> >> > > Dear community,
> >> > >
> >> > > This is a call for a releasing Apache MXNet (incubating) 1.5.1,
> >> release
> >> > > candidate 0.
> >> > >
> >> > > Apache MXNet (incubating) community has voted and approved the
> >> release.
> >> > >
> >> > > Vote thread:
> >> > >
> >> > >
> >> > >
> >> >
> >>
> https://lists.apache.org/thread.html/32f9e98d3409c84c01703ce89843510b0f5c47a54d6d5327f6279050@%3Cdev.mxnet.apache.org%3E
> >> > >
> >> > > Result thread:
> >> > >
> >> > >
> >> >
> >>
> https://lists.apache.org/thread.html/964c0a228c2d6bfbb8428be8c1454f660b8b4a684d334cfbdf317f57@%3Cdev.mxnet.apache.org%3E
> >> > >
> >> > >
> >> > > The source tarball, including signatures, digests, etc. can be found
> >> at:
> >> > >
> >> > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.5.1.rc0/
> >> > >
> >> > > The tag to be voted upon is 1.5.1.rc0:
> >> > > https://github.com/apache/incubator-mxnet/releases/tag/1.5.1.rc0
> >> > >
> >> > > The release hash is  c9818480680f84daa6e281a974ab263691302ba8  :
> >> > >
> >> > >
> >> >
> >>
> https://github.com/apache/incubator-mxnet/commit/c9818480680f84daa6e281a974ab263691302ba8
> >> > >
> >> > >
> >> > > KEYS file available:
> >> > >
> >> > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS
> >> > >
> >> > > For information about the contents of this release, see:
> >> > >
> https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Notes
> >> > >
> >> > > The vote will be open for 72 hours.
> >> > >
> >> > > [ ] +1 release this package as #
> >> > > [ ] +0 no opinion
> >> > > [ ] -1 do not release this package because...
> >> > >
> >> > >
> >> > > Best Regards,
> >> > >
> >> > > -tao
> >> > >
> >> >
> >>
> >
>

[RESULTS][VOTE] Release Apache MXNet (incubating) 1.5.1.rc0

[Tao Lv]

Dear MXNet community,


I'm happy to announce the results of the vote.

This vote passes with 9 +1 votes (4 binding), no 0 votes, and 0 -1 vote.

+1 votes

* Qing Lan (binding)

* Patric Zhao

* Lin Yuan

* Chaitanya Bapat

* Anirudh Subramanian (binding)

* Sandeep Krishnamurthy (binding)

* Lai Wei

* Srivastava, Rohit Kumar

* Carin Meier (binding)



0 votes

* No votes



-1 votes

* No votes



Vote thread can be found here [1]. The list of members can be found here
[2].

I'll continue with the release process and the release announcement will
follow in the next week.



Thanks,

-tao



[1]
https://lists.apache.org/thread.html/32f9e98d3409c84c01703ce89843510b0f5c47a54d6d5327f6279050@%3Cdev.mxnet.apache.org%3E

[2] http://incubator.apache.org/projects/mxnet.html

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

[Tao Lv]

Hi Mike,
May I have your opinion? I'm going to count the vote now. Thanks!

Hi Marco,
Thanks for your input. We indeed fixed several license issues in this patch
release but still have to leave over the license issue of cub and mklml to
the next minor release.

-tao

On Sat, Sep 21, 2019 at 12:04 AM Marco de Abreu 
wrote:

> We only need a mentors vote on general, but it certainly would be
> appreciated especially considering the licensing issues we're constantly
> encountering. One part of graduation is having a number of releases that
> went without issues.
>
> -Marco
>
> Tao Lv  schrieb am Fr., 20. Sep. 2019, 17:10:
>
> > Sure. Really appreciate your help, Mike.
> >
> > -tao
> >
> > On Fri, Sep 20, 2019 at 10:48 PM Michael Wall  wrote:
> >
> > > Tao,
> > >
> > > I can take a look tonight if you want to wait.
> > >
> > > Mike
> > >
> > > On Fri, Sep 20, 2019 at 10:45 AM Tao Lv  wrote:
> > >
> > > > Thank you all for the support!
> > > >
> > > > One question, do we need mentor's vote here?
> > > >
> > > > Thanks,
> > > > -tao
> > > >
> > > > On Fri, Sep 20, 2019 at 10:25 PM Carin Meier 
> > > wrote:
> > > >
> > > > > +1 built and tested the Clojure package
> > > > >
> > > > > On Fri, Sep 20, 2019 at 12:08 AM Srivastava, Rohit Kumar <
> > > > > srivastava@buckeyemail.osu.edu> wrote:
> > > > >
> > > > > > +1
> > > > > > build mxnet from source with large tensor support. Ran tests only
> > for
> > > > > > large array. All passed !
> > > > > >
> > > > > > On 9/19/19, 2:58 PM, "Lai Wei"  wrote:
> > > > > >
> > > > > > +1
> > > > > >
> > > > > > build from source on GPU and tested with gluon estimator and
> > > latest
> > > > > > keras-mxnet.
> > > > > >
> > > > > >
> > > > > > Best Regards
> > > > > >
> > > > > > Lai
> > > > > >
> > > > > >
> > > > > > On Thu, Sep 19, 2019 at 1:02 PM sandeep krishnamurthy <
> > > > > > sandeep.krishn...@gmail.com> wrote:
> > > > > >
> > > > > > > Thank you Tao for leading this and all the community
> members
> > > for
> > > > > > helping in
> > > > > > > this release.
> > > > > > >
> > > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > >
> > > > > > > -[Y] Are release files in correct location?
> > > > > > >
> > > > > > > -[Y] Do release files have the word incubating in their
> name?
> > > > > > >
> > > > > > > -[Y] Are the digital signature and hashes correct?
> > > > > > >
> > > > > > > -[Y] Does DISCLAIMER file exist?
> > > > > > >
> > > > > > > -[Y] Do LICENSE and NOTICE files exists?
> > > > > > >
> > > > > > > -[Y] Is the LICENSE and NOTICE text correct?
> > > > > > >
> > > > > > > -[Y] Is the NOTICE year correct?
> > > > > > >
> > > > > > > -[Y] Un-included software dependencies are not mentioned in
> > > > LICENSE
> > > > > > or
> > > > > > > NOTICE?
> > > > > > >
> > > > > > > -[Y] License information is not mentioned in NOTICE?
> > > > > > >
> > > > > > > Is there any 3rd party code contained inside the release?
> If
> > > so:
> > > > > > >
> > > > > > > -[N] Does the software have a compatible license?
> > > > > > >
> > > > > > > -[Y] Are all software licenses mentioned in LICENSE?
> > > > > > >
> > > > > > > -[Y] Is the full text of the licenses (or pointers to it)
> in
> > > > > LICENSE?
> > > > > > >
> > > > > > > Is any of this code Apache licensed? Do they

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

[Tao Lv]

Sure. Really appreciate your help, Mike.

-tao

On Fri, Sep 20, 2019 at 10:48 PM Michael Wall  wrote:

> Tao,
>
> I can take a look tonight if you want to wait.
>
> Mike
>
> On Fri, Sep 20, 2019 at 10:45 AM Tao Lv  wrote:
>
> > Thank you all for the support!
> >
> > One question, do we need mentor's vote here?
> >
> > Thanks,
> > -tao
> >
> > On Fri, Sep 20, 2019 at 10:25 PM Carin Meier 
> wrote:
> >
> > > +1 built and tested the Clojure package
> > >
> > > On Fri, Sep 20, 2019 at 12:08 AM Srivastava, Rohit Kumar <
> > > srivastava@buckeyemail.osu.edu> wrote:
> > >
> > > > +1
> > > > build mxnet from source with large tensor support. Ran tests only for
> > > > large array. All passed !
> > > >
> > > > On 9/19/19, 2:58 PM, "Lai Wei"  wrote:
> > > >
> > > > +1
> > > >
> > > > build from source on GPU and tested with gluon estimator and
> latest
> > > > keras-mxnet.
> > > >
> > > >
> > > > Best Regards
> > > >
> > > > Lai
> > > >
> > > >
> > > > On Thu, Sep 19, 2019 at 1:02 PM sandeep krishnamurthy <
> > > > sandeep.krishn...@gmail.com> wrote:
> > > >
> > > > > Thank you Tao for leading this and all the community members
> for
> > > > helping in
> > > > > this release.
> > > > >
> > > > >
> > > > > +1
> > > > >
> > > > >
> > > > > -[Y] Are release files in correct location?
> > > > >
> > > > > -[Y] Do release files have the word incubating in their name?
> > > > >
> > > > > -[Y] Are the digital signature and hashes correct?
> > > > >
> > > > > -[Y] Does DISCLAIMER file exist?
> > > > >
> > > > > -[Y] Do LICENSE and NOTICE files exists?
> > > > >
> > > > > -[Y] Is the LICENSE and NOTICE text correct?
> > > > >
> > > > > -[Y] Is the NOTICE year correct?
> > > > >
> > > > > -[Y] Un-included software dependencies are not mentioned in
> > LICENSE
> > > > or
> > > > > NOTICE?
> > > > >
> > > > > -[Y] License information is not mentioned in NOTICE?
> > > > >
> > > > > Is there any 3rd party code contained inside the release? If
> so:
> > > > >
> > > > > -[N] Does the software have a compatible license?
> > > > >
> > > > > -[Y] Are all software licenses mentioned in LICENSE?
> > > > >
> > > > > -[Y] Is the full text of the licenses (or pointers to it) in
> > > LICENSE?
> > > > >
> > > > > Is any of this code Apache licensed? Do they have NOTICE files?
> > If
> > > > so:
> > > > >
> > > > > -[Y] Have relevant parts of those NOTICE files been added to
> this
> > > > NOTICE
> > > > >
> > > > > file?
> > > > >
> > > > > -[Y] Do all source files have ASF headers?
> > > > >
> > > > > -[Y] Do the contents of the release match with what's tagged in
> > > > version
> > > > > control?
> > > > >
> > > > > -[N] Are there any unexpected binary files in the release?
> > > > >
> > > > > -[Y] Can you compile from source? Are the instruction clear?
> > > > >
> > > > >
> > > > > Except the license issue mentioned in this Github issue -
> > > > > https://github.com/apache/incubator-mxnet/issues/15542
> > > > >
> > > > >
> > > > > I was able to build from source on GPU(p3.2x EC2 instance) and
> > run
> > > > > opperf-operator
> > > > > benchmark utilit
> > > > > <
> > > >
> https://github.com/apache/incubator-mxnet/tree/master/benchmark/opperf
> > >y
> > > > > successfully
> > > > > with no regression compared to v1.5.0.
> > > > >
> > > >   

Re: Code freeze for 1.5.1 patch release

[Tao Lv]

Great. Thank you, Carin!

On Fri, Sep 20, 2019 at 10:24 PM Carin Meier  wrote:

> The Clojure jars have been built and put to staging
>
>
> https://repository.apache.org/content/repositories/staging/org/apache/mxnet/contrib/clojure/clojure-mxnet-linux-cpu/1.5.1/
>
> https://repository.apache.org/content/repositories/staging/org/apache/mxnet/contrib/clojure/clojure-mxnet-linux-gpu/1.5.1/
>
> https://repository.apache.org/content/repositories/staging/org/apache/mxnet/contrib/clojure/clojure-mxnet-osx-cpu/1.5.1/
>
> On Tue, Sep 17, 2019 at 2:21 PM Tao Lv  wrote:
>
> > I have started the voting thread and move the language binding to after
> the
> > vote passes.
> > If someone has concerns about this decision, please comment in the voting
> > thread.
> >
> > Thanks,
> > -tao
> >
> > On Wed, Sep 18, 2019 at 1:09 AM Carin Meier 
> wrote:
> >
> > > To clarify, the Clojure source is included is the vote, the built jar
> is
> > > not
> > >
> > > On Tue, Sep 17, 2019 at 1:08 PM Carin Meier 
> > wrote:
> > >
> > > > We have done that on other releases. That is, vote without Clojure
> > > > package. Someone feel free to clarify the official stance.
> > > >
> > > > On Tue, Sep 17, 2019 at 12:55 PM Lin Yuan 
> wrote:
> > > >
> > > >> Hi Tao,
> > > >>
> > > >> If the voting is on the source and not requiring the language
> > bindings,
> > > >> can
> > > >> we do the voting in parallel with the release?
> > > >>
> > > >> Carin/Qing, please help to clarify if the R/Clojure language
> bindings
> > > are
> > > >> required for voting.
> > > >>
> > > >> Thanks,
> > > >>
> > > >> Lin
> > > >>
> > > >> On Tue, Sep 17, 2019 at 7:32 AM Tao Lv  wrote:
> > > >>
> > > >> > Thanks for your help, Carin. Per step 1.14 of  the release process
> > > [1],
> > > >> > stage repo links should be included in the voting email.
> > > >> >
> > > >> > Scala packages are done. Thanks to the help from @Lanking.
> > > >> >
> > > >> > We still have problem with R package on Windows. @yajiedesign is
> > > >> helping on
> > > >> > that.
> > > >> >
> > > >> > Again thanks for all of your support and patience.
> > > >> >
> > > >> > -tao
> > > >> >
> > > >> > [1]
> > https://cwiki.apache.org/confluence/display/MXNET/Release+Process
> > > >> >
> > > >> > On Tue, Sep 17, 2019 at 6:10 PM Carin Meier  >
> > > >> wrote:
> > > >> >
> > > >> > > I will be able to build the Clojure packages on Friday. I don’t
> > > >> believe
> > > >> > > this needs to hold up the voting. I believe the voting is only
> on
> > > the
> > > >> > > source.
> > > >> > >
> > > >> > > -Carin
> > > >> > >
> > > >> > > On Mon, Sep 16, 2019 at 7:05 PM Lin Yuan 
> > > wrote:
> > > >> > >
> > > >> > > > Hi Tao,
> > > >> > > >
> > > >> > > > Thanks for uploading the artifacts. May I know what the
> current
> > > >> status
> > > >> > of
> > > >> > > > Scala, Clojure and R packages and any help you need from the
> > > >> community
> > > >> > to
> > > >> > > > complete?
> > > >> > > >
> > > >> > > > Thanks,
> > > >> > > >
> > > >> > > > Lin
> > > >> > > >
> > > >> > > > On Fri, Sep 6, 2019 at 7:35 AM Tao Lv 
> wrote:
> > > >> > > >
> > > >> > > > > Update:
> > > >> > > > >
> > > >> > > > > Artifacts of 1.5.1.rc0 have been uploaded to github and
> Apache
> > > >> dist.
> > > >> > > > Before
> > > >> > > > > voting, we still need some time to build packages for Scala,
> > > >> Clojure
> > > >> > > and
> > > >> > > > R.
> > > >> > > > 

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

[Tao Lv]

Thank you all for the support!

One question, do we need mentor's vote here?

Thanks,
-tao

On Fri, Sep 20, 2019 at 10:25 PM Carin Meier  wrote:

> +1 built and tested the Clojure package
>
> On Fri, Sep 20, 2019 at 12:08 AM Srivastava, Rohit Kumar <
> srivastava@buckeyemail.osu.edu> wrote:
>
> > +1
> > build mxnet from source with large tensor support. Ran tests only for
> > large array. All passed !
> >
> > On 9/19/19, 2:58 PM, "Lai Wei"  wrote:
> >
> > +1
> >
> > build from source on GPU and tested with gluon estimator and latest
> > keras-mxnet.
> >
> >
> > Best Regards
> >
> > Lai
> >
> >
> > On Thu, Sep 19, 2019 at 1:02 PM sandeep krishnamurthy <
> > sandeep.krishn...@gmail.com> wrote:
> >
> > > Thank you Tao for leading this and all the community members for
> > helping in
> > > this release.
> > >
> > >
> > > +1
> > >
> > >
> > > -[Y] Are release files in correct location?
> > >
> > > -[Y] Do release files have the word incubating in their name?
> > >
> > > -[Y] Are the digital signature and hashes correct?
> > >
> > > -[Y] Does DISCLAIMER file exist?
> > >
> > > -[Y] Do LICENSE and NOTICE files exists?
> > >
> > > -[Y] Is the LICENSE and NOTICE text correct?
> > >
> > > -[Y] Is the NOTICE year correct?
> > >
> > > -[Y] Un-included software dependencies are not mentioned in LICENSE
> > or
> > > NOTICE?
> > >
> > > -[Y] License information is not mentioned in NOTICE?
> > >
> > > Is there any 3rd party code contained inside the release? If so:
> > >
> > > -[N] Does the software have a compatible license?
> > >
> > > -[Y] Are all software licenses mentioned in LICENSE?
> > >
> > > -[Y] Is the full text of the licenses (or pointers to it) in
> LICENSE?
> > >
> > > Is any of this code Apache licensed? Do they have NOTICE files? If
> > so:
> > >
> > > -[Y] Have relevant parts of those NOTICE files been added to this
> > NOTICE
> > >
> > > file?
> > >
> > > -[Y] Do all source files have ASF headers?
> > >
> > > -[Y] Do the contents of the release match with what's tagged in
> > version
> > > control?
> > >
> > > -[N] Are there any unexpected binary files in the release?
> > >
> > > -[Y] Can you compile from source? Are the instruction clear?
> > >
> > >
> > > Except the license issue mentioned in this Github issue -
> > > https://github.com/apache/incubator-mxnet/issues/15542
> > >
> > >
> > > I was able to build from source on GPU(p3.2x EC2 instance) and run
> > > opperf-operator
> > > benchmark utilit
> > > <
> > https://github.com/apache/incubator-mxnet/tree/master/benchmark/opperf>y
> > > successfully
> > > with no regression compared to v1.5.0.
> > >
> > >
> > >
> > >
> > > On Thu, Sep 19, 2019 at 11:51 AM Anirudh Subramanian <
> > > anirudh2...@gmail.com>
> > > wrote:
> > >
> > > > +1
> > > >
> > > > Build from source with cmake and ran unittest for gluon and amp.
> > > >
> > > > Noticed that test_sync_batchnorm fails on p3.8xlarge (hidden by
> > the CI
> > > > because passes on machines with 1 or 2 gpus).
> > > > I have opened an issue for the same
> > > > https://github.com/apache/incubator-mxnet/issues/16214 though I
> > think
> > > its
> > > > not a blocker for this release.
> > > >
> > > > Anirudh
> > > >
> > > > On Thu, Sep 19, 2019 at 11:28 AM Chaitanya Bapat <
> > chai.ba...@gmail.com>
> > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > Correctly built for GPU, CPU on Ubuntu 14.01 (10.1 Cuda for
> GPU)
> > > > > Ran image classification (resnet50+cifar10)
> > > > > Ran Operator Performance (opperf)
> > &g

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

[Tao Lv]

Hi community,

Friendly reminder: it is less than 1.5 days remaining, so please take your
time to verify and vote.

Thanks,
-tao

On Thu, Sep 19, 2019 at 3:06 PM Lin Yuan  wrote:

> +1
> Tested Horovod on GPU
>
> On Wed, Sep 18, 2019 at 6:16 AM Zhao, Patric 
> wrote:
>
> > +1
> >
> > Tested MKLDNN backend and everything looks great.
> >
> > > -Original Message-
> > > From: Qing Lan 
> > > Sent: Wednesday, September 18, 2019 2:20 AM
> > > To: dev@mxnet.incubator.apache.org
> > > Subject: Re: [VOTE] Release Apache MXNet (incubating) 1.5.1.rc0
> > >
> > > +1 for Scala/Java test. Passed all tests for CPU/GPU build.
> > > Also tested build from source with static build.
> > >
> > > Thanks,
> > > Qing
> > > 
> > > From: Tao Lv 
> > > Sent: Tuesday, September 17, 2019 14:14
> > > To: dev@mxnet.incubator.apache.org 
> > > Subject: [VOTE] Release Apache MXNet (incubating) 1.5.1.rc0
> > >
> > > Dear MXNet community,
> > >
> > >
> > >
> > > This is the 3-day vote to release Apache MXNet (incubating) version
> > 1.5.1.
> > >
> > > Voting on dev@ will start September 17, 12:00pm (PST)  and close on
> > > September 20, 12:00pm (PST).
> > >
> > >
> > >
> > > 1) Link to release notes:
> > >
> > > https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Notes
> > >
> > >
> > >
> > > 2) Link to release candidate:
> > >
> > > https://github.com/apache/incubator-mxnet/releases/tag/1.5.1.rc0
> > >
> > >
> > >
> > > 3) Link to source and signatures on Apache dist server:
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.5.1.rc0/
> > >
> > >
> > >
> > > Please remember to TEST first before voting accordingly:
> > >
> > > +1 = approve
> > >
> > > +0 = no opinion
> > >
> > > -1 = disapprove (provide reason)
> > >
> > >
> > >
> > > Thanks,
> > >
> > > -tao
> >
>

Re: Code freeze for 1.5.1 patch release

[Tao Lv]

I have started the voting thread and move the language binding to after the
vote passes.
If someone has concerns about this decision, please comment in the voting
thread.

Thanks,
-tao

On Wed, Sep 18, 2019 at 1:09 AM Carin Meier  wrote:

> To clarify, the Clojure source is included is the vote, the built jar is
> not
>
> On Tue, Sep 17, 2019 at 1:08 PM Carin Meier  wrote:
>
> > We have done that on other releases. That is, vote without Clojure
> > package. Someone feel free to clarify the official stance.
> >
> > On Tue, Sep 17, 2019 at 12:55 PM Lin Yuan  wrote:
> >
> >> Hi Tao,
> >>
> >> If the voting is on the source and not requiring the language bindings,
> >> can
> >> we do the voting in parallel with the release?
> >>
> >> Carin/Qing, please help to clarify if the R/Clojure language bindings
> are
> >> required for voting.
> >>
> >> Thanks,
> >>
> >> Lin
> >>
> >> On Tue, Sep 17, 2019 at 7:32 AM Tao Lv  wrote:
> >>
> >> > Thanks for your help, Carin. Per step 1.14 of  the release process
> [1],
> >> > stage repo links should be included in the voting email.
> >> >
> >> > Scala packages are done. Thanks to the help from @Lanking.
> >> >
> >> > We still have problem with R package on Windows. @yajiedesign is
> >> helping on
> >> > that.
> >> >
> >> > Again thanks for all of your support and patience.
> >> >
> >> > -tao
> >> >
> >> > [1] https://cwiki.apache.org/confluence/display/MXNET/Release+Process
> >> >
> >> > On Tue, Sep 17, 2019 at 6:10 PM Carin Meier 
> >> wrote:
> >> >
> >> > > I will be able to build the Clojure packages on Friday. I don’t
> >> believe
> >> > > this needs to hold up the voting. I believe the voting is only on
> the
> >> > > source.
> >> > >
> >> > > -Carin
> >> > >
> >> > > On Mon, Sep 16, 2019 at 7:05 PM Lin Yuan 
> wrote:
> >> > >
> >> > > > Hi Tao,
> >> > > >
> >> > > > Thanks for uploading the artifacts. May I know what the current
> >> status
> >> > of
> >> > > > Scala, Clojure and R packages and any help you need from the
> >> community
> >> > to
> >> > > > complete?
> >> > > >
> >> > > > Thanks,
> >> > > >
> >> > > > Lin
> >> > > >
> >> > > > On Fri, Sep 6, 2019 at 7:35 AM Tao Lv  wrote:
> >> > > >
> >> > > > > Update:
> >> > > > >
> >> > > > > Artifacts of 1.5.1.rc0 have been uploaded to github and Apache
> >> dist.
> >> > > > Before
> >> > > > > voting, we still need some time to build packages for Scala,
> >> Clojure
> >> > > and
> >> > > > R.
> >> > > > >
> >> > > > > Thank you for your patience.
> >> > > > >
> >> > > > > -tao
> >> > > > >
> >> > > > > On Thu, Sep 5, 2019 at 10:15 PM Tao Lv 
> wrote:
> >> > > > >
> >> > > > > >
> >> > > > > > Following the release process [1], I just created the tag for
> >> > > 1.5.1.rc0
> >> > > > > > [2]. Artifacts uploading and validation are still WIP. Will
> keep
> >> > you
> >> > > > > > posted. Hopefully we can start the veto soon for a new
> release.
> >> :)
> >> > > > > >
> >> > > > > > Let me know if you any question or suggestion for the release.
> >> > > > > >
> >> > > > > > Thanks,
> >> > > > > > -tao
> >> > > > > >
> >> > > > > > [1]
> >> > > https://cwiki.apache.org/confluence/display/MXNET/Release+Process
> >> > > > > > [2]
> >> > https://github.com/apache/incubator-mxnet/releases/tag/1.5.1.rc0
> >> > > > > >
> >> > > > > >
> >> > > > > > On Wed, Sep 4, 2019 at 9:23 AM Tao Lv 
> wrote:
> >> > > > > >
> >> > > > > >>
> >> > > > > &

[VOTE] Release Apache MXNet (incubating) 1.5.1.rc0

[Tao Lv]

Dear MXNet community,



This is the 3-day vote to release Apache MXNet (incubating) version 1.5.1.

Voting on dev@ will start September 17, 12:00pm (PST)  and close on
September 20, 12:00pm (PST).



1) Link to release notes:

https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Notes



2) Link to release candidate:

https://github.com/apache/incubator-mxnet/releases/tag/1.5.1.rc0



3) Link to source and signatures on Apache dist server:

https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.5.1.rc0/



Please remember to TEST first before voting accordingly:

+1 = approve

+0 = no opinion

-1 = disapprove (provide reason)



Thanks,

-tao

Re: Code freeze for 1.5.1 patch release

[Tao Lv]

Thanks for your help, Carin. Per step 1.14 of  the release process [1],
stage repo links should be included in the voting email.

Scala packages are done. Thanks to the help from @Lanking.

We still have problem with R package on Windows. @yajiedesign is helping on
that.

Again thanks for all of your support and patience.

-tao

[1] https://cwiki.apache.org/confluence/display/MXNET/Release+Process

On Tue, Sep 17, 2019 at 6:10 PM Carin Meier  wrote:

> I will be able to build the Clojure packages on Friday. I don’t believe
> this needs to hold up the voting. I believe the voting is only on the
> source.
>
> -Carin
>
> On Mon, Sep 16, 2019 at 7:05 PM Lin Yuan  wrote:
>
> > Hi Tao,
> >
> > Thanks for uploading the artifacts. May I know what the current status of
> > Scala, Clojure and R packages and any help you need from the community to
> > complete?
> >
> > Thanks,
> >
> > Lin
> >
> > On Fri, Sep 6, 2019 at 7:35 AM Tao Lv  wrote:
> >
> > > Update:
> > >
> > > Artifacts of 1.5.1.rc0 have been uploaded to github and Apache dist.
> > Before
> > > voting, we still need some time to build packages for Scala, Clojure
> and
> > R.
> > >
> > > Thank you for your patience.
> > >
> > > -tao
> > >
> > > On Thu, Sep 5, 2019 at 10:15 PM Tao Lv  wrote:
> > >
> > > >
> > > > Following the release process [1], I just created the tag for
> 1.5.1.rc0
> > > > [2]. Artifacts uploading and validation are still WIP. Will keep you
> > > > posted. Hopefully we can start the veto soon for a new release. :)
> > > >
> > > > Let me know if you any question or suggestion for the release.
> > > >
> > > > Thanks,
> > > > -tao
> > > >
> > > > [1]
> https://cwiki.apache.org/confluence/display/MXNET/Release+Process
> > > > [2] https://github.com/apache/incubator-mxnet/releases/tag/1.5.1.rc0
> > > >
> > > >
> > > > On Wed, Sep 4, 2019 at 9:23 AM Tao Lv  wrote:
> > > >
> > > >>
> > > >> Code freezing!
> > > >>
> > > >> If you happen to be around github, please help to review the PR [1]
> > for
> > > >> bumping version strings on the release branch. Thanks.
> > > >>
> > > >> I will continue working on the rest steps for the release.
> > > >>
> > > >> Thanks,
> > > >> -tao
> > > >>
> > > >> [1] https://github.com/apache/incubator-mxnet/pull/16072
> > > >>
> > > >> On Mon, Sep 2, 2019 at 9:51 PM Tao Lv  wrote:
> > > >>
> > > >>>
> > > >>> I drafted the release notes for 1.5.1 patch release:
> > > >>>
> > https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Notes
> > > >>>
> > > >>> Any comments or suggestions are highly appreciated!
> > > >>>
> > > >>> -tao
> > > >>>
> > > >>> On Mon, Sep 2, 2019 at 2:00 PM kellen sunderland <
> > > >>> kellen.sunderl...@gmail.com> wrote:
> > > >>>
> > > >>>> Thanks for organizing the release Tao.
> > > >>>>
> > > >>>> On Sun, Sep 1, 2019, 5:53 PM Tao Lv  wrote:
> > > >>>>
> > > >>>> > Hi Community,
> > > >>>> >
> > > >>>> > Code freeze for 1.5.1 patch release will be 9/3 6pm PST (9/4 9am
> > > >>>> CST). If
> > > >>>> > you have any additional fix in progress and would like to
> include
> > it
> > > >>>> in
> > > >>>> > this release, please assure they have been merged before code
> > > freeze.
> > > >>>> >
> > > >>>> > Thanks for all your support and contribution.
> > > >>>> >
> > > >>>> > -tao
> > > >>>> >
> > > >>>>
> > > >>>
> > >
> >
>

Re: Code freeze for 1.5.1 patch release

[Tao Lv]

Update:

Artifacts of 1.5.1.rc0 have been uploaded to github and Apache dist. Before
voting, we still need some time to build packages for Scala, Clojure and R.

Thank you for your patience.

-tao

On Thu, Sep 5, 2019 at 10:15 PM Tao Lv  wrote:

>
> Following the release process [1], I just created the tag for 1.5.1.rc0
> [2]. Artifacts uploading and validation are still WIP. Will keep you
> posted. Hopefully we can start the veto soon for a new release. :)
>
> Let me know if you any question or suggestion for the release.
>
> Thanks,
> -tao
>
> [1] https://cwiki.apache.org/confluence/display/MXNET/Release+Process
> [2] https://github.com/apache/incubator-mxnet/releases/tag/1.5.1.rc0
>
>
> On Wed, Sep 4, 2019 at 9:23 AM Tao Lv  wrote:
>
>>
>> Code freezing!
>>
>> If you happen to be around github, please help to review the PR [1] for
>> bumping version strings on the release branch. Thanks.
>>
>> I will continue working on the rest steps for the release.
>>
>> Thanks,
>> -tao
>>
>> [1] https://github.com/apache/incubator-mxnet/pull/16072
>>
>> On Mon, Sep 2, 2019 at 9:51 PM Tao Lv  wrote:
>>
>>>
>>> I drafted the release notes for 1.5.1 patch release:
>>> https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Notes
>>>
>>> Any comments or suggestions are highly appreciated!
>>>
>>> -tao
>>>
>>> On Mon, Sep 2, 2019 at 2:00 PM kellen sunderland <
>>> kellen.sunderl...@gmail.com> wrote:
>>>
>>>> Thanks for organizing the release Tao.
>>>>
>>>> On Sun, Sep 1, 2019, 5:53 PM Tao Lv  wrote:
>>>>
>>>> > Hi Community,
>>>> >
>>>> > Code freeze for 1.5.1 patch release will be 9/3 6pm PST (9/4 9am
>>>> CST). If
>>>> > you have any additional fix in progress and would like to include it
>>>> in
>>>> > this release, please assure they have been merged before code freeze.
>>>> >
>>>> > Thanks for all your support and contribution.
>>>> >
>>>> > -tao
>>>> >
>>>>
>>>

Re: Code freeze for 1.5.1 patch release

[Tao Lv]

Following the release process [1], I just created the tag for 1.5.1.rc0
[2]. Artifacts uploading and validation are still WIP. Will keep you
posted. Hopefully we can start the veto soon for a new release. :)

Let me know if you any question or suggestion for the release.

Thanks,
-tao

[1] https://cwiki.apache.org/confluence/display/MXNET/Release+Process
[2] https://github.com/apache/incubator-mxnet/releases/tag/1.5.1.rc0


On Wed, Sep 4, 2019 at 9:23 AM Tao Lv  wrote:

>
> Code freezing!
>
> If you happen to be around github, please help to review the PR [1] for
> bumping version strings on the release branch. Thanks.
>
> I will continue working on the rest steps for the release.
>
> Thanks,
> -tao
>
> [1] https://github.com/apache/incubator-mxnet/pull/16072
>
> On Mon, Sep 2, 2019 at 9:51 PM Tao Lv  wrote:
>
>>
>> I drafted the release notes for 1.5.1 patch release:
>> https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Notes
>>
>> Any comments or suggestions are highly appreciated!
>>
>> -tao
>>
>> On Mon, Sep 2, 2019 at 2:00 PM kellen sunderland <
>> kellen.sunderl...@gmail.com> wrote:
>>
>>> Thanks for organizing the release Tao.
>>>
>>> On Sun, Sep 1, 2019, 5:53 PM Tao Lv  wrote:
>>>
>>> > Hi Community,
>>> >
>>> > Code freeze for 1.5.1 patch release will be 9/3 6pm PST (9/4 9am CST).
>>> If
>>> > you have any additional fix in progress and would like to include it in
>>> > this release, please assure they have been merged before code freeze.
>>> >
>>> > Thanks for all your support and contribution.
>>> >
>>> > -tao
>>> >
>>>
>>

Re: Code freeze for 1.5.1 patch release

[Tao Lv]

Code freezing!

If you happen to be around github, please help to review the PR [1] for
bumping version strings on the release branch. Thanks.

I will continue working on the rest steps for the release.

Thanks,
-tao

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

On Mon, Sep 2, 2019 at 9:51 PM Tao Lv  wrote:

>
> I drafted the release notes for 1.5.1 patch release:
> https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Notes
>
> Any comments or suggestions are highly appreciated!
>
> -tao
>
> On Mon, Sep 2, 2019 at 2:00 PM kellen sunderland <
> kellen.sunderl...@gmail.com> wrote:
>
>> Thanks for organizing the release Tao.
>>
>> On Sun, Sep 1, 2019, 5:53 PM Tao Lv  wrote:
>>
>> > Hi Community,
>> >
>> > Code freeze for 1.5.1 patch release will be 9/3 6pm PST (9/4 9am CST).
>> If
>> > you have any additional fix in progress and would like to include it in
>> > this release, please assure they have been merged before code freeze.
>> >
>> > Thanks for all your support and contribution.
>> >
>> > -tao
>> >
>>
>

Re: Code freeze for 1.5.1 patch release

[Tao Lv]

I drafted the release notes for 1.5.1 patch release:
https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Notes

Any comments or suggestions are highly appreciated!

-tao

On Mon, Sep 2, 2019 at 2:00 PM kellen sunderland <
kellen.sunderl...@gmail.com> wrote:

> Thanks for organizing the release Tao.
>
> On Sun, Sep 1, 2019, 5:53 PM Tao Lv  wrote:
>
> > Hi Community,
> >
> > Code freeze for 1.5.1 patch release will be 9/3 6pm PST (9/4 9am CST). If
> > you have any additional fix in progress and would like to include it in
> > this release, please assure they have been merged before code freeze.
> >
> > Thanks for all your support and contribution.
> >
> > -tao
> >
>

Code freeze for 1.5.1 patch release

[Tao Lv]

Hi Community,

Code freeze for 1.5.1 patch release will be 9/3 6pm PST (9/4 9am CST). If
you have any additional fix in progress and would like to include it in
this release, please assure they have been merged before code freeze.

Thanks for all your support and contribution.

-tao

Re: [Discussion] MXNet 1.5.1 release

[Tao Lv]

>
> 5) is not a bug. It's just a large tensor support requirement. The PR was
> to fix a memory alignment issue introduced in master but not in 1.5.1
> (since you did not cherry pick that PR). So, I have crossed out 5) in the
> doc and I don't think we need to mention it in release note.
>

@Lin, I notice there is a revert on the v1.5.x [1]. Was it supposed to fix
the GPU OOM issue on v1.5.x but caused other problems?

What is the current timeline for 1.5.1 release?


Thank you for asking. It's my first time to manage a release so I'm not
sure what's the best pace for a patch release. I saw that it took us about
2.5 months to release 1.4.1 after 1.4.0 was released. I'm wondering if we
need more time to gather enough feedbacks about 1.5.0.

Nevertheless, if there's no other objections and if we can close the last
two opens in time, I think we can freeze the v1.5.x branch early next week
and start the vote subsequently.

Thanks,
-tao

[1]
https://github.com/apache/incubator-mxnet/commit/33f4de13d3909fc356ace8ff7a5c9665a651fc63

On Fri, Aug 30, 2019 at 5:31 PM Tao Lv  wrote:

> Progress since the last update:
> 1. 2 more fixes [1] [2] were picked to v1.5.x;
> 2. 1 cherry pick PR [3] was opened for TensorRT;
> 3. The nightly build issue [4] was removed from the scope of 1.5.1;
> 4. GPU OOM issue [5] was removed from the scope of 1.5.1.
> 5. So far, nightly test shows the release branch is healthy.
>
> Opens:
> 1. [3] is stopped by the CI;
> 2. [6] is proposed but not picked to v1.5.x branch. @Aaron could you
> please update the status?
>
> Please find details on
> https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Plan+and+Status
>
> Thanks,
> -tao
>
> [1] https://github.com/apache/incubator-mxnet/pull/16044
> [2] https://github.com/apache/incubator-mxnet/pull/15803
> [3] https://github.com/apache/incubator-mxnet/pull/16043
> [4]
> https://github.com/apache/incubator-mxnet/issues/15613#issuecomment-516937546
> [5] https://github.com/apache/incubator-mxnet/issues/15703
> [6] https://github.com/apache/incubator-mxnet/pull/15608
>
> On Fri, Aug 30, 2019 at 7:16 AM Lai Wei  wrote:
>
>> Hi Tao,
>>
>> Just checked 1.5.x nightly build is passing, so 10 is not needed. I moved
>> it so 1.6.0 scope.
>>
>> Thanks
>>
>>
>> Best Regards
>>
>> Lai
>>
>>
>> On Thu, Aug 29, 2019 at 8:12 AM Tao Lv  wrote:
>>
>> > @Aaron,
>> > Thank you for looking into these two issues. I have removed the #15609
>> from
>> > the scope of 1.5.1. Please let me know if you have any update about
>> #15608.
>> >
>> > @Lai,
>> > I'm fine with the decision. License issue about MKL-DNN, cub and pybind
>> is
>> > moved to next release.
>> >
>> > @Sam,
>> > I also removed the sidebar issue [3] from the scope of 1.5.1. Besides, I
>> > notice one of your cherry picks is stopped by the CI. Please take a
>> look at
>> > it. Thanks.
>> >
>> > *Nice progress since the last update:*
>> > 1. Per the discussion, we decided to remove #15609, the license issue
>> about
>> > MKL-DNN, cub and pybind, and the sidebar issue [3] from the scope of
>> 1.5.1
>> > patch release;
>> > 2. 3 fixes [4] [5] [6] were merged into the v1.5.x branch.
>> >
>> > *Opens (suggested owners are highlighted):*
>> > 1. @Aaron is working on #15608 to see if we can have it in v1.5.x;
>> > 2. Two cherry pick PRs [7] [8] cannot pass the CI. I have pinged the
>> > authors to take a look at the CI failures.
>> > 3. @Kellen proposed 5 fixes [9] for TensorRT but till now only 3 are
>> picked
>> > to v1.5.x. Please help to confirm if the other 2 are still needed.
>> > 4. Sorry that I missed the proposal for fixing the nightly build [10] in
>> > previous update. @Lai, can you help to confirm if it's still valid?
>> > 5. @Lin please help to make a conclusion for the GPU OOM issue caused by
>> > topk regression [11]. If it cannot be addressed on v1.5.x branch, I will
>> > remove it from the scope of this release and mark it as a known issue in
>> > the release note.
>> >
>> > Please find the details in
>> >
>> >
>> https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Plan+and+Status
>> > .
>> >
>> > Thanks,
>> > -tao
>> >
>> > [1] https://github.com/apache/incubator-mxnet/pull/15609
>> > [2] https://github.com/apache/incubator-mxnet/pull/15608
>> > [3] https://github.com/apache/incubator-mxnet/issues/15200
>> > [4] https://github.com/apache/incub

Re: [Discussion] MXNet 1.5.1 release

[Tao Lv]

Progress since the last update:
1. 2 more fixes [1] [2] were picked to v1.5.x;
2. 1 cherry pick PR [3] was opened for TensorRT;
3. The nightly build issue [4] was removed from the scope of 1.5.1;
4. GPU OOM issue [5] was removed from the scope of 1.5.1.
5. So far, nightly test shows the release branch is healthy.

Opens:
1. [3] is stopped by the CI;
2. [6] is proposed but not picked to v1.5.x branch. @Aaron could you please
update the status?

Please find details on
https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Plan+and+Status

Thanks,
-tao

[1] https://github.com/apache/incubator-mxnet/pull/16044
[2] https://github.com/apache/incubator-mxnet/pull/15803
[3] https://github.com/apache/incubator-mxnet/pull/16043
[4]
https://github.com/apache/incubator-mxnet/issues/15613#issuecomment-516937546
[5] https://github.com/apache/incubator-mxnet/issues/15703
[6] https://github.com/apache/incubator-mxnet/pull/15608

On Fri, Aug 30, 2019 at 7:16 AM Lai Wei  wrote:

> Hi Tao,
>
> Just checked 1.5.x nightly build is passing, so 10 is not needed. I moved
> it so 1.6.0 scope.
>
> Thanks
>
>
> Best Regards
>
> Lai
>
>
> On Thu, Aug 29, 2019 at 8:12 AM Tao Lv  wrote:
>
> > @Aaron,
> > Thank you for looking into these two issues. I have removed the #15609
> from
> > the scope of 1.5.1. Please let me know if you have any update about
> #15608.
> >
> > @Lai,
> > I'm fine with the decision. License issue about MKL-DNN, cub and pybind
> is
> > moved to next release.
> >
> > @Sam,
> > I also removed the sidebar issue [3] from the scope of 1.5.1. Besides, I
> > notice one of your cherry picks is stopped by the CI. Please take a look
> at
> > it. Thanks.
> >
> > *Nice progress since the last update:*
> > 1. Per the discussion, we decided to remove #15609, the license issue
> about
> > MKL-DNN, cub and pybind, and the sidebar issue [3] from the scope of
> 1.5.1
> > patch release;
> > 2. 3 fixes [4] [5] [6] were merged into the v1.5.x branch.
> >
> > *Opens (suggested owners are highlighted):*
> > 1. @Aaron is working on #15608 to see if we can have it in v1.5.x;
> > 2. Two cherry pick PRs [7] [8] cannot pass the CI. I have pinged the
> > authors to take a look at the CI failures.
> > 3. @Kellen proposed 5 fixes [9] for TensorRT but till now only 3 are
> picked
> > to v1.5.x. Please help to confirm if the other 2 are still needed.
> > 4. Sorry that I missed the proposal for fixing the nightly build [10] in
> > previous update. @Lai, can you help to confirm if it's still valid?
> > 5. @Lin please help to make a conclusion for the GPU OOM issue caused by
> > topk regression [11]. If it cannot be addressed on v1.5.x branch, I will
> > remove it from the scope of this release and mark it as a known issue in
> > the release note.
> >
> > Please find the details in
> >
> >
> https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Plan+and+Status
> > .
> >
> > Thanks,
> > -tao
> >
> > [1] https://github.com/apache/incubator-mxnet/pull/15609
> > [2] https://github.com/apache/incubator-mxnet/pull/15608
> > [3] https://github.com/apache/incubator-mxnet/issues/15200
> > [4] https://github.com/apache/incubator-mxnet/pull/16029
> > [5] https://github.com/apache/incubator-mxnet/pull/16026
> > [6] https://github.com/apache/incubator-mxnet/pull/16028
> > [7] https://github.com/apache/incubator-mxnet/pull/15803
> > [8] https://github.com/apache/incubator-mxnet/pull/16027
> > [9]
> >
> >
> https://github.com/apache/incubator-mxnet/issues/15613#issuecomment-520688668
> > [10]
> >
> >
> https://github.com/apache/incubator-mxnet/issues/15613#issuecomment-516937546
> > [11] https://github.com/apache/incubator-mxnet/issues/15703
> >
> >
> >
> > On Thu, Aug 29, 2019 at 1:06 AM Skalicky, Sam  >
> > wrote:
> >
> > > Hi Tao,
> > >
> > > I just talked with Aaron, lets leave the sidebar issue for later.
> > >
> > > I created PRs in the v1.5.x branch to cherry pick the fixes into the
> > 1.5.1
> > > release:
> > > https://github.com/apache/incubator-mxnet/pull/16027
> > > https://github.com/apache/incubator-mxnet/pull/16028
> > >
> > > Thanks for your work on this release!
> > > Sam
> > >
> > > On Aug 28, 2019, at 9:35 AM, Lai Wei  > > roywei...@gmail.com>> wrote:
> > >
> > > Hi,
> > >
> > > Regrading the license issue[1],  we still have item 3, 4, 5 left.
> > > I think it's better to remove them from 1.5.1 release scope 

Re: [Discussion] MXNet 1.5.1 release

[Tao Lv]

@Aaron,
Thank you for looking into these two issues. I have removed the #15609 from
the scope of 1.5.1. Please let me know if you have any update about #15608.

@Lai,
I'm fine with the decision. License issue about MKL-DNN, cub and pybind is
moved to next release.

@Sam,
I also removed the sidebar issue [3] from the scope of 1.5.1. Besides, I
notice one of your cherry picks is stopped by the CI. Please take a look at
it. Thanks.

*Nice progress since the last update:*
1. Per the discussion, we decided to remove #15609, the license issue about
MKL-DNN, cub and pybind, and the sidebar issue [3] from the scope of 1.5.1
patch release;
2. 3 fixes [4] [5] [6] were merged into the v1.5.x branch.

*Opens (suggested owners are highlighted):*
1. @Aaron is working on #15608 to see if we can have it in v1.5.x;
2. Two cherry pick PRs [7] [8] cannot pass the CI. I have pinged the
authors to take a look at the CI failures.
3. @Kellen proposed 5 fixes [9] for TensorRT but till now only 3 are picked
to v1.5.x. Please help to confirm if the other 2 are still needed.
4. Sorry that I missed the proposal for fixing the nightly build [10] in
previous update. @Lai, can you help to confirm if it's still valid?
5. @Lin please help to make a conclusion for the GPU OOM issue caused by
topk regression [11]. If it cannot be addressed on v1.5.x branch, I will
remove it from the scope of this release and mark it as a known issue in
the release note.

Please find the details in
https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Plan+and+Status
.

Thanks,
-tao

[1] https://github.com/apache/incubator-mxnet/pull/15609
[2] https://github.com/apache/incubator-mxnet/pull/15608
[3] https://github.com/apache/incubator-mxnet/issues/15200
[4] https://github.com/apache/incubator-mxnet/pull/16029
[5] https://github.com/apache/incubator-mxnet/pull/16026
[6] https://github.com/apache/incubator-mxnet/pull/16028
[7] https://github.com/apache/incubator-mxnet/pull/15803
[8] https://github.com/apache/incubator-mxnet/pull/16027
[9]
https://github.com/apache/incubator-mxnet/issues/15613#issuecomment-520688668
[10]
https://github.com/apache/incubator-mxnet/issues/15613#issuecomment-516937546
[11] https://github.com/apache/incubator-mxnet/issues/15703



On Thu, Aug 29, 2019 at 1:06 AM Skalicky, Sam 
wrote:

> Hi Tao,
>
> I just talked with Aaron, lets leave the sidebar issue for later.
>
> I created PRs in the v1.5.x branch to cherry pick the fixes into the 1.5.1
> release:
> https://github.com/apache/incubator-mxnet/pull/16027
> https://github.com/apache/incubator-mxnet/pull/16028
>
> Thanks for your work on this release!
> Sam
>
> On Aug 28, 2019, at 9:35 AM, Lai Wei  roywei...@gmail.com>> wrote:
>
> Hi,
>
> Regrading the license issue[1],  we still have item 3, 4, 5 left.
> I think it's better to remove them from 1.5.1 release scope and target for
> 1.6.0 as it need more time and requires changes that should not go into
> patch release.
>
>
> [1] https://github.com/apache/incubator-mxnet/issues/15542
>
> Best Regards
>
> Lai
>
>
> On Wed, Aug 28, 2019 at 9:20 AM Aaron Markham  <mailto:aaron.s.mark...@gmail.com>>
> wrote:
>
> 5 no. Install page defaults to master so you don't need to pick it.
> 6 probably, but there might be other PRs needed. I'd check out the branch
> and attempt the install across platforms to be sure.
>
> On Wed, Aug 28, 2019, 08:55 Tao Lv  ta...@apache.org>> wrote:
>
> Hi Aaron,
>
> They were proposed to be ported to v1.5.x at the beginning of the
> discussion but I didn't see any action for that. So I'm wondering if
> they're still needed. I asked for that in the last update on 8/20 but
> didn't get a response.
>
> If they're still needed, I hope someone who is more familiar with Julia
> frontend can help to cherry pick the commits to the v1.5.x branch.
>
> thanks,
> -tao
>
> On Wed, Aug 28, 2019 at 11:43 PM Aaron Markham <
> aaron.s.mark...@gmail.com<mailto:aaron.s.mark...@gmail.com>>
> wrote:
>
> I don't see any request for action on the Julia PRs: 5 or 6.
> We didn't put the change in right away because we wanted it to not
> break
> anything. But the changes are needed to make Julia setup more seamless.
>
> What "update" is needed?
>
>
> On Wed, Aug 28, 2019, 08:36 Tao Lv  ta...@apache.org>> wrote:
>
> @Pedro, seems the issue is still open on the master branch. Do you
> still
> think we can have your fix on the 1.5.x branch?
>
> Progress since last update:
> 1. We received several more proposals in the github thread [1]. I
> humbly
> ask the reporters to pick the fixes to the v1.5.x. I will keep
> tracking
> the
> progress and the healthy status of the release branch.
> 2. Thanks to @Lai, the licence issue of julia cat image was fixed on
&g

Re: [Discussion] MXNet 1.5.1 release

[Tao Lv]

Hi Aaron,

They were proposed to be ported to v1.5.x at the beginning of the
discussion but I didn't see any action for that. So I'm wondering if
they're still needed. I asked for that in the last update on 8/20 but
didn't get a response.

If they're still needed, I hope someone who is more familiar with Julia
frontend can help to cherry pick the commits to the v1.5.x branch.

thanks,
-tao

On Wed, Aug 28, 2019 at 11:43 PM Aaron Markham 
wrote:

> I don't see any request for action on the Julia PRs: 5 or 6.
> We didn't put the change in right away because we wanted it to not break
> anything. But the changes are needed to make Julia setup more seamless.
>
> What "update" is needed?
>
>
> On Wed, Aug 28, 2019, 08:36 Tao Lv  wrote:
>
> > @Pedro, seems the issue is still open on the master branch. Do you still
> > think we can have your fix on the 1.5.x branch?
> >
> > Progress since last update:
> > 1. We received several more proposals in the github thread [1]. I humbly
> > ask the reporters to pick the fixes to the v1.5.x. I will keep tracking
> the
> > progress and the healthy status of the release branch.
> > 2. Thanks to @Lai, the licence issue of julia cat image was fixed on the
> > master branch and I opened a PR to pick it to v1.5.x [2].
> > 3. The GPU OOM issue was fixed on the master branch by @Lin [3] . But
> there
> > is a problem with porting the fix to v1.5.x branch [4].
> >
> > Opens:
> > 1. https://github.com/apache/incubator-mxnet/pull/15803 still can not
> pass
> > the CI;
> > 2. Call for a update from julia folks about the back porting for [5] and
> > [6]
> > 3. License issue of cub and pybind is still open. @Lai opened a PR [7] to
> > update cub submodule but seems it need more effort than just commit id
> > update. I suspect that we cannot finish this work in 1.5.1 patch release.
> > 4. Still no progress for the sidebar issue on web page [8].
> > 5. Call for a conclusion about fixing the GPU OOM issue in 1.5.1
> >
> > Besides, I would like to ask if there is any preference for the release
> > timeline of 1.5.1 patch release? Please share so I can propose the time
> for
> > code freeze.
> >
> > Thanks,
> > -tao
> >
> > [1]  https://github.com/apache/incubator-mxnet/issues/15613.
> > [2] https://github.com/apache/incubator-mxnet/pull/16026
> > [3] https://github.com/apache/incubator-mxnet/pull/15948
> > [4] https://github.com/apache/incubator-mxnet/pull/15999
> > [5] https://github.com/apache/incubator-mxnet/pull/15609
> > [6]  https://github.com/apache/incubator-mxnet/pull/15608
> > [7] https://github.com/apache/incubator-mxnet/pull/15963
> > [8] https://github.com/apache/incubator-mxnet/issues/15200
> >
> > On Wed, Aug 28, 2019 at 5:50 AM Pedro Larroy <
> pedro.larroy.li...@gmail.com
> > >
> > wrote:
> >
> > > Ok. I was just asking if we want this fix in 1.5.1 since it addresses
> > > crashes using multiprocessing. The problem with cherry picking is that
> > the
> > > patch contains the dynamic load change which shouldn't impact anything
> > else
> > > but is not supposed to go in a release branch.
> > >
> > > On Tue, Aug 27, 2019 at 1:19 PM Lin Yuan  wrote:
> > >
> > > > https://github.com/apache/incubator-mxnet/pull/15762  contains some
> > > > unrelated changes which is being reverted. Please do not cherry pick
> it
> > > > yet.
> > > >
> > > > On Mon, Aug 26, 2019 at 4:25 PM Pedro Larroy <
> > > pedro.larroy.li...@gmail.com
> > > > >
> > > > wrote:
> > > >
> > > > > There's a fix that I did which seems to still produce crashes in
> 1.5
> > > for
> > > > > some users, which I got notice today and is fixed in master.
> > > > >
> > > > > Might be useful to put in 1.5.1:
> > > > > https://github.com/apache/incubator-mxnet/pull/15762   ?
> > > > >
> > > > > Pedro.
> > > > >
> > > > > On Tue, Aug 20, 2019 at 7:49 AM Tao Lv  wrote:
> > > > >
> > > > > > Hi dev,
> > > > > >
> > > > > > Here is an update for the 1.5.1 patch release.
> > > > > >
> > > > > > 1. Thanks for the effort from whole community, we have cherry
> > picked
> > > a
> > > > > > bunch of fixes to v1.5.x branch. So far, the branch looks
> healthy:
> > > > > >
> > > > > >
> > > > >
> > &g

Re: [Discussion] MXNet 1.5.1 release

[Tao Lv]

@Pedro, seems the issue is still open on the master branch. Do you still
think we can have your fix on the 1.5.x branch?

Progress since last update:
1. We received several more proposals in the github thread [1]. I humbly
ask the reporters to pick the fixes to the v1.5.x. I will keep tracking the
progress and the healthy status of the release branch.
2. Thanks to @Lai, the licence issue of julia cat image was fixed on the
master branch and I opened a PR to pick it to v1.5.x [2].
3. The GPU OOM issue was fixed on the master branch by @Lin [3] . But there
is a problem with porting the fix to v1.5.x branch [4].

Opens:
1. https://github.com/apache/incubator-mxnet/pull/15803 still can not pass
the CI;
2. Call for a update from julia folks about the back porting for [5] and [6]
3. License issue of cub and pybind is still open. @Lai opened a PR [7] to
update cub submodule but seems it need more effort than just commit id
update. I suspect that we cannot finish this work in 1.5.1 patch release.
4. Still no progress for the sidebar issue on web page [8].
5. Call for a conclusion about fixing the GPU OOM issue in 1.5.1

Besides, I would like to ask if there is any preference for the release
timeline of 1.5.1 patch release? Please share so I can propose the time for
code freeze.

Thanks,
-tao

[1]  https://github.com/apache/incubator-mxnet/issues/15613.
[2] https://github.com/apache/incubator-mxnet/pull/16026
[3] https://github.com/apache/incubator-mxnet/pull/15948
[4] https://github.com/apache/incubator-mxnet/pull/15999
[5] https://github.com/apache/incubator-mxnet/pull/15609
[6]  https://github.com/apache/incubator-mxnet/pull/15608
[7] https://github.com/apache/incubator-mxnet/pull/15963
[8] https://github.com/apache/incubator-mxnet/issues/15200

On Wed, Aug 28, 2019 at 5:50 AM Pedro Larroy 
wrote:

> Ok. I was just asking if we want this fix in 1.5.1 since it addresses
> crashes using multiprocessing. The problem with cherry picking is that the
> patch contains the dynamic load change which shouldn't impact anything else
> but is not supposed to go in a release branch.
>
> On Tue, Aug 27, 2019 at 1:19 PM Lin Yuan  wrote:
>
> > https://github.com/apache/incubator-mxnet/pull/15762  contains some
> > unrelated changes which is being reverted. Please do not cherry pick it
> > yet.
> >
> > On Mon, Aug 26, 2019 at 4:25 PM Pedro Larroy <
> pedro.larroy.li...@gmail.com
> > >
> > wrote:
> >
> > > There's a fix that I did which seems to still produce crashes in 1.5
> for
> > > some users, which I got notice today and is fixed in master.
> > >
> > > Might be useful to put in 1.5.1:
> > > https://github.com/apache/incubator-mxnet/pull/15762   ?
> > >
> > > Pedro.
> > >
> > > On Tue, Aug 20, 2019 at 7:49 AM Tao Lv  wrote:
> > >
> > > > Hi dev,
> > > >
> > > > Here is an update for the 1.5.1 patch release.
> > > >
> > > > 1. Thanks for the effort from whole community, we have cherry picked
> a
> > > > bunch of fixes to v1.5.x branch. So far, the branch looks healthy:
> > > >
> > > >
> > >
> >
> http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/NightlyTestsForBinaries/activity/
> > > > 2. https://github.com/apache/incubator-mxnet/pull/15803 cannot pass
> > the
> > > > CI;
> > > > 3. I hope julia folks can take a look at the back porting for
> > > > https://github.com/apache/incubator-mxnet/pull/15609 and
> > > > https://github.com/apache/incubator-mxnet/pull/15608 - do we still
> > need
> > > > them?
> > > > 4. License issue of cub and pybind is still not fixed. We also has a
> > > > license issue of a cat image in julia examples.
> > > > https://github.com/apache/incubator-mxnet/issues/15542
> > > > 5. Still no progress for the sidebar issue:
> > > > https://github.com/apache/incubator-mxnet/issues/15200
> > > > 6. There is a GPU OOM issue in 1.5.0 release and already root caused
> by
> > > > Lin:
> > > >
> > > >
> > >
> >
> https://github.com/apache/incubator-mxnet/issues/15703#issuecomment-522780492
> > > > .
> > > > We need decide whether we want to get it fixed in the 1.5.1 patch
> > > release.
> > > >
> > > > Please find details in
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Plan+and+Status
> > > > .
> > > >
> > > > Thanks,
> > > > -tao
> > > >
> > > > On Mon, Aug 12, 2019 at 9:57 PM Zhao, Pat

Re: [Discussion] MXNet 1.5.1 release

[Tao Lv]

Hi dev,

Here is an update for the 1.5.1 patch release.

1. Thanks for the effort from whole community, we have cherry picked a
bunch of fixes to v1.5.x branch. So far, the branch looks healthy:
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/NightlyTestsForBinaries/activity/
2. https://github.com/apache/incubator-mxnet/pull/15803 cannot pass the CI;
3. I hope julia folks can take a look at the back porting for
https://github.com/apache/incubator-mxnet/pull/15609 and
https://github.com/apache/incubator-mxnet/pull/15608 - do we still need
them?
4. License issue of cub and pybind is still not fixed. We also has a
license issue of a cat image in julia examples.
https://github.com/apache/incubator-mxnet/issues/15542
5. Still no progress for the sidebar issue:
https://github.com/apache/incubator-mxnet/issues/15200
6. There is a GPU OOM issue in 1.5.0 release and already root caused by
Lin:
https://github.com/apache/incubator-mxnet/issues/15703#issuecomment-522780492.
We need decide whether we want to get it fixed in the 1.5.1 patch release.

Please find details in
https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Plan+and+Status
.

Thanks,
-tao

On Mon, Aug 12, 2019 at 9:57 PM Zhao, Patric  wrote:

> Thanks for the explanation, Marco & Tao. Sounds great!
>
> > -Original Message-----
> > From: Tao Lv 
> > Sent: Monday, August 12, 2019 9:54 PM
> > To: dev@mxnet.incubator.apache.org
> > Subject: Re: [Discussion] MXNet 1.5.1 release
> >
> > > Regarding the open issue, is there default code owner/maintainer? If
> > > so, he/she will be the right people to look into the issue.
> > > https://github.com/apache/incubator-mxnet/blob/master/CODEOWNERS
> > >
> >
> > I have no idea. But the CODEOWNERS is used to receive change
> notificaitons,
> > not actually indicates the maintainer of a piece of code.
> >
> > Do we have regularly build, run, functionality and performance testing
> for
> > > this release?
> >
> >
> > As Marco mentioned, build, run and functionality of v1.5.x branch are
> tracked
> > automatically by the CI for each cherry pick pull request and the
> nightly tests
> > here:
> > http://jenkins.mxnet-ci.amazon-
> > ml.com/blue/organizations/jenkins/NightlyTestsForBinaries/activity.
> > I see it's healthy so far.
> >
> > For performance, Shufan will track CPU performance with his test suite
> and
> > send out the report once the branch is frozen. I'm not sure if there are
> any
> > other performance tests.
> >
> > On Mon, Aug 12, 2019 at 9:36 PM Marco de Abreu
> > 
> > wrote:
> >
> > > Hi Patric,
> > >
> > > CI should automatically pick up the branch and validate it as usual.
> > >
> > > Best regards,
> > > Marco
> > >
> > > Zhao, Patric  schrieb am Mo., 12. Aug. 2019,
> 15:22:
> > >
> > > > It's great works, Tao 
> > > >
> > > > Regarding the open issue, is there default code owner/maintainer? If
> > > > so, he/she will be the right people to look into the issue.
> > > > https://github.com/apache/incubator-
> > mxnet/blob/master/CODEOWNERS
> > > >
> > > > Do we have regularly build, run, functionality and performance
> > > > testing
> > > for
> > > > this release?
> > > >
> > > > Thanks,
> > > >
> > > > --Patric
> > > >
> > > > > -Original Message-
> > > > > From: Tao Lv 
> > > > > Sent: Monday, August 12, 2019 8:59 PM
> > > > > To: dev@mxnet.incubator.apache.org
> > > > > Subject: Re: [Discussion] MXNet 1.5.1 release
> > > > >
> > > > > Update:
> > > > >
> > > > > We're cherry picking fixes from the master to the v1.5.x branch.
> > > > > Some
> > > of
> > > > > them are already merged. Please find details on the cwiki page:
> > > > > https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Pl
> > > > > an+a
> > > > > nd+Status
> > > > >
> > > > >
> > > > >  There are still 3 opens:
> > > > > 1. Nightly test failure on CI (
> > > > > https://github.com/apache/incubator-mxnet/issues/15374): The issue
> > > > > is
> > > > still
> > > > > open. I'm wondering if it has been fixed or not. If not, is there
> > > anyone
> > > > > working on it?
> > > > > 2. Broken Sidebar on website API for mast

Re: [Discussion] MXNet 1.5.1 release

[Tao Lv]

> Regarding the open issue, is there default code owner/maintainer? If so,
> he/she will be the right people to look into the issue.
> https://github.com/apache/incubator-mxnet/blob/master/CODEOWNERS
>

I have no idea. But the CODEOWNERS is used to receive change notificaitons,
not actually indicates the maintainer of a piece of code.

Do we have regularly build, run, functionality and performance testing for
> this release?


As Marco mentioned, build, run and functionality of v1.5.x branch are
tracked automatically by the CI for each cherry pick pull request and the
nightly tests here:
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/NightlyTestsForBinaries/activity.
I see it's healthy so far.

For performance, Shufan will track CPU performance with his test suite and
send out the report once the branch is frozen. I'm not sure if there are
any other performance tests.

On Mon, Aug 12, 2019 at 9:36 PM Marco de Abreu 
wrote:

> Hi Patric,
>
> CI should automatically pick up the branch and validate it as usual.
>
> Best regards,
> Marco
>
> Zhao, Patric  schrieb am Mo., 12. Aug. 2019, 15:22:
>
> > It's great works, Tao 
> >
> > Regarding the open issue, is there default code owner/maintainer? If so,
> > he/she will be the right people to look into the issue.
> > https://github.com/apache/incubator-mxnet/blob/master/CODEOWNERS
> >
> > Do we have regularly build, run, functionality and performance testing
> for
> > this release?
> >
> > Thanks,
> >
> > --Patric
> >
> > > -Original Message-
> > > From: Tao Lv 
> > > Sent: Monday, August 12, 2019 8:59 PM
> > > To: dev@mxnet.incubator.apache.org
> > > Subject: Re: [Discussion] MXNet 1.5.1 release
> > >
> > > Update:
> > >
> > > We're cherry picking fixes from the master to the v1.5.x branch. Some
> of
> > > them are already merged. Please find details on the cwiki page:
> > > https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Plan+a
> > > nd+Status
> > >
> > >
> > >  There are still 3 opens:
> > > 1. Nightly test failure on CI (
> > > https://github.com/apache/incubator-mxnet/issues/15374): The issue is
> > still
> > > open. I'm wondering if it has been fixed or not. If not, is there
> anyone
> > > working on it?
> > > 2. Broken Sidebar on website API for master and 1.5.0 (
> > > https://github.com/apache/incubator-mxnet/issues/15200): I don't see
> any
> > > progress on this issue? Do we still want to include it into 1.5.1 patch
> > release?
> > > 3. License issues need to be fixed before 1.6 release (
> > > https://github.com/apache/incubator-mxnet/issues/15542): Currently the
> > > license issue for code and images is partially fixed on the master
> > branch and
> > > will be picked to v1.5.x soon. MKLML license issue is pushed out to 1.6
> > > release. But license issue for cub and pybind is still open.
> > >
> > > Let me know if you any suggestion. Thanks for your support!
> > >
> > > -tao
> > >
> > >
> > > On Wed, Aug 7, 2019 at 11:03 PM Tao Lv  wrote:
> > >
> > > >
> > > > Update:
> > > >
> > > > Thanks to wkcn's report, Issue #15774 [1] and the fix #15751 [2] are
> > > > added to the scope of 1.5.1 patch release.
> > > > For issue #15703 [3], I'm still waiting from the response from the
> > > > reporter.
> > > > Issue #15431 [4] was closed as false positive report.
> > > > I also included several MKL-DNN backend issues reported by mxnet
> users
> > > > and downstream projects. They are already fixed on the master branch.
> > > >
> > > > Please kindly check the full list of issues need be included in the
> > > > 1.5.1 patch release:
> > > >
> > > https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Plan+a
> > > > nd+Status
> > > >
> > > > For issues which are already fixed on the master branch, we will
> start
> > > > to cherry pick the fix commit to the v1.5.x branch. For issues which
> > > > are still open, we will start to track the fix process.
> > > >
> > > > Thanks for your great support. Let me know if you have any questions
> > > > or concerns.
> > > >
> > > > -tao
> > > >
> > > > [1] https://github.com/apache/incubator-mxnet/issues/15774
> > > > [2] https://github.com/apache/incubator-mxnet/pull/1575

Re: [Discussion] MXNet 1.5.1 release

[Tao Lv]

Update:

We're cherry picking fixes from the master to the v1.5.x branch. Some of
them are already merged. Please find details on the cwiki page:
https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Plan+and+Status


 There are still 3 opens:
1. Nightly test failure on CI (
https://github.com/apache/incubator-mxnet/issues/15374): The issue is still
open. I'm wondering if it has been fixed or not. If not, is there anyone
working on it?
2. Broken Sidebar on website API for master and 1.5.0 (
https://github.com/apache/incubator-mxnet/issues/15200): I don't see any
progress on this issue? Do we still want to include it into 1.5.1 patch
release?
3. License issues need to be fixed before 1.6 release (
https://github.com/apache/incubator-mxnet/issues/15542): Currently the
license issue for code and images is partially fixed on the master branch
and will be picked to v1.5.x soon. MKLML license issue is pushed out to 1.6
release. But license issue for cub and pybind is still open.

Let me know if you any suggestion. Thanks for your support!

-tao


On Wed, Aug 7, 2019 at 11:03 PM Tao Lv  wrote:

>
> Update:
>
> Thanks to wkcn's report, Issue #15774 [1] and the fix #15751 [2] are added
> to the scope of 1.5.1 patch release.
> For issue #15703 [3], I'm still waiting from the response from the
> reporter.
> Issue #15431 [4] was closed as false positive report.
> I also included several MKL-DNN backend issues reported by mxnet users and
> downstream projects. They are already fixed on the master branch.
>
> Please kindly check the full list of issues need be included in the 1.5.1
> patch release:
> https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Plan+and+Status
>
> For issues which are already fixed on the master branch, we will start to
> cherry pick the fix commit to the v1.5.x branch. For issues which are still
> open, we will start to track the fix process.
>
> Thanks for your great support. Let me know if you have any questions or
> concerns.
>
> -tao
>
> [1] https://github.com/apache/incubator-mxnet/issues/15774
> [2] https://github.com/apache/incubator-mxnet/pull/15751
> [3] https://github.com/apache/incubator-mxnet/issues/15703
> [4] https://github.com/apache/incubator-mxnet/issues/15431
>
>
> On Tue, Aug 6, 2019 at 2:04 PM Tao Lv  wrote:
>
>>
>> Per Sam's proposal [1], Issue #15737 [2] and the fix [3] are added to the
>> scope of 1.5.1 patch release.
>>
>> A friendly reminder: the issue proposing will be closed before 11pm 8/7
>> CST (8am 8/7 PST). After that, we will start to cherry pick fixes to the
>> v1.5.x branch.
>>
>>
>> [1]
>> https://github.com/apache/incubator-mxnet/issues/15613#issuecomment-518430120
>> [2] https://github.com/apache/incubator-mxnet/issues/15737
>> [3] https://github.com/apache/incubator-mxnet/pull/15692
>>
>> On Thu, Aug 1, 2019 at 4:24 PM Tao Lv  wrote:
>>
>>> Hi Sandeep/Lai,
>>>
>>> Thank you for the prompt response!
>>>
>>> https://github.com/apache/incubator-mxnet/issues/15200  is added to the
>>> list to track the sidebar issue.
>>>
>>> On Thu, Aug 1, 2019 at 7:54 AM sandeep krishnamurthy <
>>> sandeep.krishn...@gmail.com> wrote:
>>>
>>>> Thank you Tao and Shufan.
>>>> Sidebar missing bug in API documentation is inconvenience for the user.
>>>> It
>>>> would great if we can fix it with 1.5.1
>>>>
>>>> On Wed, Jul 31, 2019, 10:14 AM Lai Wei  wrote:
>>>>
>>>> > Hi Tao,
>>>> >
>>>> > Thank you so much for driving it.  Currently nightly test on
>>>> tutorials are
>>>> > failing and it need to be fixed. [3]
>>>> > I have updated the issue[1] and cwiki.[2]
>>>> >
>>>> > [1] https://github.com/apache/incubator-mxnet/issues/15613
>>>> > [2]
>>>> >
>>>> >
>>>> https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Plan+and+Status
>>>> > [3] https://github.com/apache/incubator-mxnet/issues/15374
>>>> >
>>>> > Best Regards
>>>> >
>>>> > Lai
>>>> >
>>>> >
>>>> > On Wed, Jul 31, 2019 at 8:04 AM Tao Lv  wrote:
>>>> >
>>>> > >  Hi community,
>>>> > >
>>>> > >
>>>> > >
>>>> > > Thanks for the initiative from Sam (samskalicky@github), we already
>>>> > have a
>>>> > > discussion thread [1] on github about the defects and bugs exposed
>>>> in the
>

Re: [Discussion] MXNet 1.5.1 release

[Tao Lv]

Per Sam's proposal [1], Issue #15737 [2] and the fix [3] are added to the
scope of 1.5.1 patch release.

A friendly reminder: the issue proposing will be closed before 11pm 8/7 CST
(8am 8/7 PST). After that, we will start to cherry pick fixes to the v1.5.x
branch.


[1]
https://github.com/apache/incubator-mxnet/issues/15613#issuecomment-518430120
[2] https://github.com/apache/incubator-mxnet/issues/15737
[3] https://github.com/apache/incubator-mxnet/pull/15692

On Thu, Aug 1, 2019 at 4:24 PM Tao Lv  wrote:

> Hi Sandeep/Lai,
>
> Thank you for the prompt response!
>
> https://github.com/apache/incubator-mxnet/issues/15200  is added to the
> list to track the sidebar issue.
>
> On Thu, Aug 1, 2019 at 7:54 AM sandeep krishnamurthy <
> sandeep.krishn...@gmail.com> wrote:
>
>> Thank you Tao and Shufan.
>> Sidebar missing bug in API documentation is inconvenience for the user. It
>> would great if we can fix it with 1.5.1
>>
>> On Wed, Jul 31, 2019, 10:14 AM Lai Wei  wrote:
>>
>> > Hi Tao,
>> >
>> > Thank you so much for driving it.  Currently nightly test on tutorials
>> are
>> > failing and it need to be fixed. [3]
>> > I have updated the issue[1] and cwiki.[2]
>> >
>> > [1] https://github.com/apache/incubator-mxnet/issues/15613
>> > [2]
>> >
>> >
>> https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Plan+and+Status
>> > [3] https://github.com/apache/incubator-mxnet/issues/15374
>> >
>> > Best Regards
>> >
>> > Lai
>> >
>> >
>> > On Wed, Jul 31, 2019 at 8:04 AM Tao Lv  wrote:
>> >
>> > >  Hi community,
>> > >
>> > >
>> > >
>> > > Thanks for the initiative from Sam (samskalicky@github), we already
>> > have a
>> > > discussion thread [1] on github about the defects and bugs exposed in
>> the
>> > > 1.5.0 release.
>> > >
>> > > Shufan (juliusshufan@github) and I (TaoLv@github) would like to
>> manage
>> > the
>> > > release of 1.5.1. This will be our first debut on the release process,
>> > your
>> > > comments are always valuable.
>> > >
>> > >
>> > >
>> > > Per the SemVer 2.0 [2], MXNet 1.5.1 will be a patch release which
>> > contains
>> > > backwards-compatible fixes only.
>> > >
>> > > I have created a page on cwiki [3] to track the release process and
>> moved
>> > > the issues and PRs mentioned in the github discussion thread to the
>> page.
>> > >
>> > >
>> > >
>> > > Here I would like to ask the community to:
>> > >
>> > > (1) Raise any other defect or regression you identified in the 1.5.0
>> > > release. Please file a github issue for it and note the issue number
>> in
>> > > this thread;
>> > >
>> > > (2) Please comment with one sentence for why you think the issue is
>> > > critical and must have in the 1.5.1 release;
>> > >
>> > > (3) If the issue is already fixed on master branch or already have a
>> PR
>> > > WIP, please also note the fix commit id or PR number;
>> > >
>> > > (4) If the issue is still open and there is no PR WIP, please indicate
>> > > whether you'd be willing to help it out;
>> > >
>> > > (5) Feel free to comment if any other suggestion for the release.
>> > >
>> > >
>> > >
>> > > I suggest to keep this thread open for one week to collect enough
>> > > information and proposals before we decide the timeline for the
>> release.
>> > So
>> > > your timely response will be highly appreciated!
>> > >
>> > >
>> > >
>> > > PS: Sorry to say that even as a committer, this is the first time for
>> me
>> > to
>> > > manage a release. So it would be great if an experienced committer can
>> > help
>> > > to guide the process.
>> > >
>> > >
>> > >
>> > > -tao
>> > >
>> > >
>> > >
>> > > [1] https://github.com/apache/incubator-mxnet/issues/15613
>> > >
>> > > [2] https://semver.org/
>> > >
>> > > [3]
>> > >
>> > >
>> >
>> https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Plan+and+Status
>> > >
>> >
>>
>

Re: [Discussion] MXNet 1.5.1 release

[Tao Lv]

Hi Sandeep/Lai,

Thank you for the prompt response!

https://github.com/apache/incubator-mxnet/issues/15200  is added to the
list to track the sidebar issue.

On Thu, Aug 1, 2019 at 7:54 AM sandeep krishnamurthy <
sandeep.krishn...@gmail.com> wrote:

> Thank you Tao and Shufan.
> Sidebar missing bug in API documentation is inconvenience for the user. It
> would great if we can fix it with 1.5.1
>
> On Wed, Jul 31, 2019, 10:14 AM Lai Wei  wrote:
>
> > Hi Tao,
> >
> > Thank you so much for driving it.  Currently nightly test on tutorials
> are
> > failing and it need to be fixed. [3]
> > I have updated the issue[1] and cwiki.[2]
> >
> > [1] https://github.com/apache/incubator-mxnet/issues/15613
> > [2]
> >
> >
> https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Plan+and+Status
> > [3] https://github.com/apache/incubator-mxnet/issues/15374
> >
> > Best Regards
> >
> > Lai
> >
> >
> > On Wed, Jul 31, 2019 at 8:04 AM Tao Lv  wrote:
> >
> > >  Hi community,
> > >
> > >
> > >
> > > Thanks for the initiative from Sam (samskalicky@github), we already
> > have a
> > > discussion thread [1] on github about the defects and bugs exposed in
> the
> > > 1.5.0 release.
> > >
> > > Shufan (juliusshufan@github) and I (TaoLv@github) would like to manage
> > the
> > > release of 1.5.1. This will be our first debut on the release process,
> > your
> > > comments are always valuable.
> > >
> > >
> > >
> > > Per the SemVer 2.0 [2], MXNet 1.5.1 will be a patch release which
> > contains
> > > backwards-compatible fixes only.
> > >
> > > I have created a page on cwiki [3] to track the release process and
> moved
> > > the issues and PRs mentioned in the github discussion thread to the
> page.
> > >
> > >
> > >
> > > Here I would like to ask the community to:
> > >
> > > (1) Raise any other defect or regression you identified in the 1.5.0
> > > release. Please file a github issue for it and note the issue number in
> > > this thread;
> > >
> > > (2) Please comment with one sentence for why you think the issue is
> > > critical and must have in the 1.5.1 release;
> > >
> > > (3) If the issue is already fixed on master branch or already have a PR
> > > WIP, please also note the fix commit id or PR number;
> > >
> > > (4) If the issue is still open and there is no PR WIP, please indicate
> > > whether you'd be willing to help it out;
> > >
> > > (5) Feel free to comment if any other suggestion for the release.
> > >
> > >
> > >
> > > I suggest to keep this thread open for one week to collect enough
> > > information and proposals before we decide the timeline for the
> release.
> > So
> > > your timely response will be highly appreciated!
> > >
> > >
> > >
> > > PS: Sorry to say that even as a committer, this is the first time for
> me
> > to
> > > manage a release. So it would be great if an experienced committer can
> > help
> > > to guide the process.
> > >
> > >
> > >
> > > -tao
> > >
> > >
> > >
> > > [1] https://github.com/apache/incubator-mxnet/issues/15613
> > >
> > > [2] https://semver.org/
> > >
> > > [3]
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Plan+and+Status
> > >
> >
>

[Discussion] MXNet 1.5.1 release

[Tao Lv]

 Hi community,



Thanks for the initiative from Sam (samskalicky@github), we already have a
discussion thread [1] on github about the defects and bugs exposed in the
1.5.0 release.

Shufan (juliusshufan@github) and I (TaoLv@github) would like to manage the
release of 1.5.1. This will be our first debut on the release process, your
comments are always valuable.



Per the SemVer 2.0 [2], MXNet 1.5.1 will be a patch release which contains
backwards-compatible fixes only.

I have created a page on cwiki [3] to track the release process and moved
the issues and PRs mentioned in the github discussion thread to the page.



Here I would like to ask the community to:

(1) Raise any other defect or regression you identified in the 1.5.0
release. Please file a github issue for it and note the issue number in
this thread;

(2) Please comment with one sentence for why you think the issue is
critical and must have in the 1.5.1 release;

(3) If the issue is already fixed on master branch or already have a PR
WIP, please also note the fix commit id or PR number;

(4) If the issue is still open and there is no PR WIP, please indicate
whether you'd be willing to help it out;

(5) Feel free to comment if any other suggestion for the release.



I suggest to keep this thread open for one week to collect enough
information and proposals before we decide the timeline for the release. So
your timely response will be highly appreciated!



PS: Sorry to say that even as a committer, this is the first time for me to
manage a release. So it would be great if an experienced committer can help
to guide the process.



-tao



[1] https://github.com/apache/incubator-mxnet/issues/15613

[2] https://semver.org/

[3]
https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Plan+and+Status

Re: Join the MXNet slack channel

[Tao Lv]

Hi Yan Zhe,

Invite is sent. You can find the `mxnet` channel in the ASF workspace.

-tao

On Fri, May 31, 2019 at 3:15 PM 严哲  wrote:

> Dear MXNet community，
>
>
>
>
> I want to join the MXNet slack channel,  can you allow me to join it ?
>
>
>
>
>
> Thanks & Best Regards,
>
> Yan Zhe

Re: apply for slack channel

[Tao Lv]

Hi Shuchun,

Welcome to the MXNet community!

Invite is sent. You will be added to the 'general' channel of ASF and you
can search for the 'mxnet' channel.

-tao

On Sun, May 5, 2019 at 5:38 PM shuchun liu  wrote:

> thanks.
>
> --
> --
> --
> Best Regards,
> Liu Shuchun techgo.io
> Address: 上海市浦东新区张江金科路2889弄长泰广场A座
> Tel: +86 13524123160
>