[RESULTS][VOTE] Release Apache MXNet (incubating) 1.5.1.rc0
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
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 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
RE: new website, docs code freeze
Minor suggestion: I think we can add more in features page to attract the user and also highlight the differentiation of MXNet. Something like quantization, faster inference and training, horovod supporting, AMP, automatic fusion in the fly... http://mxnet.incubator.apache.org/features Thanks, --Patric > -Original Message- > From: Thomas DELTEIL > Sent: Saturday, September 21, 2019 12:29 PM > To: dev@mxnet.incubator.apache.org > Subject: Re: new website, docs code freeze > > 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 > > > > > > > >
