Re: new website, docs code freeze

[Thomas DELTEIL]

Thanks all for the feedback,

We'll send an email next week with the list of missing features, content
and bugs that we plan to fix.
We took the option of releasing early, with some features missing, rather
than trying to be at feature parity with the old website before launching
the website.
The reason why we decided to do that is two-fold:
- playing catch-up with docs in master introduce daily conflicts that need
to be resolved and introduce opportunity for errors
- by releasing early, we can take advantage of the community contributions
in modifying whatever the community feels like a better way of doing things.

One of the goals of the new website was to disentangle the main website,
now called "static_site" to the auto-generated docs. Now the overall site
is made of a main static site, with easy to modify content and easy to
understand architecture for anybody familiar with basic html, and a
collection of mini-websites for each language bindings that can be built in
isolation and that are self-contained. Actually the new CI jobs builds all
of them in parallel independently.

There is PLENTY of room for improvement, it would be great if the community
can help contribute to bring the new website at the same level of content
richness as the old one, and then even further.

Missing features:
- As pointed by Haibin, the API docs do not have the full list of operators
and classes. There is a mix of auto-generated docs based on packages, and
some docs that are spelled out manually to improve the logical organization
of the package where there is a need. The drawback with manually listed
classes in a package is that it's very easy to miss some. If someone wanted
to build a sanity check that would automatically detect which classes are
not in the documentation, or if someone knew how to enable that with
sphinx, that would be a great addition to the python docs
- There is missing content in the python tutorials, and the discoverability
could be improved. Some old tutorials have not been migrated just yet.
- The nightly tests on tutorials have been disabled for now
- There is no "Download jupyter notebook" for tutorials just yet.
- Non-python tutorials might benefit from a blurb description and a better
content organization.
- Python tutorials could be better organized, have a picture accompanying
their description
- There is no site-wide search, this is not an easy problem to solve to be
fair given the static nature of the website, but maybe an external plugin
might be able to give a half-way solution
- There is no version selector for the docs
- There is bug in search box of the python docs, but this is just a small
JS bug that can be fixed easily (on my list for next week)
- Most old links have not had a redirect put in place.

We'll formalize this in github issues next week, but they are all fairly
small and helping out on these would be a great way of familiarizing
yourself with the new website build system and website architecture.

 Thanks all for the feedback, please keep it coming!

Thomas Delteil

Le sam. 21 sept. 2019 à 09:53, Haibin Lin  a
écrit :

> It looks like my previous email did not go through. Re-sending:
>
> Hi Aaron,
>
> The website looks cool. Thanks for pushing this to production. A few
> questions:
>
> - I was looking for the API doc for mx.sym.dot, but I find that most
> operators under mx.sym.* are missing. Is this expected?
> - I was also checking the search functionality, searching the keyword
> "ndarray" only returns one result "mxnet.ndarray.NDArray", which doesn't
> seem right. There animation keeps going (Searching. -> Searching.. ->
> Searching ...) and gives me an impression that the search is never
> completely done(?).
>
> Best,
> Haibin
>
>
> On Fri, Sep 20, 2019 at 4:50 PM Chaitanya Bapat 
> wrote:
>
> > Thanks Aaron and the team for launching new website!
> >
> > 1. There's no search button anywhere on the landing page.
> > 2. I wasn't able to find FAQ (and without search button I dont have
> option
> > but to go manually on each menu). Only when I go to Docs -> FAQ
> > -> Extend and Cotribute (that I got what I wanted).
> >
> > Suggestions
> > Might want to make this searchable and pop FAQ on the main page (or
> > somewhere prominent)
> >
> > Thanks,
> > Chai
> >
> >
> > On Fri, 20 Sep 2019 at 14:58, Przemysław Trędak 
> > wrote:
> >
> > > There seems to be a problem with (at least Python, did not check
> others)
> > > APIs. For example this page:
> > >
> > >
> >
> https://mxnet.incubator.apache.org/api/python/docs/api/symbol/_autogen/mxnet.symbol.Symbol.argmax.html
> > >
> > > says that it is a convenience method for argmax (with a link), but
> > > clicking that link just points to the same website (and so user has no
> > way
> > > of getting to the docs of the actual operator).
> > >
> > > When I tried to manually remove Symbol from the URL to get to
> > > mxnet.symbol.argmax.html, I got a "Not found" webpage which I guess
> also
> > > should not happen (ignoring the 

Re: new website, docs code freeze

[Haibin Lin]

It looks like my previous email did not go through. Re-sending:

Hi Aaron,

The website looks cool. Thanks for pushing this to production. A few
questions:

- I was looking for the API doc for mx.sym.dot, but I find that most
operators under mx.sym.* are missing. Is this expected?
- I was also checking the search functionality, searching the keyword
"ndarray" only returns one result "mxnet.ndarray.NDArray", which doesn't
seem right. There animation keeps going (Searching. -> Searching.. ->
Searching ...) and gives me an impression that the search is never
completely done(?).

Best,
Haibin


On Fri, Sep 20, 2019 at 4:50 PM Chaitanya Bapat 
wrote:

> Thanks Aaron and the team for launching new website!
>
> 1. There's no search button anywhere on the landing page.
> 2. I wasn't able to find FAQ (and without search button I dont have option
> but to go manually on each menu). Only when I go to Docs -> FAQ
> -> Extend and Cotribute (that I got what I wanted).
>
> Suggestions
> Might want to make this searchable and pop FAQ on the main page (or
> somewhere prominent)
>
> Thanks,
> Chai
>
>
> On Fri, 20 Sep 2019 at 14:58, Przemysław Trędak 
> wrote:
>
> > There seems to be a problem with (at least Python, did not check others)
> > APIs. For example this page:
> >
> >
> https://mxnet.incubator.apache.org/api/python/docs/api/symbol/_autogen/mxnet.symbol.Symbol.argmax.html
> >
> > says that it is a convenience method for argmax (with a link), but
> > clicking that link just points to the same website (and so user has no
> way
> > of getting to the docs of the actual operator).
> >
> > When I tried to manually remove Symbol from the URL to get to
> > mxnet.symbol.argmax.html, I got a "Not found" webpage which I guess also
> > should not happen (ignoring the fact that this should exist, going to
> > random URL under the website should redirect to the main page I think).
> >
> > Przemek
> >
> > On 2019/09/20 16:41:28, Lin Yuan  wrote:
> > > Looks very neat. Thank you Aaron and many others for launching this!
> > >
> > > On Fri, Sep 20, 2019 at 7:31 AM Carin Meier 
> > wrote:
> > >
> > > > Nice!!! Congrats everyone!
> > > >
> > > > On Fri, Sep 20, 2019 at 10:28 AM Aaron Markham <
> > aaron.s.mark...@gmail.com>
> > > > wrote:
> > > >
> > > > > Alrighty! The new site is launched. You might need to clear your
> > cache.
> > > > >
> > > > > Cheers,
> > > > > Aaron
> > > > >
> > > > > On Thu, Sep 19, 2019 at 3:33 PM Aaron Markham <
> > aaron.s.mark...@gmail.com
> > > > >
> > > > > wrote:
> > > > > >
> > > > > > Thanks everyone. The PRs passed CI, but please continue holding
> > off on
> > > > > > docs and CI edits. Unless there are any objections, I'd like to
> > launch
> > > > > > the new website today.
> > > > > >
> > > > > > On Wed, Sep 18, 2019 at 7:46 AM Aaron Markham <
> > > > aaron.s.mark...@gmail.com>
> > > > > wrote:
> > > > > > >
> > > > > > > Hi everyone,
> > > > > > > The last two PRs [1][2] for the new website and docs have
> passed
> > CI
> > > > > > > (finally). Please do not make changes to /docs or /ci until we
> > get
> > > > > > > these approved and merged. Every time there's a merge conflict
> > it has
> > > > > > > set us back a day or two while shepherding the PRs through CI
> > again.
> > > > > > > Unless there are catastrophic issues discovered in a review, I
> > > > > > > recommend that we hold any patches or updates to the PRs to
> > follow-up
> > > > > > > PRs.
> > > > > > >
> > > > > > > There are four steps to launch:
> > > > > > > 1. Once the PRs are approved, the plan is to merge 15885 to
> > delete
> > > > the
> > > > > > > old content first.
> > > > > > > 2. Then immediately merge 15883 to add in the new CI flows and
> > > > updates
> > > > > > > to the content Thomas and I have already had merged in 15884
> [3].
> > > > > > > 3. I will change the website validation Jenkins pipeline to
> > point to
> > > > > > > the new pipeline.
> > > > > > > 4. I will change the website publishing Jenkins pipeline to
> > point to
> > > > > > > its new pipeline as well. Once triggered, the old site will be
> > > > > > > replaced with the new one.
> > > > > > >
> > > > > > > Post launch we'll need to update the DNS for beta.mxnet.io to
> > point
> > > > to
> > > > > > > production, and there will likely be some redirect/.htaccess
> > updates
> > > > > > > needed next week to assist with any deep linking and 404 issues
> > that
> > > > > > > pop up.
> > > > > > >
> > > > > > > Cheers,
> > > > > > > Aaron
> > > > > > >
> > > > > > > [1] https://github.com/apache/incubator-mxnet/pull/15885
> > > > > > > [2] https://github.com/apache/incubator-mxnet/pull/15883
> > > > > > > [3] https://github.com/apache/incubator-mxnet/pull/15884
> > > > >
> > > >
> > >
> >
>
>
> --
> *Chaitanya Prakash Bapat*
> *+1 (973) 953-6299*
>
> [image: https://www.linkedin.com//in/chaibapat25]
> [image: https://www.facebook.com/chaibapat
> ]
> [image:
> 

Re: new website, docs code freeze

[Chaitanya Bapat]

Thanks Aaron and the team for launching new website!

1. There's no search button anywhere on the landing page.
2. I wasn't able to find FAQ (and without search button I dont have option
but to go manually on each menu). Only when I go to Docs -> FAQ
-> Extend and Cotribute (that I got what I wanted).

Suggestions
Might want to make this searchable and pop FAQ on the main page (or
somewhere prominent)

Thanks,
Chai


On Fri, 20 Sep 2019 at 14:58, Przemysław Trędak  wrote:

> There seems to be a problem with (at least Python, did not check others)
> APIs. For example this page:
>
> https://mxnet.incubator.apache.org/api/python/docs/api/symbol/_autogen/mxnet.symbol.Symbol.argmax.html
>
> says that it is a convenience method for argmax (with a link), but
> clicking that link just points to the same website (and so user has no way
> of getting to the docs of the actual operator).
>
> When I tried to manually remove Symbol from the URL to get to
> mxnet.symbol.argmax.html, I got a "Not found" webpage which I guess also
> should not happen (ignoring the fact that this should exist, going to
> random URL under the website should redirect to the main page I think).
>
> Przemek
>
> On 2019/09/20 16:41:28, Lin Yuan  wrote:
> > Looks very neat. Thank you Aaron and many others for launching this!
> >
> > On Fri, Sep 20, 2019 at 7:31 AM Carin Meier 
> wrote:
> >
> > > Nice!!! Congrats everyone!
> > >
> > > On Fri, Sep 20, 2019 at 10:28 AM Aaron Markham <
> aaron.s.mark...@gmail.com>
> > > wrote:
> > >
> > > > Alrighty! The new site is launched. You might need to clear your
> cache.
> > > >
> > > > Cheers,
> > > > Aaron
> > > >
> > > > On Thu, Sep 19, 2019 at 3:33 PM Aaron Markham <
> aaron.s.mark...@gmail.com
> > > >
> > > > wrote:
> > > > >
> > > > > Thanks everyone. The PRs passed CI, but please continue holding
> off on
> > > > > docs and CI edits. Unless there are any objections, I'd like to
> launch
> > > > > the new website today.
> > > > >
> > > > > On Wed, Sep 18, 2019 at 7:46 AM Aaron Markham <
> > > aaron.s.mark...@gmail.com>
> > > > wrote:
> > > > > >
> > > > > > Hi everyone,
> > > > > > The last two PRs [1][2] for the new website and docs have passed
> CI
> > > > > > (finally). Please do not make changes to /docs or /ci until we
> get
> > > > > > these approved and merged. Every time there's a merge conflict
> it has
> > > > > > set us back a day or two while shepherding the PRs through CI
> again.
> > > > > > Unless there are catastrophic issues discovered in a review, I
> > > > > > recommend that we hold any patches or updates to the PRs to
> follow-up
> > > > > > PRs.
> > > > > >
> > > > > > There are four steps to launch:
> > > > > > 1. Once the PRs are approved, the plan is to merge 15885 to
> delete
> > > the
> > > > > > old content first.
> > > > > > 2. Then immediately merge 15883 to add in the new CI flows and
> > > updates
> > > > > > to the content Thomas and I have already had merged in 15884 [3].
> > > > > > 3. I will change the website validation Jenkins pipeline to
> point to
> > > > > > the new pipeline.
> > > > > > 4. I will change the website publishing Jenkins pipeline to
> point to
> > > > > > its new pipeline as well. Once triggered, the old site will be
> > > > > > replaced with the new one.
> > > > > >
> > > > > > Post launch we'll need to update the DNS for beta.mxnet.io to
> point
> > > to
> > > > > > production, and there will likely be some redirect/.htaccess
> updates
> > > > > > needed next week to assist with any deep linking and 404 issues
> that
> > > > > > pop up.
> > > > > >
> > > > > > Cheers,
> > > > > > Aaron
> > > > > >
> > > > > > [1] https://github.com/apache/incubator-mxnet/pull/15885
> > > > > > [2] https://github.com/apache/incubator-mxnet/pull/15883
> > > > > > [3] https://github.com/apache/incubator-mxnet/pull/15884
> > > >
> > >
> >
>


-- 
*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: new website, docs code freeze

[Przemysław Trędak]

There seems to be a problem with (at least Python, did not check others) APIs. 
For example this page:
https://mxnet.incubator.apache.org/api/python/docs/api/symbol/_autogen/mxnet.symbol.Symbol.argmax.html

says that it is a convenience method for argmax (with a link), but clicking 
that link just points to the same website (and so user has no way of getting to 
the docs of the actual operator).

When I tried to manually remove Symbol from the URL to get to 
mxnet.symbol.argmax.html, I got a "Not found" webpage which I guess also should 
not happen (ignoring the fact that this should exist, going to random URL under 
the website should redirect to the main page I think).

Przemek

On 2019/09/20 16:41:28, Lin Yuan  wrote: 
> Looks very neat. Thank you Aaron and many others for launching this!
> 
> On Fri, Sep 20, 2019 at 7:31 AM Carin Meier  wrote:
> 
> > Nice!!! Congrats everyone!
> >
> > On Fri, Sep 20, 2019 at 10:28 AM Aaron Markham 
> > wrote:
> >
> > > Alrighty! The new site is launched. You might need to clear your cache.
> > >
> > > Cheers,
> > > Aaron
> > >
> > > On Thu, Sep 19, 2019 at 3:33 PM Aaron Markham  > >
> > > wrote:
> > > >
> > > > Thanks everyone. The PRs passed CI, but please continue holding off on
> > > > docs and CI edits. Unless there are any objections, I'd like to launch
> > > > the new website today.
> > > >
> > > > On Wed, Sep 18, 2019 at 7:46 AM Aaron Markham <
> > aaron.s.mark...@gmail.com>
> > > wrote:
> > > > >
> > > > > Hi everyone,
> > > > > The last two PRs [1][2] for the new website and docs have passed CI
> > > > > (finally). Please do not make changes to /docs or /ci until we get
> > > > > these approved and merged. Every time there's a merge conflict it has
> > > > > set us back a day or two while shepherding the PRs through CI again.
> > > > > Unless there are catastrophic issues discovered in a review, I
> > > > > recommend that we hold any patches or updates to the PRs to follow-up
> > > > > PRs.
> > > > >
> > > > > There are four steps to launch:
> > > > > 1. Once the PRs are approved, the plan is to merge 15885 to delete
> > the
> > > > > old content first.
> > > > > 2. Then immediately merge 15883 to add in the new CI flows and
> > updates
> > > > > to the content Thomas and I have already had merged in 15884 [3].
> > > > > 3. I will change the website validation Jenkins pipeline to point to
> > > > > the new pipeline.
> > > > > 4. I will change the website publishing Jenkins pipeline to point to
> > > > > its new pipeline as well. Once triggered, the old site will be
> > > > > replaced with the new one.
> > > > >
> > > > > Post launch we'll need to update the DNS for beta.mxnet.io to point
> > to
> > > > > production, and there will likely be some redirect/.htaccess updates
> > > > > needed next week to assist with any deep linking and 404 issues that
> > > > > pop up.
> > > > >
> > > > > Cheers,
> > > > > Aaron
> > > > >
> > > > > [1] https://github.com/apache/incubator-mxnet/pull/15885
> > > > > [2] https://github.com/apache/incubator-mxnet/pull/15883
> > > > > [3] https://github.com/apache/incubator-mxnet/pull/15884
> > >
> >
> 

Re: new website, docs code freeze

[Lin Yuan]

Looks very neat. Thank you Aaron and many others for launching this!

On Fri, Sep 20, 2019 at 7:31 AM Carin Meier  wrote:

> Nice!!! Congrats everyone!
>
> On Fri, Sep 20, 2019 at 10:28 AM Aaron Markham 
> wrote:
>
> > Alrighty! The new site is launched. You might need to clear your cache.
> >
> > Cheers,
> > Aaron
> >
> > On Thu, Sep 19, 2019 at 3:33 PM Aaron Markham  >
> > wrote:
> > >
> > > Thanks everyone. The PRs passed CI, but please continue holding off on
> > > docs and CI edits. Unless there are any objections, I'd like to launch
> > > the new website today.
> > >
> > > On Wed, Sep 18, 2019 at 7:46 AM Aaron Markham <
> aaron.s.mark...@gmail.com>
> > wrote:
> > > >
> > > > Hi everyone,
> > > > The last two PRs [1][2] for the new website and docs have passed CI
> > > > (finally). Please do not make changes to /docs or /ci until we get
> > > > these approved and merged. Every time there's a merge conflict it has
> > > > set us back a day or two while shepherding the PRs through CI again.
> > > > Unless there are catastrophic issues discovered in a review, I
> > > > recommend that we hold any patches or updates to the PRs to follow-up
> > > > PRs.
> > > >
> > > > There are four steps to launch:
> > > > 1. Once the PRs are approved, the plan is to merge 15885 to delete
> the
> > > > old content first.
> > > > 2. Then immediately merge 15883 to add in the new CI flows and
> updates
> > > > to the content Thomas and I have already had merged in 15884 [3].
> > > > 3. I will change the website validation Jenkins pipeline to point to
> > > > the new pipeline.
> > > > 4. I will change the website publishing Jenkins pipeline to point to
> > > > its new pipeline as well. Once triggered, the old site will be
> > > > replaced with the new one.
> > > >
> > > > Post launch we'll need to update the DNS for beta.mxnet.io to point
> to
> > > > production, and there will likely be some redirect/.htaccess updates
> > > > needed next week to assist with any deep linking and 404 issues that
> > > > pop up.
> > > >
> > > > Cheers,
> > > > Aaron
> > > >
> > > > [1] https://github.com/apache/incubator-mxnet/pull/15885
> > > > [2] https://github.com/apache/incubator-mxnet/pull/15883
> > > > [3] https://github.com/apache/incubator-mxnet/pull/15884
> >
>

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

[Marco de Abreu]

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

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.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > 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)
> > > > > > >
> > > > > > > On Thu, 19 Sep 2019 at 02:12, Tao Lv 
> > wrote:
> > > > > > >
> > > > > > > > Hi community,
> > > > > > > >
> > > > > > > > Friendly reminder: it is less than 1.5 days remaining, so
> > > > please take
> > > > > > > your
> > > > > > > > time to verify and vote.
> > > >  

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.
> > > >> > > > >
> > > >> > > > > 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] 

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

[Michael Wall]

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.
> > > >
> > > >
> > > >
> > > >
> > > > 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)
> > > > > >
> > > > > > On Thu, 19 Sep 2019 at 02:12, Tao Lv 
> wrote:
> > > > > >
> > > > > > > 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 <
> > apefor...@gmail.com>
> > > > wrote:
> > > > > > >
> > > > > > > > +1
> > > > > > > > Tested Horovod on GPU
> > > > > > > >
> > > > > > > > On Wed, Sep 18, 2019 at 6:16 AM Zhao, Patric <
> > > > patric.z...@intel.com>
> > > > > > > > wrote:
> > > > > > > 

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)
> > > > >
> > > > > On Thu, 19 Sep 2019 at 02:12, Tao Lv  wrote:
> > > > >
> > > > > > 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 <
> apefor...@gmail.com>
> > > wrote:
> > > > > >
> > > > > > > +1
> > > > > > > Tested Horovod on GPU
> > > > > > >
> > > > > > > On Wed, Sep 18, 2019 at 6:16 AM Zhao, Patric <
> > > patric.z...@intel.com>
> > > > > > > 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

Re: new website, docs code freeze

[Carin Meier]

Nice!!! Congrats everyone!

On Fri, Sep 20, 2019 at 10:28 AM Aaron Markham 
wrote:

> Alrighty! The new site is launched. You might need to clear your cache.
>
> Cheers,
> Aaron
>
> On Thu, Sep 19, 2019 at 3:33 PM Aaron Markham 
> wrote:
> >
> > Thanks everyone. The PRs passed CI, but please continue holding off on
> > docs and CI edits. Unless there are any objections, I'd like to launch
> > the new website today.
> >
> > On Wed, Sep 18, 2019 at 7:46 AM Aaron Markham 
> wrote:
> > >
> > > Hi everyone,
> > > The last two PRs [1][2] for the new website and docs have passed CI
> > > (finally). Please do not make changes to /docs or /ci until we get
> > > these approved and merged. Every time there's a merge conflict it has
> > > set us back a day or two while shepherding the PRs through CI again.
> > > Unless there are catastrophic issues discovered in a review, I
> > > recommend that we hold any patches or updates to the PRs to follow-up
> > > PRs.
> > >
> > > There are four steps to launch:
> > > 1. Once the PRs are approved, the plan is to merge 15885 to delete the
> > > old content first.
> > > 2. Then immediately merge 15883 to add in the new CI flows and updates
> > > to the content Thomas and I have already had merged in 15884 [3].
> > > 3. I will change the website validation Jenkins pipeline to point to
> > > the new pipeline.
> > > 4. I will change the website publishing Jenkins pipeline to point to
> > > its new pipeline as well. Once triggered, the old site will be
> > > replaced with the new one.
> > >
> > > Post launch we'll need to update the DNS for beta.mxnet.io to point to
> > > production, and there will likely be some redirect/.htaccess updates
> > > needed next week to assist with any deep linking and 404 issues that
> > > pop up.
> > >
> > > Cheers,
> > > Aaron
> > >
> > > [1] https://github.com/apache/incubator-mxnet/pull/15885
> > > [2] https://github.com/apache/incubator-mxnet/pull/15883
> > > [3] https://github.com/apache/incubator-mxnet/pull/15884
>

Re: new website, docs code freeze

[Aaron Markham]

Alrighty! The new site is launched. You might need to clear your cache.

Cheers,
Aaron

On Thu, Sep 19, 2019 at 3:33 PM Aaron Markham  wrote:
>
> Thanks everyone. The PRs passed CI, but please continue holding off on
> docs and CI edits. Unless there are any objections, I'd like to launch
> the new website today.
>
> On Wed, Sep 18, 2019 at 7:46 AM Aaron Markham  
> wrote:
> >
> > Hi everyone,
> > The last two PRs [1][2] for the new website and docs have passed CI
> > (finally). Please do not make changes to /docs or /ci until we get
> > these approved and merged. Every time there's a merge conflict it has
> > set us back a day or two while shepherding the PRs through CI again.
> > Unless there are catastrophic issues discovered in a review, I
> > recommend that we hold any patches or updates to the PRs to follow-up
> > PRs.
> >
> > There are four steps to launch:
> > 1. Once the PRs are approved, the plan is to merge 15885 to delete the
> > old content first.
> > 2. Then immediately merge 15883 to add in the new CI flows and updates
> > to the content Thomas and I have already had merged in 15884 [3].
> > 3. I will change the website validation Jenkins pipeline to point to
> > the new pipeline.
> > 4. I will change the website publishing Jenkins pipeline to point to
> > its new pipeline as well. Once triggered, the old site will be
> > replaced with the new one.
> >
> > Post launch we'll need to update the DNS for beta.mxnet.io to point to
> > production, and there will likely be some redirect/.htaccess updates
> > needed next week to assist with any deep linking and 404 issues that
> > pop up.
> >
> > Cheers,
> > Aaron
> >
> > [1] https://github.com/apache/incubator-mxnet/pull/15885
> > [2] https://github.com/apache/incubator-mxnet/pull/15883
> > [3] https://github.com/apache/incubator-mxnet/pull/15884

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

[Carin Meier]

+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)
> > > >
> > > > On Thu, 19 Sep 2019 at 02:12, Tao Lv  wrote:
> > > >
> > > > > 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 <
> > patric.z...@intel.com>
> > > > > > 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 <
> > > 

Re: Code freeze for 1.5.1 patch release

[Carin Meier]

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.
> > >> > > > >
> > >> > > > > 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!
> > >> > >