[ANNOUNCE] Release Apache MXNet (incubating) version 1.6.0
Dear All, The Apache MXNet (incubating) community is happy to announce Apache MXNet (incubating) version 1.6.0! Release blog post: https://medium.com/apache-mxnet/apache-mxnet-1-6-0-release-is-now-available-f48f1dd16dd0 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. A full list of the changes in this release can be found in the release notes: https://cwiki.apache.org/confluence/display/MXNET/1.6.0+Release+notes A link to the download can be found here: https://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: https://mxnet.incubator.apache.org/get_started Or you can download and play with MXNet easily using the Pip packages, which can be found here: https://pypi.python.org/pypi/mxnet The Release Tag: https://github.com/apache/incubator-mxnet/tree/1.6.0 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) For more information on Apache MXNet (incubating), please see: https://mxnet.incubator.apache.org Best regards, Apache MXNet (incubating) Team
Fwd: [MENTORS] Podlings with releases but no download pages
I just saw this email on the incubator general mailing list. MXNet is missing an apache download page. Is anyone interested in adding one? Zach -- Forwarded message - From: Justin Mclean Date: Tue, Mar 3, 2020 at 5:44 PM Subject: [MENTORS] Podlings with releases but no download pages To: Hi, >From a quick look these podlings have made releases but don’t have a download pages: Annotator Datasketches DLab Doris Hivemall (download from front page) MXNet PageSpeed - only has pre apache downloads Samoa - has direct link Superset TVM Can you ask your podling to set up one up. [1][2] Thanks, Justin 1. http://www.apache.org/dev/release-download-pages.html#download-page 2. https://www.apache.org/dev/release-distribution#download-links - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Fwd: [MENTORS] Podlings with releases but no download pages
Wait, what? That's not right - I was even discussing this with Sheng yesterday (as I did not immediately see that page, which I agree is a problem, but still, that page exists). It is https://mxnet.incubator.apache.org/get_started/download Przemek On 2020/03/04 21:11:04, Zach Kimberg wrote: > I just saw this email on the incubator general mailing list. MXNet is > missing an apache download page. Is anyone interested in adding one? > > Zach > > -- Forwarded message - > From: Justin Mclean > Date: Tue, Mar 3, 2020 at 5:44 PM > Subject: [MENTORS] Podlings with releases but no download pages > To: > > > Hi, > > From a quick look these podlings have made releases but don’t have a > download pages: > Annotator > Datasketches > DLab > Doris > Hivemall (download from front page) > MXNet > PageSpeed - only has pre apache downloads > Samoa - has direct link > Superset > TVM > > Can you ask your podling to set up one up. [1][2] > > Thanks, > Justin > > 1. http://www.apache.org/dev/release-download-pages.html#download-page > 2. https://www.apache.org/dev/release-distribution#download-links > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
Re: [apache/incubator-mxnet] [RFC] New Branches for MXNet 1.x, 1.7.x, and 2.x (#17701)
Website versioning is tracked in https://github.com/apache/incubator-mxnet/issues/17497 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-mxnet/issues/17701#issuecomment-594916076
Re: [apache/incubator-mxnet] [RFC] New Branches for MXNet 1.x, 1.7.x, and 2.x (#17701)
@leezu @szha - We need a clear direction on what to do for the current site's docs generation. It isn't really website versioning. It's generating documentation from different branches. The core website jekyll should stay the same and be generated from master. However, the default docs for each API can be generated from a specific version/branch. -- 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/17701#issuecomment-594925989
Re: [apache/incubator-mxnet] [RFC] New Branches for MXNet 1.x, 1.7.x, and 2.x (#17701)
It's not only about the API documentation. Installation instructions or tutorials will change over time. Building the website independently for different versions may be the simplest approach. I'm also fine with any other approach that enables users to look up documentation and instructions for their respective version. -- 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/17701#issuecomment-594934176
Re: [apache/incubator-mxnet] [RFC] MXNet 2.0 API Deprecation (#17676)
I am generally in favor of those deprecations. The scariest part is the removal of `mx.module` API, so definitely `Gluon is on par with module in terms of functionality and performance` is very important for this to be successful. -- 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-594945007
Re: [apache/incubator-mxnet] [RFC] MXNet 2.0 API Deprecation (#17676)
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] MXNet 2.0 API Deprecation (#17676)
@TaoLv the search result shows API in the following categories: - operator (these will be deprecated and the newest version should be covered in https://github.com/apache/incubator-mxnet/issues/17096) - gluon blocks (e.g. Con**v1**D). they are not legacy ops and will be kept - io (these will be deprecated and replacement is covered in 2.0 roadmap item 4.8 data API enhancement) - model zoo (e.g. ResNet**V1**). they are not legacy API and will be kept -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-mxnet/issues/17676#issuecomment-595018894
