Re: [Discuss] MXNet Python 2 Support Deprecation
+1 On Fri, Jul 19, 2019, 04:28 Pedro Larroy wrote: > Seems 3.6 is a reasonable choice. > > On Thu, Jul 18, 2019 at 2:15 PM Marco de Abreu > wrote: > > > > Looking at EOL is certainly a good idea! I think once we get closer to > > deprecation, we can check adoption statistics to make a well-informed > > decision that gives us the most advantages without dropping the ball on a > > majority of users (or supporting a branch that is going EOL soon). A > survey > > from 2018 [1] determined the following distribution: > > 3.5: 11% > > 3.6: 54% > > 3.7: 30% > > > > Deprecation for 3.5 is scheduled for 2020-09-13 [2]. Deprecation for 3.6 > is > > scheduled for 2021-12-23 [2].Deprecation for 3.7 is scheduled > > for 2023-06-27 [2]. > > > > Following the trend, I'd say that it would be a decision between Python > 3.6 > > and 3.7. Later on, I'd propose to check recent surveys and also have a > > separate thread to determine if there's anything we're missing (e.g. a > big > > company being unable to use Python 3.7). What do you think? > > > > Best regards, > > Marco > > > > [1]: https://www.jetbrains.com/research/python-developers-survey-2018/ > > [2]: https://devguide.python.org/#status-of-python-branches > > > > On Thu, Jul 18, 2019 at 9:42 PM Yuan Tang > wrote: > > > > > I would suggest supporting Python 3.5+ since the earlier versions have > > > reached end-of-life status: > > > https://devguide.python.org/devcycle/#end-of-life-branches > > > > > > On Thu, Jul 18, 2019 at 3:36 PM Pedro Larroy < > pedro.larroy.li...@gmail.com > > > > > > > wrote: > > > > > > > +1 > > > > > > > > This would simplify CI, reduce costs and more. I think a followup > > > > question is what would be the mininum Python3 version supported? > > > > Depending on that we might be able to use type annotations for > example > > > > or other features. > > > > > > > > Pedro. > > > > > > > > On Thu, Jul 18, 2019 at 12:07 PM Yuan Tang > > > > wrote: > > > > > > > > > > +1 > > > > > > > > > > On Thu, Jul 18, 2019 at 2:51 PM Yuxi Hu > wrote: > > > > > > > > > > > +1 > > > > > > > > > > > > On Thu, Jul 18, 2019 at 11:31 AM Tong He > > > wrote: > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > Tong He > > > > > > > > > > > > > > > > > > > > > Jake Lee 于2019年7月18日周四 上午11:29写道： > > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > > > On Thu, Jul 18, 2019 at 11:27 AM Junru Shao < > > > > junrushao1...@gmail.com> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > > > > > On Thu, Jul 18, 2019 at 11:12 AM Anirudh Acharya < > > > > > > > anirudhk...@gmail.com> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > > > > > > > On Thu, Jul 18, 2019 at 11:03 AM Marco de Abreu < > > > > > > > > marco.g.ab...@gmail.com > > > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > > > > > > > > > -Marco > > > > > > > > > > > > > > > > > > > > > > Sheng Zha schrieb am Do., 18. > Juli > > > > 2019, > > > > > > > > 19:59: > > > > > > > > > > > > > > > > > > > > > > > Dear MXNet community, > > > > > > > > > > > > > > > > > > > > > > > > I'd like to reopen the discussion on deprecating > python2 > > > > > > support. > > > > > > > > > This > > > > > > > > > > > > would help modernize the design and engineering > practice > > > in > > > > > > MXNet > > > > > > > > to > > > > > > > > > > help > > > > > > > > > > > > improve speed and quality. > > > > > > > > > > > > > > > > > > > > > > > > For this purpose, I reopened the issue on this here: > > > > > > > > > > > > > https://github.com/apache/incubator-mxnet/issues/8703 > > > > > > > > > > > > > > > > > > > > > > > > If the consensus is towards the direction of dropping > > > > python2 > > > > > > > > > support, > > > > > > > > > > I > > > > > > > > > > > > suggest we announce our plan to drop python2 support > in > > > the > > > > > > next > > > > > > > > > > release, > > > > > > > > > > > > and actually drop the support in the next major > version. > > > > > > Thanks. > > > > > > > > > > > > > > > > > > > > > > > > -sz > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Yuxi(Darren) Hu, Ph.D. > > > > > > Software Development Engineer > > > > > > Amazon Web Services > > > > > > > > > > > > > >
Re: [Discuss] MXNet Python 2 Support Deprecation
Seems 3.6 is a reasonable choice. On Thu, Jul 18, 2019 at 2:15 PM Marco de Abreu wrote: > > Looking at EOL is certainly a good idea! I think once we get closer to > deprecation, we can check adoption statistics to make a well-informed > decision that gives us the most advantages without dropping the ball on a > majority of users (or supporting a branch that is going EOL soon). A survey > from 2018 [1] determined the following distribution: > 3.5: 11% > 3.6: 54% > 3.7: 30% > > Deprecation for 3.5 is scheduled for 2020-09-13 [2]. Deprecation for 3.6 is > scheduled for 2021-12-23 [2].Deprecation for 3.7 is scheduled > for 2023-06-27 [2]. > > Following the trend, I'd say that it would be a decision between Python 3.6 > and 3.7. Later on, I'd propose to check recent surveys and also have a > separate thread to determine if there's anything we're missing (e.g. a big > company being unable to use Python 3.7). What do you think? > > Best regards, > Marco > > [1]: https://www.jetbrains.com/research/python-developers-survey-2018/ > [2]: https://devguide.python.org/#status-of-python-branches > > On Thu, Jul 18, 2019 at 9:42 PM Yuan Tang wrote: > > > I would suggest supporting Python 3.5+ since the earlier versions have > > reached end-of-life status: > > https://devguide.python.org/devcycle/#end-of-life-branches > > > > On Thu, Jul 18, 2019 at 3:36 PM Pedro Larroy > > > > wrote: > > > > > +1 > > > > > > This would simplify CI, reduce costs and more. I think a followup > > > question is what would be the mininum Python3 version supported? > > > Depending on that we might be able to use type annotations for example > > > or other features. > > > > > > Pedro. > > > > > > On Thu, Jul 18, 2019 at 12:07 PM Yuan Tang > > > wrote: > > > > > > > > +1 > > > > > > > > On Thu, Jul 18, 2019 at 2:51 PM Yuxi Hu wrote: > > > > > > > > > +1 > > > > > > > > > > On Thu, Jul 18, 2019 at 11:31 AM Tong He > > wrote: > > > > > > > > > > > +1 > > > > > > > > > > > > Best regards, > > > > > > > > > > > > Tong He > > > > > > > > > > > > > > > > > > Jake Lee 于2019年7月18日周四 上午11:29写道： > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > On Thu, Jul 18, 2019 at 11:27 AM Junru Shao < > > > junrushao1...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > > > On Thu, Jul 18, 2019 at 11:12 AM Anirudh Acharya < > > > > > > anirudhk...@gmail.com> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > > > > > On Thu, Jul 18, 2019 at 11:03 AM Marco de Abreu < > > > > > > > marco.g.ab...@gmail.com > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > > > > > > > -Marco > > > > > > > > > > > > > > > > > > > > Sheng Zha schrieb am Do., 18. Juli > > > 2019, > > > > > > > 19:59: > > > > > > > > > > > > > > > > > > > > > Dear MXNet community, > > > > > > > > > > > > > > > > > > > > > > I'd like to reopen the discussion on deprecating python2 > > > > > support. > > > > > > > > This > > > > > > > > > > > would help modernize the design and engineering practice > > in > > > > > MXNet > > > > > > > to > > > > > > > > > help > > > > > > > > > > > improve speed and quality. > > > > > > > > > > > > > > > > > > > > > > For this purpose, I reopened the issue on this here: > > > > > > > > > > > https://github.com/apache/incubator-mxnet/issues/8703 > > > > > > > > > > > > > > > > > > > > > > If the consensus is towards the direction of dropping > > > python2 > > > > > > > > support, > > > > > > > > > I > > > > > > > > > > > suggest we announce our plan to drop python2 support in > > the > > > > > next > > > > > > > > > release, > > > > > > > > > > > and actually drop the support in the next major version. > > > > > Thanks. > > > > > > > > > > > > > > > > > > > > > > -sz > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Yuxi(Darren) Hu, Ph.D. > > > > > Software Development Engineer > > > > > Amazon Web Services > > > > > > > > > >
Re: demise of dmlc.ml domain & new Julia docs hosting
Great, thanks for the links and for working on the plan. I think the community should align on the requirements of the new website as long as it's still in development. We can then do an analysis in how far the current state of the beta website differs from the requirements and make that part of the transition plan. Would you mind leading the technical requirement gathering? Best regards, Marco On Thu, Jul 18, 2019 at 11:22 PM Aaron Markham wrote: > What I have written doesn't directly align with the beta site. The site was > created by Mu, and several people have contributed to updating it with > content. The repo is here https://github.com/mli/new-docs > There's no architecture doc afaik. > > I have docs for a redesign and new ux in the wiki: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103089084 > I've tried to apply some of the IA to the beta site, but I'm constrained by > the Sphinx template. > > There's decent progress in the beta site, but it has the drawback of > lock-in with Sphinx again. And covers only Python and R. > > I will be writing a doc to cover a transition plan. I will try to layer it, > so we have the bare minimum all the way to the optimal route. That being > said, any plan requires resources. It's not going to be easy. > > On Thu, Jul 18, 2019, 14:01 Marco de Abreu > wrote: > > > I see. Would you mind linking the thread/doc where we discussed the > > requirements for the new website? > > > > -Marco > > > > On Thu, Jul 18, 2019 at 9:49 PM Aaron Markham > > > wrote: > > > > > I agree with you. I'd like the website to be fairly standard Jekyll and > > > normal front end stuff, rather than a Sphinx template. Docs would be > docs > > > built by doxygen, Sphinx, Scala, java, etc, based on their native docs > > > generation, and we'd get a microsite for each language binding. If one > > > breaks it doesn't break the whole website. You can build them > separately > > or > > > build a particular version. I made the settings system accomplish that > > with > > > our Sphinx build, but the template we have tied with the old versions > > keeps > > > us locked into a complex build. > > > > > > If we must support old versions then this notion needs to be part of > the > > > new beta Python site, and as far as I know, that's not planned. It is > not > > > supported in the beta site now. > > > > > > On Thu, Jul 18, 2019, 12:31 Marco de Abreu > > > wrote: > > > > > > > I'm not entirely sure about dropping docs for old versions to be > > honest. > > > > The root cause in my opinion is the fact that the build is wy to > > > > complicated. If it would have less dependencies and be more > > > > straight-forward, it should be a matter of seconds. The key here > could > > be > > > > to separate the docs from the website. Doc generation should be a > > simple > > > > matter of "run doxygen" (or whatever we use). Right now, the website > > > build > > > > process intermingles every aspect of it. If each version (and > language) > > > > would just output a docs folder that has no outgoing references, they > > > could > > > > be created entirely independent of another. Right now, we regenerate > > > every > > > > version for every single build - that's not necessary. > > > > > > > > Considering how many people are unable to use the latest version of > > > MXNet, > > > > I'd prefer if we provide the docs as long as the release binaries are > > > > available. > > > > > > > > -Marco > > > > > > > > Aaron Markham schrieb am Do., 18. Juli > > 2019, > > > > 21:20: > > > > > > > > > I'd have it check signatures. Ssl is optional I think. China users > > seem > > > > to > > > > > have issues with SSL... That may have changed, but I think we might > > > have > > > > to > > > > > work around that for background downloads for models. > > > > > > > > > > With regard to the current links to dmlc.ml, I asked ivy to just > get > > > rid > > > > > of > > > > > them with # if necessary. Better to 404 than go to malware. This > > > requires > > > > > going back into previous release branches and purging those > > references. > > > > > > > > > > The website is publishing regularly again. I had trouble getting > > Julia > > > to > > > > > work in CI for generating the Julia docs, but I have it working > now. > > > > > > > > > > As we move forward with yet another release, plus the potential > > launch > > > of > > > > > the new Python docs site we need to consider reducing complexity of > > the > > > > > build and prune old versions. I think we should only host master or > > the > > > > > most recent release, and provide instructions on how to generate > > other > > > > > versions. Otherwise the transition will be too difficult and > > > disruptive. > > > > > > > > > > On Tue, Jul 16, 2019, 16:41 Marco de Abreu < > marco.g.ab...@gmail.com> > > > > > wrote: > > > > > > > > > > > While we are at it, we should maybe also take about SSL to avoid > > > these > > > > > > kinds of downloads in future.
Re: demise of dmlc.ml domain & new Julia docs hosting
What I have written doesn't directly align with the beta site. The site was created by Mu, and several people have contributed to updating it with content. The repo is here https://github.com/mli/new-docs There's no architecture doc afaik. I have docs for a redesign and new ux in the wiki: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103089084 I've tried to apply some of the IA to the beta site, but I'm constrained by the Sphinx template. There's decent progress in the beta site, but it has the drawback of lock-in with Sphinx again. And covers only Python and R. I will be writing a doc to cover a transition plan. I will try to layer it, so we have the bare minimum all the way to the optimal route. That being said, any plan requires resources. It's not going to be easy. On Thu, Jul 18, 2019, 14:01 Marco de Abreu wrote: > I see. Would you mind linking the thread/doc where we discussed the > requirements for the new website? > > -Marco > > On Thu, Jul 18, 2019 at 9:49 PM Aaron Markham > wrote: > > > I agree with you. I'd like the website to be fairly standard Jekyll and > > normal front end stuff, rather than a Sphinx template. Docs would be docs > > built by doxygen, Sphinx, Scala, java, etc, based on their native docs > > generation, and we'd get a microsite for each language binding. If one > > breaks it doesn't break the whole website. You can build them separately > or > > build a particular version. I made the settings system accomplish that > with > > our Sphinx build, but the template we have tied with the old versions > keeps > > us locked into a complex build. > > > > If we must support old versions then this notion needs to be part of the > > new beta Python site, and as far as I know, that's not planned. It is not > > supported in the beta site now. > > > > On Thu, Jul 18, 2019, 12:31 Marco de Abreu > > wrote: > > > > > I'm not entirely sure about dropping docs for old versions to be > honest. > > > The root cause in my opinion is the fact that the build is wy to > > > complicated. If it would have less dependencies and be more > > > straight-forward, it should be a matter of seconds. The key here could > be > > > to separate the docs from the website. Doc generation should be a > simple > > > matter of "run doxygen" (or whatever we use). Right now, the website > > build > > > process intermingles every aspect of it. If each version (and language) > > > would just output a docs folder that has no outgoing references, they > > could > > > be created entirely independent of another. Right now, we regenerate > > every > > > version for every single build - that's not necessary. > > > > > > Considering how many people are unable to use the latest version of > > MXNet, > > > I'd prefer if we provide the docs as long as the release binaries are > > > available. > > > > > > -Marco > > > > > > Aaron Markham schrieb am Do., 18. Juli > 2019, > > > 21:20: > > > > > > > I'd have it check signatures. Ssl is optional I think. China users > seem > > > to > > > > have issues with SSL... That may have changed, but I think we might > > have > > > to > > > > work around that for background downloads for models. > > > > > > > > With regard to the current links to dmlc.ml, I asked ivy to just get > > rid > > > > of > > > > them with # if necessary. Better to 404 than go to malware. This > > requires > > > > going back into previous release branches and purging those > references. > > > > > > > > The website is publishing regularly again. I had trouble getting > Julia > > to > > > > work in CI for generating the Julia docs, but I have it working now. > > > > > > > > As we move forward with yet another release, plus the potential > launch > > of > > > > the new Python docs site we need to consider reducing complexity of > the > > > > build and prune old versions. I think we should only host master or > the > > > > most recent release, and provide instructions on how to generate > other > > > > versions. Otherwise the transition will be too difficult and > > disruptive. > > > > > > > > On Tue, Jul 16, 2019, 16:41 Marco de Abreu > > > > wrote: > > > > > > > > > While we are at it, we should maybe also take about SSL to avoid > > these > > > > > kinds of downloads in future. > > > > > > > > > > -Marco > > > > > > > > > > Aaron Markham schrieb am Mi., 17. Juli > > > 2019, > > > > > 01:20: > > > > > > > > > > > Hi Hen, > > > > > > We still have all of the these models that are referenced in this > > > > > > issue: https://github.com/apache/incubator-mxnet/issues/15410 > > > > > > I think it's a pretty big security breach to have systems that do > > > > > > automatic downloading point to a malware site. Anything that > > fetches > > > > > > binary data should be well secured and it really lowers trust if > > > > > > assets send customers to malware sites. > > > > > > There might be more. > > > > > > > > > > > > On Sat, Jul 13, 2019 at 1:00 PM Hen wrote: > > > > > > > > > > > > > > Nice
Re: [Discuss] MXNet Python 2 Support Deprecation
Looking at EOL is certainly a good idea! I think once we get closer to deprecation, we can check adoption statistics to make a well-informed decision that gives us the most advantages without dropping the ball on a majority of users (or supporting a branch that is going EOL soon). A survey from 2018 [1] determined the following distribution: 3.5: 11% 3.6: 54% 3.7: 30% Deprecation for 3.5 is scheduled for 2020-09-13 [2]. Deprecation for 3.6 is scheduled for 2021-12-23 [2].Deprecation for 3.7 is scheduled for 2023-06-27 [2]. Following the trend, I'd say that it would be a decision between Python 3.6 and 3.7. Later on, I'd propose to check recent surveys and also have a separate thread to determine if there's anything we're missing (e.g. a big company being unable to use Python 3.7). What do you think? Best regards, Marco [1]: https://www.jetbrains.com/research/python-developers-survey-2018/ [2]: https://devguide.python.org/#status-of-python-branches On Thu, Jul 18, 2019 at 9:42 PM Yuan Tang wrote: > I would suggest supporting Python 3.5+ since the earlier versions have > reached end-of-life status: > https://devguide.python.org/devcycle/#end-of-life-branches > > On Thu, Jul 18, 2019 at 3:36 PM Pedro Larroy > > wrote: > > > +1 > > > > This would simplify CI, reduce costs and more. I think a followup > > question is what would be the mininum Python3 version supported? > > Depending on that we might be able to use type annotations for example > > or other features. > > > > Pedro. > > > > On Thu, Jul 18, 2019 at 12:07 PM Yuan Tang > > wrote: > > > > > > +1 > > > > > > On Thu, Jul 18, 2019 at 2:51 PM Yuxi Hu wrote: > > > > > > > +1 > > > > > > > > On Thu, Jul 18, 2019 at 11:31 AM Tong He > wrote: > > > > > > > > > +1 > > > > > > > > > > Best regards, > > > > > > > > > > Tong He > > > > > > > > > > > > > > > Jake Lee 于2019年7月18日周四 上午11:29写道： > > > > > > > > > > > +1 > > > > > > > > > > > > On Thu, Jul 18, 2019 at 11:27 AM Junru Shao < > > junrushao1...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > On Thu, Jul 18, 2019 at 11:12 AM Anirudh Acharya < > > > > > anirudhk...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > > > On Thu, Jul 18, 2019 at 11:03 AM Marco de Abreu < > > > > > > marco.g.ab...@gmail.com > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > > > > > -Marco > > > > > > > > > > > > > > > > > > Sheng Zha schrieb am Do., 18. Juli > > 2019, > > > > > > 19:59: > > > > > > > > > > > > > > > > > > > Dear MXNet community, > > > > > > > > > > > > > > > > > > > > I'd like to reopen the discussion on deprecating python2 > > > > support. > > > > > > > This > > > > > > > > > > would help modernize the design and engineering practice > in > > > > MXNet > > > > > > to > > > > > > > > help > > > > > > > > > > improve speed and quality. > > > > > > > > > > > > > > > > > > > > For this purpose, I reopened the issue on this here: > > > > > > > > > > https://github.com/apache/incubator-mxnet/issues/8703 > > > > > > > > > > > > > > > > > > > > If the consensus is towards the direction of dropping > > python2 > > > > > > > support, > > > > > > > > I > > > > > > > > > > suggest we announce our plan to drop python2 support in > the > > > > next > > > > > > > > release, > > > > > > > > > > and actually drop the support in the next major version. > > > > Thanks. > > > > > > > > > > > > > > > > > > > > -sz > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Yuxi(Darren) Hu, Ph.D. > > > > Software Development Engineer > > > > Amazon Web Services > > > > > > >
Re: demise of dmlc.ml domain & new Julia docs hosting
I see. Would you mind linking the thread/doc where we discussed the requirements for the new website? -Marco On Thu, Jul 18, 2019 at 9:49 PM Aaron Markham wrote: > I agree with you. I'd like the website to be fairly standard Jekyll and > normal front end stuff, rather than a Sphinx template. Docs would be docs > built by doxygen, Sphinx, Scala, java, etc, based on their native docs > generation, and we'd get a microsite for each language binding. If one > breaks it doesn't break the whole website. You can build them separately or > build a particular version. I made the settings system accomplish that with > our Sphinx build, but the template we have tied with the old versions keeps > us locked into a complex build. > > If we must support old versions then this notion needs to be part of the > new beta Python site, and as far as I know, that's not planned. It is not > supported in the beta site now. > > On Thu, Jul 18, 2019, 12:31 Marco de Abreu > wrote: > > > I'm not entirely sure about dropping docs for old versions to be honest. > > The root cause in my opinion is the fact that the build is wy to > > complicated. If it would have less dependencies and be more > > straight-forward, it should be a matter of seconds. The key here could be > > to separate the docs from the website. Doc generation should be a simple > > matter of "run doxygen" (or whatever we use). Right now, the website > build > > process intermingles every aspect of it. If each version (and language) > > would just output a docs folder that has no outgoing references, they > could > > be created entirely independent of another. Right now, we regenerate > every > > version for every single build - that's not necessary. > > > > Considering how many people are unable to use the latest version of > MXNet, > > I'd prefer if we provide the docs as long as the release binaries are > > available. > > > > -Marco > > > > Aaron Markham schrieb am Do., 18. Juli 2019, > > 21:20: > > > > > I'd have it check signatures. Ssl is optional I think. China users seem > > to > > > have issues with SSL... That may have changed, but I think we might > have > > to > > > work around that for background downloads for models. > > > > > > With regard to the current links to dmlc.ml, I asked ivy to just get > rid > > > of > > > them with # if necessary. Better to 404 than go to malware. This > requires > > > going back into previous release branches and purging those references. > > > > > > The website is publishing regularly again. I had trouble getting Julia > to > > > work in CI for generating the Julia docs, but I have it working now. > > > > > > As we move forward with yet another release, plus the potential launch > of > > > the new Python docs site we need to consider reducing complexity of the > > > build and prune old versions. I think we should only host master or the > > > most recent release, and provide instructions on how to generate other > > > versions. Otherwise the transition will be too difficult and > disruptive. > > > > > > On Tue, Jul 16, 2019, 16:41 Marco de Abreu > > > wrote: > > > > > > > While we are at it, we should maybe also take about SSL to avoid > these > > > > kinds of downloads in future. > > > > > > > > -Marco > > > > > > > > Aaron Markham schrieb am Mi., 17. Juli > > 2019, > > > > 01:20: > > > > > > > > > Hi Hen, > > > > > We still have all of the these models that are referenced in this > > > > > issue: https://github.com/apache/incubator-mxnet/issues/15410 > > > > > I think it's a pretty big security breach to have systems that do > > > > > automatic downloading point to a malware site. Anything that > fetches > > > > > binary data should be well secured and it really lowers trust if > > > > > assets send customers to malware sites. > > > > > There might be more. > > > > > > > > > > On Sat, Jul 13, 2019 at 1:00 PM Hen wrote: > > > > > > > > > > > > Nice work :) > > > > > > > > > > > > What other links does the project have that are outside Apache > > Infra > > > > > > control and have this risk? > > > > > > > > > > > > Outside of github.com/dmlc which is well known and iiuc in > process > > > for > > > > > > resolving. > > > > > > > > > > > > Hen > > > > > > > > > > > > > > > > > > On Tue, Jul 9, 2019 at 4:46 PM Aaron Markham < > > > > aaron.s.mark...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > The PR has passed CI. Please take a look. > > > > > > > https://github.com/apache/incubator-mxnet/pull/15454 > > > > > > > We really need to get rid of those malware links, and this does > > > that, > > > > > > > restores the Julia docs with a local build, has CI coverage, > and > > a > > > > new > > > > > > > Ubuntu guide (since I had to figure out how to use Julia and > > found > > > > our > > > > > > > docs for that were kind of broken). > > > > > > > Cheers, > > > > > > > Aaron > > > > > > > > > > > > > > On Thu, Jul 4, 2019 at 8:09 PM Iblis Lin > > > > > wrote: > > > > > > > > > > > > > > > > Hi, > > > > > >
Re: demise of dmlc.ml domain & new Julia docs hosting
I agree with you. I'd like the website to be fairly standard Jekyll and normal front end stuff, rather than a Sphinx template. Docs would be docs built by doxygen, Sphinx, Scala, java, etc, based on their native docs generation, and we'd get a microsite for each language binding. If one breaks it doesn't break the whole website. You can build them separately or build a particular version. I made the settings system accomplish that with our Sphinx build, but the template we have tied with the old versions keeps us locked into a complex build. If we must support old versions then this notion needs to be part of the new beta Python site, and as far as I know, that's not planned. It is not supported in the beta site now. On Thu, Jul 18, 2019, 12:31 Marco de Abreu wrote: > I'm not entirely sure about dropping docs for old versions to be honest. > The root cause in my opinion is the fact that the build is wy to > complicated. If it would have less dependencies and be more > straight-forward, it should be a matter of seconds. The key here could be > to separate the docs from the website. Doc generation should be a simple > matter of "run doxygen" (or whatever we use). Right now, the website build > process intermingles every aspect of it. If each version (and language) > would just output a docs folder that has no outgoing references, they could > be created entirely independent of another. Right now, we regenerate every > version for every single build - that's not necessary. > > Considering how many people are unable to use the latest version of MXNet, > I'd prefer if we provide the docs as long as the release binaries are > available. > > -Marco > > Aaron Markham schrieb am Do., 18. Juli 2019, > 21:20: > > > I'd have it check signatures. Ssl is optional I think. China users seem > to > > have issues with SSL... That may have changed, but I think we might have > to > > work around that for background downloads for models. > > > > With regard to the current links to dmlc.ml, I asked ivy to just get rid > > of > > them with # if necessary. Better to 404 than go to malware. This requires > > going back into previous release branches and purging those references. > > > > The website is publishing regularly again. I had trouble getting Julia to > > work in CI for generating the Julia docs, but I have it working now. > > > > As we move forward with yet another release, plus the potential launch of > > the new Python docs site we need to consider reducing complexity of the > > build and prune old versions. I think we should only host master or the > > most recent release, and provide instructions on how to generate other > > versions. Otherwise the transition will be too difficult and disruptive. > > > > On Tue, Jul 16, 2019, 16:41 Marco de Abreu > > wrote: > > > > > While we are at it, we should maybe also take about SSL to avoid these > > > kinds of downloads in future. > > > > > > -Marco > > > > > > Aaron Markham schrieb am Mi., 17. Juli > 2019, > > > 01:20: > > > > > > > Hi Hen, > > > > We still have all of the these models that are referenced in this > > > > issue: https://github.com/apache/incubator-mxnet/issues/15410 > > > > I think it's a pretty big security breach to have systems that do > > > > automatic downloading point to a malware site. Anything that fetches > > > > binary data should be well secured and it really lowers trust if > > > > assets send customers to malware sites. > > > > There might be more. > > > > > > > > On Sat, Jul 13, 2019 at 1:00 PM Hen wrote: > > > > > > > > > > Nice work :) > > > > > > > > > > What other links does the project have that are outside Apache > Infra > > > > > control and have this risk? > > > > > > > > > > Outside of github.com/dmlc which is well known and iiuc in process > > for > > > > > resolving. > > > > > > > > > > Hen > > > > > > > > > > > > > > > On Tue, Jul 9, 2019 at 4:46 PM Aaron Markham < > > > aaron.s.mark...@gmail.com> > > > > > wrote: > > > > > > > > > > > The PR has passed CI. Please take a look. > > > > > > https://github.com/apache/incubator-mxnet/pull/15454 > > > > > > We really need to get rid of those malware links, and this does > > that, > > > > > > restores the Julia docs with a local build, has CI coverage, and > a > > > new > > > > > > Ubuntu guide (since I had to figure out how to use Julia and > found > > > our > > > > > > docs for that were kind of broken). > > > > > > Cheers, > > > > > > Aaron > > > > > > > > > > > > On Thu, Jul 4, 2019 at 8:09 PM Iblis Lin > > > wrote: > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > I will add +1 to the micro-site approach. > > > > > > > Since I have tried to take the generated MD outputs from > > > > > > > Julia's doc system, but the syntax is incompatible with > > > > > > > the MD plugin of Sphinx. > > > > > > > > > > > > > > Iblis Lin > > > > > > > 林峻頤 > > > > > > > > > > > > > > On 7/4/19 12:12 PM, Aaron Markham wrote: > > > > > > > > Hi dev@, > > > > > > > > In case you
Re: [Discuss] MXNet Python 2 Support Deprecation
I would suggest supporting Python 3.5+ since the earlier versions have reached end-of-life status: https://devguide.python.org/devcycle/#end-of-life-branches On Thu, Jul 18, 2019 at 3:36 PM Pedro Larroy wrote: > +1 > > This would simplify CI, reduce costs and more. I think a followup > question is what would be the mininum Python3 version supported? > Depending on that we might be able to use type annotations for example > or other features. > > Pedro. > > On Thu, Jul 18, 2019 at 12:07 PM Yuan Tang > wrote: > > > > +1 > > > > On Thu, Jul 18, 2019 at 2:51 PM Yuxi Hu wrote: > > > > > +1 > > > > > > On Thu, Jul 18, 2019 at 11:31 AM Tong He wrote: > > > > > > > +1 > > > > > > > > Best regards, > > > > > > > > Tong He > > > > > > > > > > > > Jake Lee 于2019年7月18日周四 上午11:29写道： > > > > > > > > > +1 > > > > > > > > > > On Thu, Jul 18, 2019 at 11:27 AM Junru Shao < > junrushao1...@gmail.com> > > > > > wrote: > > > > > > > > > > > +1 > > > > > > > > > > > > On Thu, Jul 18, 2019 at 11:12 AM Anirudh Acharya < > > > > anirudhk...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > On Thu, Jul 18, 2019 at 11:03 AM Marco de Abreu < > > > > > marco.g.ab...@gmail.com > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > > > -Marco > > > > > > > > > > > > > > > > Sheng Zha schrieb am Do., 18. Juli > 2019, > > > > > 19:59: > > > > > > > > > > > > > > > > > Dear MXNet community, > > > > > > > > > > > > > > > > > > I'd like to reopen the discussion on deprecating python2 > > > support. > > > > > > This > > > > > > > > > would help modernize the design and engineering practice in > > > MXNet > > > > > to > > > > > > > help > > > > > > > > > improve speed and quality. > > > > > > > > > > > > > > > > > > For this purpose, I reopened the issue on this here: > > > > > > > > > https://github.com/apache/incubator-mxnet/issues/8703 > > > > > > > > > > > > > > > > > > If the consensus is towards the direction of dropping > python2 > > > > > > support, > > > > > > > I > > > > > > > > > suggest we announce our plan to drop python2 support in the > > > next > > > > > > > release, > > > > > > > > > and actually drop the support in the next major version. > > > Thanks. > > > > > > > > > > > > > > > > > > -sz > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Yuxi(Darren) Hu, Ph.D. > > > Software Development Engineer > > > Amazon Web Services > > > >
Re: [Discuss] MXNet Python 2 Support Deprecation
+1 This would simplify CI, reduce costs and more. I think a followup question is what would be the mininum Python3 version supported? Depending on that we might be able to use type annotations for example or other features. Pedro. On Thu, Jul 18, 2019 at 12:07 PM Yuan Tang wrote: > > +1 > > On Thu, Jul 18, 2019 at 2:51 PM Yuxi Hu wrote: > > > +1 > > > > On Thu, Jul 18, 2019 at 11:31 AM Tong He wrote: > > > > > +1 > > > > > > Best regards, > > > > > > Tong He > > > > > > > > > Jake Lee 于2019年7月18日周四 上午11:29写道： > > > > > > > +1 > > > > > > > > On Thu, Jul 18, 2019 at 11:27 AM Junru Shao > > > > wrote: > > > > > > > > > +1 > > > > > > > > > > On Thu, Jul 18, 2019 at 11:12 AM Anirudh Acharya < > > > anirudhk...@gmail.com> > > > > > wrote: > > > > > > > > > > > +1 > > > > > > > > > > > > On Thu, Jul 18, 2019 at 11:03 AM Marco de Abreu < > > > > marco.g.ab...@gmail.com > > > > > > > > > > > > wrote: > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > -Marco > > > > > > > > > > > > > > Sheng Zha schrieb am Do., 18. Juli 2019, > > > > 19:59: > > > > > > > > > > > > > > > Dear MXNet community, > > > > > > > > > > > > > > > > I'd like to reopen the discussion on deprecating python2 > > support. > > > > > This > > > > > > > > would help modernize the design and engineering practice in > > MXNet > > > > to > > > > > > help > > > > > > > > improve speed and quality. > > > > > > > > > > > > > > > > For this purpose, I reopened the issue on this here: > > > > > > > > https://github.com/apache/incubator-mxnet/issues/8703 > > > > > > > > > > > > > > > > If the consensus is towards the direction of dropping python2 > > > > > support, > > > > > > I > > > > > > > > suggest we announce our plan to drop python2 support in the > > next > > > > > > release, > > > > > > > > and actually drop the support in the next major version. > > Thanks. > > > > > > > > > > > > > > > > -sz > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > Yuxi(Darren) Hu, Ph.D. > > Software Development Engineer > > Amazon Web Services > >
Re: [DISCUSS] MXNet 1.6.0 Roadmap
I think that's what the GitHub issue is for. The referenced issues can then automatically be tracked in a GitHub progress/kanban board. -Marco Pedro Larroy schrieb am Do., 18. Juli 2019, 21:32: > Are we using Jira or some other tool (Trello?) for planning? I think > getting more visibility on some of on the major ongoing activities > would help rally contributions around them. If they link to the design > document and group PRs in a single place (I think Jira or trello can > do that) it would help streamline the process and contributions. > > Pedro. > > On Thu, Jul 18, 2019 at 10:54 AM Sheng Zha wrote: > > > > Hi, > > > > While 1.5.0 vote on general@incubator is still on going, I’d like to > propose that we start planning for 1.6.0. To this end, I started a > discussion on the roadmap on GitHub > https://github.com/apache/incubator-mxnet/issues/15589. > > > > If no objection, we will conclude the discussion in two weeks (Aug 1st), > and start release plan by then. Thanks. > > > > -sz >
Re: [DISCUSS] MXNet 1.6.0 Roadmap
Are we using Jira or some other tool (Trello?) for planning? I think getting more visibility on some of on the major ongoing activities would help rally contributions around them. If they link to the design document and group PRs in a single place (I think Jira or trello can do that) it would help streamline the process and contributions. Pedro. On Thu, Jul 18, 2019 at 10:54 AM Sheng Zha wrote: > > Hi, > > While 1.5.0 vote on general@incubator is still on going, I’d like to propose > that we start planning for 1.6.0. To this end, I started a discussion on the > roadmap on GitHub https://github.com/apache/incubator-mxnet/issues/15589. > > If no objection, we will conclude the discussion in two weeks (Aug 1st), and > start release plan by then. Thanks. > > -sz
Re: demise of dmlc.ml domain & new Julia docs hosting
I'm not entirely sure about dropping docs for old versions to be honest. The root cause in my opinion is the fact that the build is wy to complicated. If it would have less dependencies and be more straight-forward, it should be a matter of seconds. The key here could be to separate the docs from the website. Doc generation should be a simple matter of "run doxygen" (or whatever we use). Right now, the website build process intermingles every aspect of it. If each version (and language) would just output a docs folder that has no outgoing references, they could be created entirely independent of another. Right now, we regenerate every version for every single build - that's not necessary. Considering how many people are unable to use the latest version of MXNet, I'd prefer if we provide the docs as long as the release binaries are available. -Marco Aaron Markham schrieb am Do., 18. Juli 2019, 21:20: > I'd have it check signatures. Ssl is optional I think. China users seem to > have issues with SSL... That may have changed, but I think we might have to > work around that for background downloads for models. > > With regard to the current links to dmlc.ml, I asked ivy to just get rid > of > them with # if necessary. Better to 404 than go to malware. This requires > going back into previous release branches and purging those references. > > The website is publishing regularly again. I had trouble getting Julia to > work in CI for generating the Julia docs, but I have it working now. > > As we move forward with yet another release, plus the potential launch of > the new Python docs site we need to consider reducing complexity of the > build and prune old versions. I think we should only host master or the > most recent release, and provide instructions on how to generate other > versions. Otherwise the transition will be too difficult and disruptive. > > On Tue, Jul 16, 2019, 16:41 Marco de Abreu > wrote: > > > While we are at it, we should maybe also take about SSL to avoid these > > kinds of downloads in future. > > > > -Marco > > > > Aaron Markham schrieb am Mi., 17. Juli 2019, > > 01:20: > > > > > Hi Hen, > > > We still have all of the these models that are referenced in this > > > issue: https://github.com/apache/incubator-mxnet/issues/15410 > > > I think it's a pretty big security breach to have systems that do > > > automatic downloading point to a malware site. Anything that fetches > > > binary data should be well secured and it really lowers trust if > > > assets send customers to malware sites. > > > There might be more. > > > > > > On Sat, Jul 13, 2019 at 1:00 PM Hen wrote: > > > > > > > > Nice work :) > > > > > > > > What other links does the project have that are outside Apache Infra > > > > control and have this risk? > > > > > > > > Outside of github.com/dmlc which is well known and iiuc in process > for > > > > resolving. > > > > > > > > Hen > > > > > > > > > > > > On Tue, Jul 9, 2019 at 4:46 PM Aaron Markham < > > aaron.s.mark...@gmail.com> > > > > wrote: > > > > > > > > > The PR has passed CI. Please take a look. > > > > > https://github.com/apache/incubator-mxnet/pull/15454 > > > > > We really need to get rid of those malware links, and this does > that, > > > > > restores the Julia docs with a local build, has CI coverage, and a > > new > > > > > Ubuntu guide (since I had to figure out how to use Julia and found > > our > > > > > docs for that were kind of broken). > > > > > Cheers, > > > > > Aaron > > > > > > > > > > On Thu, Jul 4, 2019 at 8:09 PM Iblis Lin > > wrote: > > > > > > > > > > > > Hi, > > > > > > > > > > > > I will add +1 to the micro-site approach. > > > > > > Since I have tried to take the generated MD outputs from > > > > > > Julia's doc system, but the syntax is incompatible with > > > > > > the MD plugin of Sphinx. > > > > > > > > > > > > Iblis Lin > > > > > > 林峻頤 > > > > > > > > > > > > On 7/4/19 12:12 PM, Aaron Markham wrote: > > > > > > > Hi dev@, > > > > > > > In case you missed the issues with the dmlc.ml domain, it was > > let > > > go > > > > > > > or sniped and now goes to a malware site. [1] Several assets > like > > > > > > > models and the Julia documentation were hosted there. > > > > > > > > > > > > > > I made some progress getting the Julia docs generated as part > of > > > the > > > > > > > regular website build flow. [2] It'll work as long as you have > > > Julia > > > > > > > installed and configured with MXNet. I don't imagine you can > use > > > it to > > > > > > > build the website natively on your mac or windows box at this > > point > > > > > > > because all of the CI and related instructions appear to be > only > > > for > > > > > > > Ubuntu. That being said, I added an option to dev_menu.py so > you > > > can > > > > > > > build the Julia docs with docker on whatever host you're on. > > > > > > > > > > > > > > I tried to bring in the markdown files and have the website > theme > > > > > > > applied to them. Many things were then broken
Re: warnings as errors
Hi. These two prs are fixing warnings on different platforms and removing some code bloat due to inlines. Could you guys help get them in? they are open for a while. https://github.com/apache/incubator-mxnet/pull/15270 https://github.com/apache/incubator-mxnet/pull/14940 Thanks. Pedro. On Wed, May 22, 2019 at 1:50 PM Pedro Larroy wrote: > > I was not able to fix the warnings on mshadow type switch with unused > local typedefs, that's one example of warning that I would disable. I > couldn't find a way to solve that one and I think the ramifications of > an unused typedef are not likely to cause bugs in the code and are > more of a pedantic nature. > > https://github.com/apache/incubator-mxnet/pull/13424 > > I think turning on them one by one is going to pollute the compilation > output unecesarily and even run into commandline length problems? I > think is best to enable all warnings and errors and cherry pick the > ones we can't fix or won't fix on purpose. > > In this other case, I managed to tighten the warnings but ASAN is > giving some problems: > > https://github.com/apache/incubator-mxnet/pull/14850 > > I think having warning fixes reviewed and merged faster without > triggering additional refactorings could make this process easier, > also having some help in this area and contributions would be greatly > appreciated. > > Pedro. > > On Tue, May 21, 2019 at 3:49 PM Sheng Zha wrote: > > > > It would be great to enforce the check for warnings and treat as errors. > > Some questions I have: > > - what are the warnings that you think should be ignored? > > - for the rest of the warning types, can we turn them on one by one? > > > > -sz > > > > On 2019/05/21 22:33:51, Pedro Larroy wrote: > > > Hi dev@ > > > > > > I try to fix any warning that I see during compilation of MXNet in my > > > platform and with the build toggles that I care about. These seemingly > > > trivial and ungrateful efforts, take nonetheless energy on the > > > contributor side. > > > > > > I think overall I submitted myself more than a dozen of PRs fixing > > > warnings and I would like to call for additional help and > > > contributions in this area. > > > > > > There was a question from Lin about discussing this on the mailing > > > list, I have the feeling that everybody agrees on moving towards zero > > > warnings and warnings as errors. I think there are unavoidable > > > warnings that can be disabled specifically such as the one triggered > > > by mshadow type switch. > > > > > > Some important missing warnings such as warning on missing return > > > values (ie. forgetting to return on a function returning non-void) > > > cause bugs, danger and additional time spent bugfixing, which can be > > > better spent somewhere else. > > > > > > Is there a process that we can figure out such as a more expedited > > > merges of PRs fixing warnings or a specific label? > > > > > > Some simple PRs that fixes a warning can take long to merge, and > > > sometimes trigger too much discussion and make the progress a bit > > > unfriendly to contributors. > > > > > > Any help or constructive ideas on this topic would be appreciated. > > > > > > Pedro. > > >
Re: demise of dmlc.ml domain & new Julia docs hosting
I'd have it check signatures. Ssl is optional I think. China users seem to have issues with SSL... That may have changed, but I think we might have to work around that for background downloads for models. With regard to the current links to dmlc.ml, I asked ivy to just get rid of them with # if necessary. Better to 404 than go to malware. This requires going back into previous release branches and purging those references. The website is publishing regularly again. I had trouble getting Julia to work in CI for generating the Julia docs, but I have it working now. As we move forward with yet another release, plus the potential launch of the new Python docs site we need to consider reducing complexity of the build and prune old versions. I think we should only host master or the most recent release, and provide instructions on how to generate other versions. Otherwise the transition will be too difficult and disruptive. On Tue, Jul 16, 2019, 16:41 Marco de Abreu wrote: > While we are at it, we should maybe also take about SSL to avoid these > kinds of downloads in future. > > -Marco > > Aaron Markham schrieb am Mi., 17. Juli 2019, > 01:20: > > > Hi Hen, > > We still have all of the these models that are referenced in this > > issue: https://github.com/apache/incubator-mxnet/issues/15410 > > I think it's a pretty big security breach to have systems that do > > automatic downloading point to a malware site. Anything that fetches > > binary data should be well secured and it really lowers trust if > > assets send customers to malware sites. > > There might be more. > > > > On Sat, Jul 13, 2019 at 1:00 PM Hen wrote: > > > > > > Nice work :) > > > > > > What other links does the project have that are outside Apache Infra > > > control and have this risk? > > > > > > Outside of github.com/dmlc which is well known and iiuc in process for > > > resolving. > > > > > > Hen > > > > > > > > > On Tue, Jul 9, 2019 at 4:46 PM Aaron Markham < > aaron.s.mark...@gmail.com> > > > wrote: > > > > > > > The PR has passed CI. Please take a look. > > > > https://github.com/apache/incubator-mxnet/pull/15454 > > > > We really need to get rid of those malware links, and this does that, > > > > restores the Julia docs with a local build, has CI coverage, and a > new > > > > Ubuntu guide (since I had to figure out how to use Julia and found > our > > > > docs for that were kind of broken). > > > > Cheers, > > > > Aaron > > > > > > > > On Thu, Jul 4, 2019 at 8:09 PM Iblis Lin > wrote: > > > > > > > > > > Hi, > > > > > > > > > > I will add +1 to the micro-site approach. > > > > > Since I have tried to take the generated MD outputs from > > > > > Julia's doc system, but the syntax is incompatible with > > > > > the MD plugin of Sphinx. > > > > > > > > > > Iblis Lin > > > > > 林峻頤 > > > > > > > > > > On 7/4/19 12:12 PM, Aaron Markham wrote: > > > > > > Hi dev@, > > > > > > In case you missed the issues with the dmlc.ml domain, it was > let > > go > > > > > > or sniped and now goes to a malware site. [1] Several assets like > > > > > > models and the Julia documentation were hosted there. > > > > > > > > > > > > I made some progress getting the Julia docs generated as part of > > the > > > > > > regular website build flow. [2] It'll work as long as you have > > Julia > > > > > > installed and configured with MXNet. I don't imagine you can use > > it to > > > > > > build the website natively on your mac or windows box at this > point > > > > > > because all of the CI and related instructions appear to be only > > for > > > > > > Ubuntu. That being said, I added an option to dev_menu.py so you > > can > > > > > > build the Julia docs with docker on whatever host you're on. > > > > > > > > > > > > I tried to bring in the markdown files and have the website theme > > > > > > applied to them. Many things were then broken - in large part due > > to > > > > > > some bugs in the website code related to post processing and > > injection > > > > > > of dom elements. This would require a rewrite of the Julia docs > to > > > > > > workaround the existing website bugs. Rather than do this, I just > > took > > > > > > the Julia site output, which has its own look and feel and nested > > in > > > > > > Julia's API directory. This is much like how the scala docs and > the > > > > > > java docs are - using their own look and feel as a micro-site. I > > feel > > > > > > that this is the better approach for now. > > > > > > > > > > > > The PR for the Julia docs is here: > > > > > > https://github.com/apache/incubator-mxnet/pull/15454 > > > > > > > > > > > > Ivy and I created several new issues to cover the broken links > that > > > > > > will need fixing. Models that need to be recovered or recreated > and > > > > > > uploaded to a new location. I have an s3 bucket that I've been > > using > > > > > > for some public assets like this, but I can't make progress on > > fixing > > > > > > those links when the models just don't exist. And I don't have >
Re: [Discuss] MXNet Python 2 Support Deprecation
+1 On Thu, Jul 18, 2019 at 2:51 PM Yuxi Hu wrote: > +1 > > On Thu, Jul 18, 2019 at 11:31 AM Tong He wrote: > > > +1 > > > > Best regards, > > > > Tong He > > > > > > Jake Lee 于2019年7月18日周四 上午11:29写道： > > > > > +1 > > > > > > On Thu, Jul 18, 2019 at 11:27 AM Junru Shao > > > wrote: > > > > > > > +1 > > > > > > > > On Thu, Jul 18, 2019 at 11:12 AM Anirudh Acharya < > > anirudhk...@gmail.com> > > > > wrote: > > > > > > > > > +1 > > > > > > > > > > On Thu, Jul 18, 2019 at 11:03 AM Marco de Abreu < > > > marco.g.ab...@gmail.com > > > > > > > > > > wrote: > > > > > > > > > > > +1 > > > > > > > > > > > > -Marco > > > > > > > > > > > > Sheng Zha schrieb am Do., 18. Juli 2019, > > > 19:59: > > > > > > > > > > > > > Dear MXNet community, > > > > > > > > > > > > > > I'd like to reopen the discussion on deprecating python2 > support. > > > > This > > > > > > > would help modernize the design and engineering practice in > MXNet > > > to > > > > > help > > > > > > > improve speed and quality. > > > > > > > > > > > > > > For this purpose, I reopened the issue on this here: > > > > > > > https://github.com/apache/incubator-mxnet/issues/8703 > > > > > > > > > > > > > > If the consensus is towards the direction of dropping python2 > > > > support, > > > > > I > > > > > > > suggest we announce our plan to drop python2 support in the > next > > > > > release, > > > > > > > and actually drop the support in the next major version. > Thanks. > > > > > > > > > > > > > > -sz > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > Yuxi(Darren) Hu, Ph.D. > Software Development Engineer > Amazon Web Services >
Re: [Discuss] MXNet Python 2 Support Deprecation
+1 On Thu, Jul 18, 2019 at 11:31 AM Tong He wrote: > +1 > > Best regards, > > Tong He > > > Jake Lee 于2019年7月18日周四 上午11:29写道： > > > +1 > > > > On Thu, Jul 18, 2019 at 11:27 AM Junru Shao > > wrote: > > > > > +1 > > > > > > On Thu, Jul 18, 2019 at 11:12 AM Anirudh Acharya < > anirudhk...@gmail.com> > > > wrote: > > > > > > > +1 > > > > > > > > On Thu, Jul 18, 2019 at 11:03 AM Marco de Abreu < > > marco.g.ab...@gmail.com > > > > > > > > wrote: > > > > > > > > > +1 > > > > > > > > > > -Marco > > > > > > > > > > Sheng Zha schrieb am Do., 18. Juli 2019, > > 19:59: > > > > > > > > > > > Dear MXNet community, > > > > > > > > > > > > I'd like to reopen the discussion on deprecating python2 support. > > > This > > > > > > would help modernize the design and engineering practice in MXNet > > to > > > > help > > > > > > improve speed and quality. > > > > > > > > > > > > For this purpose, I reopened the issue on this here: > > > > > > https://github.com/apache/incubator-mxnet/issues/8703 > > > > > > > > > > > > If the consensus is towards the direction of dropping python2 > > > support, > > > > I > > > > > > suggest we announce our plan to drop python2 support in the next > > > > release, > > > > > > and actually drop the support in the next major version. Thanks. > > > > > > > > > > > > -sz > > > > > > > > > > > > > > > > > > > > > -- Yuxi(Darren) Hu, Ph.D. Software Development Engineer Amazon Web Services
Re: [Discuss] MXNet Python 2 Support Deprecation
+1 Best regards, Tong He Jake Lee 于2019年7月18日周四 上午11:29写道： > +1 > > On Thu, Jul 18, 2019 at 11:27 AM Junru Shao > wrote: > > > +1 > > > > On Thu, Jul 18, 2019 at 11:12 AM Anirudh Acharya > > wrote: > > > > > +1 > > > > > > On Thu, Jul 18, 2019 at 11:03 AM Marco de Abreu < > marco.g.ab...@gmail.com > > > > > > wrote: > > > > > > > +1 > > > > > > > > -Marco > > > > > > > > Sheng Zha schrieb am Do., 18. Juli 2019, > 19:59: > > > > > > > > > Dear MXNet community, > > > > > > > > > > I'd like to reopen the discussion on deprecating python2 support. > > This > > > > > would help modernize the design and engineering practice in MXNet > to > > > help > > > > > improve speed and quality. > > > > > > > > > > For this purpose, I reopened the issue on this here: > > > > > https://github.com/apache/incubator-mxnet/issues/8703 > > > > > > > > > > If the consensus is towards the direction of dropping python2 > > support, > > > I > > > > > suggest we announce our plan to drop python2 support in the next > > > release, > > > > > and actually drop the support in the next major version. Thanks. > > > > > > > > > > -sz > > > > > > > > > > > > > > >
Re: [Discuss] MXNet Python 2 Support Deprecation
+1 On Thu, Jul 18, 2019 at 11:27 AM Junru Shao wrote: > +1 > > On Thu, Jul 18, 2019 at 11:12 AM Anirudh Acharya > wrote: > > > +1 > > > > On Thu, Jul 18, 2019 at 11:03 AM Marco de Abreu > > > wrote: > > > > > +1 > > > > > > -Marco > > > > > > Sheng Zha schrieb am Do., 18. Juli 2019, 19:59: > > > > > > > Dear MXNet community, > > > > > > > > I'd like to reopen the discussion on deprecating python2 support. > This > > > > would help modernize the design and engineering practice in MXNet to > > help > > > > improve speed and quality. > > > > > > > > For this purpose, I reopened the issue on this here: > > > > https://github.com/apache/incubator-mxnet/issues/8703 > > > > > > > > If the consensus is towards the direction of dropping python2 > support, > > I > > > > suggest we announce our plan to drop python2 support in the next > > release, > > > > and actually drop the support in the next major version. Thanks. > > > > > > > > -sz > > > > > > > > > >
Re: [Discuss] MXNet Python 2 Support Deprecation
+1 On Thu, Jul 18, 2019 at 11:12 AM Anirudh Acharya wrote: > +1 > > On Thu, Jul 18, 2019 at 11:03 AM Marco de Abreu > wrote: > > > +1 > > > > -Marco > > > > Sheng Zha schrieb am Do., 18. Juli 2019, 19:59: > > > > > Dear MXNet community, > > > > > > I'd like to reopen the discussion on deprecating python2 support. This > > > would help modernize the design and engineering practice in MXNet to > help > > > improve speed and quality. > > > > > > For this purpose, I reopened the issue on this here: > > > https://github.com/apache/incubator-mxnet/issues/8703 > > > > > > If the consensus is towards the direction of dropping python2 support, > I > > > suggest we announce our plan to drop python2 support in the next > release, > > > and actually drop the support in the next major version. Thanks. > > > > > > -sz > > > > > >
Re: [Discuss] MXNet Python 2 Support Deprecation
+1 On Thu, Jul 18, 2019 at 11:03 AM Marco de Abreu wrote: > +1 > > -Marco > > Sheng Zha schrieb am Do., 18. Juli 2019, 19:59: > > > Dear MXNet community, > > > > I'd like to reopen the discussion on deprecating python2 support. This > > would help modernize the design and engineering practice in MXNet to help > > improve speed and quality. > > > > For this purpose, I reopened the issue on this here: > > https://github.com/apache/incubator-mxnet/issues/8703 > > > > If the consensus is towards the direction of dropping python2 support, I > > suggest we announce our plan to drop python2 support in the next release, > > and actually drop the support in the next major version. Thanks. > > > > -sz > > >
Re: [Discuss] MXNet Python 2 Support Deprecation
+1 -Marco Sheng Zha schrieb am Do., 18. Juli 2019, 19:59: > Dear MXNet community, > > I'd like to reopen the discussion on deprecating python2 support. This > would help modernize the design and engineering practice in MXNet to help > improve speed and quality. > > For this purpose, I reopened the issue on this here: > https://github.com/apache/incubator-mxnet/issues/8703 > > If the consensus is towards the direction of dropping python2 support, I > suggest we announce our plan to drop python2 support in the next release, > and actually drop the support in the next major version. Thanks. > > -sz >
[Discuss] MXNet Python 2 Support Deprecation
Dear MXNet community, I'd like to reopen the discussion on deprecating python2 support. This would help modernize the design and engineering practice in MXNet to help improve speed and quality. For this purpose, I reopened the issue on this here: https://github.com/apache/incubator-mxnet/issues/8703 If the consensus is towards the direction of dropping python2 support, I suggest we announce our plan to drop python2 support in the next release, and actually drop the support in the next major version. Thanks. -sz
[DISCUSS] MXNet 1.6.0 Roadmap
Hi, While 1.5.0 vote on general@incubator is still on going, I’d like to propose that we start planning for 1.6.0. To this end, I started a discussion on the roadmap on GitHub https://github.com/apache/incubator-mxnet/issues/15589. If no objection, we will conclude the discussion in two weeks (Aug 1st), and start release plan by then. Thanks. -sz
Re: Slack Invitation
Invited. Welcome! On 2019/07/18 16:47:12, Kshitij Kalambarkar wrote: > >
