Re: [VOTE] Release MXNet version 1.3.0.RC0

[Steffen Rochel]

Thanks Sheng. With [1] I was able to build and test 1.3.0.rc0. Explanation
of version makes sense. Changing my vote to +1.
Roshani - please note, master still has version 1.3.0. This makes it
difficult to differentiate to rc0. Hope master version will be updated soon
as part of release process.

Thanks,
Steffen

On Sun, Sep 2, 2018 at 11:22 AM Joshua Z. Zhang 
wrote:

>
>
>
>
>
>
>
>
> Sheng, thanks for clarification. That make sense to me. I will change the
> vote to +1
>
>
> >
> > On Sep 2, 2018 at 9:43 AM,  mailto:zhash...@apache.org)>
> wrote:
> >
> >
> >
> >  Hi Steffen and Zhi,
> >
> > That's because those are not the artifacts being voted on. I just
> uploaded the actual release artifact to [1]. Unfortunately, even the
> lengthy release process doc [2] didn't capture this step...
> >
> > Steffen,
> >
> > In case you don't already know, regarding the version string, since we
> cannot change the code after the vote passes, the version never says it's a
> release candidate, only the file name does. None of the previous releases
> follow the convention you suggested. Please adjust your expectation and
> vote again. Feel free to download previous releases and verify:
> >
> > % tar -zxf apache-mxnet-src-1.2.1.rc1-incubating.tar.gz -O
> apache-mxnet-src-1.2.1.rc1-incubating/python/mxnet/libinfo.py | grep
> '__version__'
> > __version__ = "1.2.1"
> >
> > Zhi,
> >
> > We are not accepting new patches after the announced cutoff time. If you
> think this patch is optional and you see no other issue with this release,
> consider changing your vote. If you think the patch is critical, feel free
> to sustain your -1 vote until the end of this voting cycle.
> >
> > [1]
> https://github.com/apache/incubator-mxnet/releases/download/1.3.0.rc0/apache-mxnet-src-1.3.0.rc0-incubating.tar.gz
>
> > [2]
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=73630468
>
> >
> > -sz
> >
> > On 2018/09/01 22:08:48, "Joshua Z. Zhang"  
> wrote:
> > >  -1. Please include all 3rd party dependencies, GitHub won’t
> automatically do that.
> > >
> > >  BTW, Per user request in forum, I found this PR(
> https://github.com/apache/incubator-mxnet/pull/12118  <
> https://github.com/apache/incubator-mxnet/pull/12118>) is not included in
> 1.3 rc0, I recommend to cherry-pick into release to avoid potential
> problems.
> > >
> > >  Best,
> > >  Zhi
> > >   >  On Sep 1, 2018, at 2:27 PM, Steffen Rochel  <
> steffenroc...@gmail.com>  wrote:
> > >   >
> > >   >  -1
> > >   >
> > >   >  https://github.com/apache/incubator-mxnet/archive/1.3.0.rc0.zip
> and
> > >   >
> https://github.com/apache/incubator-mxnet/archive/1.3.0.rc0.tar.gz do
> not
> > >   >  contain 3rdparty packages, resulting in make failure:
> > >   >  tar zxf incubator-mxnet-1.3.0.rc0.tar.gz
> > >   >  cd incubator-mxnet-1.3.0.rc0/
> > >   >  make USE_OPENCV=1 USE_BLAS=openblas
> > >   >  Makefile:74:
> > >   >
> /home/steffen/Downloads/incubator-mxnet-1.3.0.rc0/3rdparty/mshadow/make/
> > >   >  mshadow.mk: No such file or directory
> > >   >  Makefile:75:
> > >   >
> /home/steffen/Downloads/incubator-mxnet-1.3.0.rc0/3rdparty/dmlc-core/make/
> > >   >  dmlc.mk: No such file or directory
> > >   >  Makefile:176: "USE_LAPACK disabled because libraries were not
> found"
> > >   >  Makefile:284: WARNING: Significant performance increases can be
> achieved by
> > >   >  installing and enabling gperftools or jemalloc development
> packages
> > >   >  Makefile:355:
> > >   >
> /home/steffen/Downloads/incubator-mxnet-1.3.0.rc0/3rdparty/ps-lite/make/
> > >   >  ps.mk: No such file or directory
> > >   >  make: *** No rule to make target
> > >   >
> '/home/steffen/Downloads/incubator-mxnet-1.3.0.rc0/3rdparty/ps-lite/make/
> > >   >  ps.mk'. Stop.
> > >   >
> > >   >  ~/Downloads/incubator-mxnet-1.3.0.rc0/3rdparty$ ls -al *
> > >   >  cub:
> > >   >  total 8
> > >   >  drwxr-xr-x 2 steffen steffen 4096 Aug 29 10:07 .
> > >   >  drwxr-xr-x 12 steffen steffen 4096 Aug 29 10:07 ..
> > >   >
> > >   >  dlpack:
> > >   >  total 8
> > >   >  drwxr-xr-x 2 steffen steffen 4096 Aug 29 10:07 .
> > >   >  drwxr-xr-x 12 steffen steffen 4096 Aug 29 10:07 ..
> > >   >
> > >   >  dmlc-core:
> > >   >  total 8
> > >   >  drwxr-xr-x 2 steffen steffen 4096 Aug 29 10:07 .
> > >   >  drwxr-xr-x 12 steffen steffen 4096 Aug 29 10:07 ..
> > >   >
> > >   >  Environment:
> > >   >  uname -a
> > >   >  Linux steffen 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15
> 16:00:05 UTC 2018
> > >   >  x86_64 x86_64 x86_64 GNU/L
> > >   >
> > >   >  Build from git succeeded:
> > >   >  git clone --recursive https://github.com/apache/incubator-mxnet
> --branch
> > >   >  1.3.0.rc0
> > >   >  cd incubator-mxnet/
> > >   >  git checkout 1.3.0.rc0
> > >   >  make USE_OPENCV=1 USE_BLAS=openblas
> > >   >  cd python/
> > >   >  sudo pip install -e .
> > >   >
> > >     import mxnet as mx
> > >     print(mx.__version__)
> > >   >  1.3.0
> > >   >
> > >   >  I was expecting version to be 1.3.0.rc0
> > >   >
> > >   

Re: Propose to discontinue supporting Apache MXNet on Windows 7

[Timur Shenkao]

>> I also believe that it is possible to install more recent >> versions of
Visual Studio on Windows 7.

It's about security reasons and AD permissions and bought licenses for VS,
not about general technical impossibility of installation of up-to-date
versions.

On Sunday, September 2, 2018, Marco de Abreu
 wrote:

> Thanks for the data and these quite important points. I agree and hereby
> change my vote to -1.
>
> Barber, Christopher  schrieb am So., 2.
> Sep.
> 2018, 18:56:
>
> > FWIW, my company is only beginning to transition to Windows 10 now, and
> my
> > past experience would lead me to believe that many enterprises stick with
> > old versions of Windows long past when you think they would.
> >
> > Seems to me that if you are unwilling to deprecate python 2.7, then
> > continuing to support Windows 7 is a no-brainer. You are more likely to
> get
> > users to switch to python 3 than you are to get them to install a new
> > operating system.
> >
> > And do you really want to drop support for platforms that your
> competitors
> > still support? Given MXNet's market share, I wouldn't dream of dropping a
> > platform until after the more popular frameworks have already done so.
> >
> > I also believe that it is possible to install more recent versions of
> > Visual Studio on Windows 7.
> >
> > On 9/2/18, 1:57 AM, "kellen sunderland" 
> > wrote:
> >
> > Google analytics are sadly probably the best numbers we're going to
> > get.
> > Of course these numbers are likely to over-represent windows usage,
> as
> > I'm
> > sure many people are looking up documentation on a windows machine
> > while
> > ssh'd into a cloud instance or IoT device.
> >
> > What's the trend over time for these numbers Mu?  Is Windows 7 usage
> > relatively stable over the last year?
> >
> > On Sun, Sep 2, 2018 at 1:58 AM Mu Li  wrote:
> >
> > > According to google analytics, ~12% users who visited mxnet's
> > website are
> > > using Windows 7. It's a significant number. Even though we cannot
> > conclude
> > > that all of these users will run MXNet on Windows 7, I suggest we
> > still
> > > support win7.
> > >
> > > BTW, anyone who can access mxnet's google analytics report can
> > verify this
> > > number by following this instruction:
> > >
> > >
> > https://stackoverflow.com/questions/1340778/detecting-
> windows-7-with-google-analytics
> > >
> > >
> > >
> > > On Sat, Sep 1, 2018 at 1:55 PM Steffen Rochel <
> > steffenroc...@gmail.com>
> > > wrote:
> > >
> > > > I support a data driven decision. Any suggestions how we can
> obtain
> > > insight
> > > > about OS usage of the MXNet user community?
> > > > Can we get such information from pip install statistics or should
> > we
> > > > perform a user poll on the discussion forum?
> > > > On the other hand the lack of data should not prevent us from
> > moving
> > > > forward and dropping support for outdated OS.
> > > > In any case we would have to announce dropping a platform support
> > at
> > > least
> > > > a release in advance.
> > > > Steffen
> > > >
> > > > On Thu, Aug 30, 2018 at 12:21 PM Sheng Zha 
> > wrote:
> > > >
> > > > > Hi Kellen,
> > > > >
> > > > > Thanks for the explanation. Unfortunately, I don't have the
> > usage data,
> > > > so
> > > > > I refrained from voting. If any of the voters have such data
> I'd
> > love
> > > to
> > > > > see it too.
> > > > >
> > > > > -sz
> > > > >
> > > > > On 2018/08/30 14:58:09, kellen sunderland <
> > kellen.sunderl...@gmail.com
> > > >
> > > > > wrote:
> > > > > > I haven't spoken to anyone about the decision (as I'm
> > currently on an
> > > > > > island in the med) but to me the quick +1s are likely a
> result
> > of
> > > this
> > > > > > being a fairly straightforward decision.  The factors that
> > went into
> > > my
> > > > > > thinking were (1) prioritizing growing platforms rather than
> > > shrinking
> > > > > > platforms (i.e. thinking long term rather than shirt term)
> and
> > (2)
> > > > > earning
> > > > > > our customers' trust.  Claiming support for a platform when
> we
> > can't
> > > > > > realistically deliver it would lose us trust.  I'd prefer to
> > over
> > > > deliver
> > > > > > and under promise when it come to windows 7 for this reason.
> > > > > >
> > > > > > Now on the flip side one thing I would see as valuable is to
> > try and
> > > > get
> > > > > > windows builds working with clang.  This could be beneficial
> > in the
> > > > sense
> > > > > > that it would be easy to maintain for mxnet devs and allow us
> > to use
> > > > > modern
> > > > > > cpp on older windows machines without using vs 2013(which I
> > consider
> > > a
> > > > > > non-starter with our codebase).
> > > > > >
> > > > > > You have 

Re: [VOTE] Release MXNet version 1.3.0.RC0

[Joshua Z. Zhang]

  
  

  
  

  
  
Sheng, thanks for clarification. That make sense to me. I will change the vote 
to +1
  
  
>   
> On Sep 2, 2018 at 9:43 AM,  mailto:zhash...@apache.org)>  wrote:
>   
>   
>   
>  Hi Steffen and Zhi,  
>
> That's because those are not the artifacts being voted on. I just uploaded 
> the actual release artifact to [1]. Unfortunately, even the lengthy release 
> process doc [2] didn't capture this step...  
>
> Steffen,  
>
> In case you don't already know, regarding the version string, since we cannot 
> change the code after the vote passes, the version never says it's a release 
> candidate, only the file name does. None of the previous releases follow the 
> convention you suggested. Please adjust your expectation and vote again. Feel 
> free to download previous releases and verify:  
>
> % tar -zxf apache-mxnet-src-1.2.1.rc1-incubating.tar.gz -O 
> apache-mxnet-src-1.2.1.rc1-incubating/python/mxnet/libinfo.py | grep 
> '__version__'  
> __version__ = "1.2.1"  
>
> Zhi,  
>
> We are not accepting new patches after the announced cutoff time. If you 
> think this patch is optional and you see no other issue with this release, 
> consider changing your vote. If you think the patch is critical, feel free to 
> sustain your -1 vote until the end of this voting cycle.  
>
> [1] 
> https://github.com/apache/incubator-mxnet/releases/download/1.3.0.rc0/apache-mxnet-src-1.3.0.rc0-incubating.tar.gz
>   
> [2] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=73630468 
>  
>
> -sz  
>
> On 2018/09/01 22:08:48, "Joshua Z. Zhang"wrote:  
> >  -1. Please include all 3rd party dependencies, GitHub won’t automatically 
> > do that.  
> >   
> >  BTW, Per user request in forum, I found this 
> > PR(https://github.com/apache/incubator-mxnet/pull/12118  
> > ) is not included in 
> > 1.3 rc0, I recommend to cherry-pick into release to avoid potential 
> > problems.  
> >   
> >  Best,  
> >  Zhi  
> >   >  On Sep 1, 2018, at 2:27 PM, Steffen Rochel
> > wrote:  
> >   >   
> >   >  -1  
> >   >   
> >   >  https://github.com/apache/incubator-mxnet/archive/1.3.0.rc0.zip and  
> >   >  https://github.com/apache/incubator-mxnet/archive/1.3.0.rc0.tar.gz do 
> > not  
> >   >  contain 3rdparty packages, resulting in make failure:  
> >   >  tar zxf incubator-mxnet-1.3.0.rc0.tar.gz  
> >   >  cd incubator-mxnet-1.3.0.rc0/  
> >   >  make USE_OPENCV=1 USE_BLAS=openblas  
> >   >  Makefile:74:  
> >   >  
> > /home/steffen/Downloads/incubator-mxnet-1.3.0.rc0/3rdparty/mshadow/make/  
> >   >  mshadow.mk: No such file or directory  
> >   >  Makefile:75:  
> >   >  
> > /home/steffen/Downloads/incubator-mxnet-1.3.0.rc0/3rdparty/dmlc-core/make/  
> >   >  dmlc.mk: No such file or directory  
> >   >  Makefile:176: "USE_LAPACK disabled because libraries were not found"  
> >   >  Makefile:284: WARNING: Significant performance increases can be 
> > achieved by  
> >   >  installing and enabling gperftools or jemalloc development packages  
> >   >  Makefile:355:  
> >   >  
> > /home/steffen/Downloads/incubator-mxnet-1.3.0.rc0/3rdparty/ps-lite/make/  
> >   >  ps.mk: No such file or directory  
> >   >  make: *** No rule to make target  
> >   >  
> > '/home/steffen/Downloads/incubator-mxnet-1.3.0.rc0/3rdparty/ps-lite/make/  
> >   >  ps.mk'. Stop.  
> >   >   
> >   >  ~/Downloads/incubator-mxnet-1.3.0.rc0/3rdparty$ ls -al *  
> >   >  cub:  
> >   >  total 8  
> >   >  drwxr-xr-x 2 steffen steffen 4096 Aug 29 10:07 .  
> >   >  drwxr-xr-x 12 steffen steffen 4096 Aug 29 10:07 ..  
> >   >   
> >   >  dlpack:  
> >   >  total 8  
> >   >  drwxr-xr-x 2 steffen steffen 4096 Aug 29 10:07 .  
> >   >  drwxr-xr-x 12 steffen steffen 4096 Aug 29 10:07 ..  
> >   >   
> >   >  dmlc-core:  
> >   >  total 8  
> >   >  drwxr-xr-x 2 steffen steffen 4096 Aug 29 10:07 .  
> >   >  drwxr-xr-x 12 steffen steffen 4096 Aug 29 10:07 ..  
> >   >   
> >   >  Environment:  
> >   >  uname -a  
> >   >  Linux steffen 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 
> > 2018  
> >   >  x86_64 x86_64 x86_64 GNU/L  
> >   >   
> >   >  Build from git succeeded:  
> >   >  git clone --recursive https://github.com/apache/incubator-mxnet 
> > --branch  
> >   >  1.3.0.rc0  
> >   >  cd incubator-mxnet/  
> >   >  git checkout 1.3.0.rc0  
> >   >  make USE_OPENCV=1 USE_BLAS=openblas  
> >   >  cd python/  
> >   >  sudo pip install -e .  
> >   >   
> >     import mxnet as mx  
> >     print(mx.__version__)  
> >   >  1.3.0  
> >   >   
> >   >  I was expecting version to be 1.3.0.rc0  
> >   >   
> >   >  Steffen  
> >   >   
> >   >   
> >   >   
> >   >  On Sat, Sep 1, 2018 at 3:22 AM Pigeon Lucky
> > wrote:  
> >   >   
> >   >>  +1  
> >   >>   
> >   >>  On Sat, 1 Sep 2018, 10:59 Roshani Nagmote,  
> >
> >   >>  wrote:  
> >   >>   
> >   >>>  Hi all,  
> >   >>>   
> >   >>>  I would like to propose a vote to release Apache MXNet 

Re: Propose to discontinue supporting Apache MXNet on Windows 7

[Marco de Abreu]

Thanks for the data and these quite important points. I agree and hereby
change my vote to -1.

Barber, Christopher  schrieb am So., 2. Sep.
2018, 18:56:

> FWIW, my company is only beginning to transition to Windows 10 now, and my
> past experience would lead me to believe that many enterprises stick with
> old versions of Windows long past when you think they would.
>
> Seems to me that if you are unwilling to deprecate python 2.7, then
> continuing to support Windows 7 is a no-brainer. You are more likely to get
> users to switch to python 3 than you are to get them to install a new
> operating system.
>
> And do you really want to drop support for platforms that your competitors
> still support? Given MXNet's market share, I wouldn't dream of dropping a
> platform until after the more popular frameworks have already done so.
>
> I also believe that it is possible to install more recent versions of
> Visual Studio on Windows 7.
>
> On 9/2/18, 1:57 AM, "kellen sunderland" 
> wrote:
>
> Google analytics are sadly probably the best numbers we're going to
> get.
> Of course these numbers are likely to over-represent windows usage, as
> I'm
> sure many people are looking up documentation on a windows machine
> while
> ssh'd into a cloud instance or IoT device.
>
> What's the trend over time for these numbers Mu?  Is Windows 7 usage
> relatively stable over the last year?
>
> On Sun, Sep 2, 2018 at 1:58 AM Mu Li  wrote:
>
> > According to google analytics, ~12% users who visited mxnet's
> website are
> > using Windows 7. It's a significant number. Even though we cannot
> conclude
> > that all of these users will run MXNet on Windows 7, I suggest we
> still
> > support win7.
> >
> > BTW, anyone who can access mxnet's google analytics report can
> verify this
> > number by following this instruction:
> >
> >
> https://stackoverflow.com/questions/1340778/detecting-windows-7-with-google-analytics
> >
> >
> >
> > On Sat, Sep 1, 2018 at 1:55 PM Steffen Rochel <
> steffenroc...@gmail.com>
> > wrote:
> >
> > > I support a data driven decision. Any suggestions how we can obtain
> > insight
> > > about OS usage of the MXNet user community?
> > > Can we get such information from pip install statistics or should
> we
> > > perform a user poll on the discussion forum?
> > > On the other hand the lack of data should not prevent us from
> moving
> > > forward and dropping support for outdated OS.
> > > In any case we would have to announce dropping a platform support
> at
> > least
> > > a release in advance.
> > > Steffen
> > >
> > > On Thu, Aug 30, 2018 at 12:21 PM Sheng Zha 
> wrote:
> > >
> > > > Hi Kellen,
> > > >
> > > > Thanks for the explanation. Unfortunately, I don't have the
> usage data,
> > > so
> > > > I refrained from voting. If any of the voters have such data I'd
> love
> > to
> > > > see it too.
> > > >
> > > > -sz
> > > >
> > > > On 2018/08/30 14:58:09, kellen sunderland <
> kellen.sunderl...@gmail.com
> > >
> > > > wrote:
> > > > > I haven't spoken to anyone about the decision (as I'm
> currently on an
> > > > > island in the med) but to me the quick +1s are likely a result
> of
> > this
> > > > > being a fairly straightforward decision.  The factors that
> went into
> > my
> > > > > thinking were (1) prioritizing growing platforms rather than
> > shrinking
> > > > > platforms (i.e. thinking long term rather than shirt term) and
> (2)
> > > > earning
> > > > > our customers' trust.  Claiming support for a platform when we
> can't
> > > > > realistically deliver it would lose us trust.  I'd prefer to
> over
> > > deliver
> > > > > and under promise when it come to windows 7 for this reason.
> > > > >
> > > > > Now on the flip side one thing I would see as valuable is to
> try and
> > > get
> > > > > windows builds working with clang.  This could be beneficial
> in the
> > > sense
> > > > > that it would be easy to maintain for mxnet devs and allow us
> to use
> > > > modern
> > > > > cpp on older windows machines without using vs 2013(which I
> consider
> > a
> > > > > non-starter with our codebase).
> > > > >
> > > > > You have peaked my curiousity though Sheng.  How many win7
> users does
> > > > MXNet
> > > > > have relative to macos/Linux?
> > > > >
> > > > > On Thu, Aug 30, 2018, 8:51 AM Sheng Zha 
> wrote:
> > > > >
> > > > > > Hi Yuan,
> > > > > >
> > > > > > No problem. This is an issue that's worth having a clear
> > definition,
> > > so
> > > > > > there's nothing wrong about your proposal, and thanks for
> bringing
> > > > this up.
> > > > > >
> > > > > > I'm more concerned about the seemingly unanimous votes on
> dropping
> > > > support
>

Re: Propose to discontinue supporting Apache MXNet on Windows 7

[Barber, Christopher]

FWIW, my company is only beginning to transition to Windows 10 now, and my past 
experience would lead me to believe that many enterprises stick with old 
versions of Windows long past when you think they would.

Seems to me that if you are unwilling to deprecate python 2.7, then continuing 
to support Windows 7 is a no-brainer. You are more likely to get users to 
switch to python 3 than you are to get them to install a new operating system.

And do you really want to drop support for platforms that your competitors 
still support? Given MXNet's market share, I wouldn't dream of dropping a 
platform until after the more popular frameworks have already done so.

I also believe that it is possible to install more recent versions of Visual 
Studio on Windows 7. 

On 9/2/18, 1:57 AM, "kellen sunderland"  wrote:

Google analytics are sadly probably the best numbers we're going to get.
Of course these numbers are likely to over-represent windows usage, as I'm
sure many people are looking up documentation on a windows machine while
ssh'd into a cloud instance or IoT device.

What's the trend over time for these numbers Mu?  Is Windows 7 usage
relatively stable over the last year?

On Sun, Sep 2, 2018 at 1:58 AM Mu Li  wrote:

> According to google analytics, ~12% users who visited mxnet's website are
> using Windows 7. It's a significant number. Even though we cannot conclude
> that all of these users will run MXNet on Windows 7, I suggest we still
> support win7.
>
> BTW, anyone who can access mxnet's google analytics report can verify this
> number by following this instruction:
>
> 
https://stackoverflow.com/questions/1340778/detecting-windows-7-with-google-analytics
>
>
>
> On Sat, Sep 1, 2018 at 1:55 PM Steffen Rochel 
> wrote:
>
> > I support a data driven decision. Any suggestions how we can obtain
> insight
> > about OS usage of the MXNet user community?
> > Can we get such information from pip install statistics or should we
> > perform a user poll on the discussion forum?
> > On the other hand the lack of data should not prevent us from moving
> > forward and dropping support for outdated OS.
> > In any case we would have to announce dropping a platform support at
> least
> > a release in advance.
> > Steffen
> >
> > On Thu, Aug 30, 2018 at 12:21 PM Sheng Zha  wrote:
> >
> > > Hi Kellen,
> > >
> > > Thanks for the explanation. Unfortunately, I don't have the usage 
data,
> > so
> > > I refrained from voting. If any of the voters have such data I'd love
> to
> > > see it too.
> > >
> > > -sz
> > >
> > > On 2018/08/30 14:58:09, kellen sunderland  >
> > > wrote:
> > > > I haven't spoken to anyone about the decision (as I'm currently on 
an
> > > > island in the med) but to me the quick +1s are likely a result of
> this
> > > > being a fairly straightforward decision.  The factors that went into
> my
> > > > thinking were (1) prioritizing growing platforms rather than
> shrinking
> > > > platforms (i.e. thinking long term rather than shirt term) and (2)
> > > earning
> > > > our customers' trust.  Claiming support for a platform when we can't
> > > > realistically deliver it would lose us trust.  I'd prefer to over
> > deliver
> > > > and under promise when it come to windows 7 for this reason.
> > > >
> > > > Now on the flip side one thing I would see as valuable is to try and
> > get
> > > > windows builds working with clang.  This could be beneficial in the
> > sense
> > > > that it would be easy to maintain for mxnet devs and allow us to use
> > > modern
> > > > cpp on older windows machines without using vs 2013(which I consider
> a
> > > > non-starter with our codebase).
> > > >
> > > > You have peaked my curiousity though Sheng.  How many win7 users 
does
> > > MXNet
> > > > have relative to macos/Linux?
> > > >
> > > > On Thu, Aug 30, 2018, 8:51 AM Sheng Zha  wrote:
> > > >
> > > > > Hi Yuan,
> > > > >
> > > > > No problem. This is an issue that's worth having a clear
> definition,
> > so
> > > > > there's nothing wrong about your proposal, and thanks for bringing
> > > this up.
> > > > >
> > > > > I'm more concerned about the seemingly unanimous votes on dropping
> > > support
> > > > > on a platform without seeing the supporting evidence that it's the
> > > right
> > > > > thing. It is as if everyone who participated in the vote are
> already
> > > on the
> > > > > same page, and somehow I'm the only one that's not. But the only
> > > argument I
> > > > > hear so far is that it's technically not straightforward to
> continue
> > > the
> > > > > support, which, coming from Amazon folks, 

Re: [VOTE] Release MXNet version 1.3.0.RC0

[Sheng Zha]

Hi Steffen and Zhi,

That's because those are not the artifacts being voted on. I just uploaded the 
actual release artifact to [1]. Unfortunately, even the lengthy release process 
doc [2] didn't capture this step...

Steffen,

In case you don't already know, regarding the version string, since we cannot 
change the code after the vote passes, the version never says it's a release 
candidate, only the file name does. None of the previous releases follow the 
convention you suggested. Please adjust your expectation and vote again. Feel 
free to download previous releases and verify:

% tar -zxf apache-mxnet-src-1.2.1.rc1-incubating.tar.gz -O 
apache-mxnet-src-1.2.1.rc1-incubating/python/mxnet/libinfo.py | grep 
'__version__'
__version__ = "1.2.1"

Zhi,

We are not accepting new patches after the announced cutoff time. If you think 
this patch is optional and you see no other issue with this release, consider 
changing your vote. If you think the patch is critical, feel free to sustain 
your -1 vote until the end of this voting cycle.

[1] 
https://github.com/apache/incubator-mxnet/releases/download/1.3.0.rc0/apache-mxnet-src-1.3.0.rc0-incubating.tar.gz
[2] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=73630468

-sz

On 2018/09/01 22:08:48, "Joshua Z. Zhang"  wrote: 
> -1. Please include all 3rd party dependencies, GitHub won’t automatically do 
> that. 
> 
> BTW, Per user request in forum, I found this 
> PR(https://github.com/apache/incubator-mxnet/pull/12118 
> ) is not included in 
> 1.3 rc0, I recommend to cherry-pick into release to avoid potential problems. 
> 
> Best,
> Zhi
> > On Sep 1, 2018, at 2:27 PM, Steffen Rochel  wrote:
> > 
> > -1
> > 
> > https://github.com/apache/incubator-mxnet/archive/1.3.0.rc0.zip and
> > https://github.com/apache/incubator-mxnet/archive/1.3.0.rc0.tar.gz do not
> > contain 3rdparty packages, resulting in make failure:
> > tar zxf incubator-mxnet-1.3.0.rc0.tar.gz
> > cd incubator-mxnet-1.3.0.rc0/
> > make USE_OPENCV=1 USE_BLAS=openblas
> > Makefile:74:
> > /home/steffen/Downloads/incubator-mxnet-1.3.0.rc0/3rdparty/mshadow/make/
> > mshadow.mk: No such file or directory
> > Makefile:75:
> > /home/steffen/Downloads/incubator-mxnet-1.3.0.rc0/3rdparty/dmlc-core/make/
> > dmlc.mk: No such file or directory
> > Makefile:176: "USE_LAPACK disabled because libraries were not found"
> > Makefile:284: WARNING: Significant performance increases can be achieved by
> > installing and enabling gperftools or jemalloc development packages
> > Makefile:355:
> > /home/steffen/Downloads/incubator-mxnet-1.3.0.rc0/3rdparty/ps-lite/make/
> > ps.mk: No such file or directory
> > make: *** No rule to make target
> > '/home/steffen/Downloads/incubator-mxnet-1.3.0.rc0/3rdparty/ps-lite/make/
> > ps.mk'.  Stop.
> > 
> > ~/Downloads/incubator-mxnet-1.3.0.rc0/3rdparty$ ls -al *
> > cub:
> > total 8
> > drwxr-xr-x  2 steffen steffen 4096 Aug 29 10:07 .
> > drwxr-xr-x 12 steffen steffen 4096 Aug 29 10:07 ..
> > 
> > dlpack:
> > total 8
> > drwxr-xr-x  2 steffen steffen 4096 Aug 29 10:07 .
> > drwxr-xr-x 12 steffen steffen 4096 Aug 29 10:07 ..
> > 
> > dmlc-core:
> > total 8
> > drwxr-xr-x  2 steffen steffen 4096 Aug 29 10:07 .
> > drwxr-xr-x 12 steffen steffen 4096 Aug 29 10:07 ..
> > 
> > Environment:
> > uname -a
> > Linux steffen 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018
> > x86_64 x86_64 x86_64 GNU/L
> > 
> > Build from git succeeded:
> > git clone --recursive https://github.com/apache/incubator-mxnet --branch
> > 1.3.0.rc0
> > cd incubator-mxnet/
> > git checkout 1.3.0.rc0
> > make USE_OPENCV=1 USE_BLAS=openblas
> > cd python/
> > sudo pip install -e .
> > 
>  import mxnet as mx
>  print(mx.__version__)
> > 1.3.0
> > 
> > I was expecting version to be 1.3.0.rc0
> > 
> > Steffen
> > 
> > 
> > 
> > On Sat, Sep 1, 2018 at 3:22 AM Pigeon Lucky  wrote:
> > 
> >> +1
> >> 
> >> On Sat, 1 Sep 2018, 10:59 Roshani Nagmote, 
> >> wrote:
> >> 
> >>> Hi all,
> >>> 
> >>> I would like to propose a vote to release Apache MXNet (incubating)
> >> version
> >>> 1.3.0.RC0. Voting will start now (Friday, Aug 31st) and end at 7:00 PM
> >>> PDT, Wednesday, Sept 5th.
> >>> 
> >>> Link to release notes:
> >>> https://github.com/apache/incubator-mxnet/releases
> >>> 
> >>> Link to release candidate 1.3.0.rc0:
> >>> *https://github.com/apache/incubator-mxnet/releases/tag/1.3.0.rc
> >>> 0*
> >>> 
> >>> View this page, click on "Build from Source", and use the source code
> >>> obtained from 1.3.0.rc0 tag:
> >>> https://mxnet.incubator.apache.org/install/index.html
> >>> 
> >>> Please remember to TEST first before voting accordingly:
> >>> 
> >>> +1 = approve
> >>> +0 = no opinion
> >>> -1 = disapprove (provide reason)
> >>> 
> >>> Thanks,
> >>> Roshani
> >>> 
> >> 
> 
> 

Re: Propose to discontinue supporting Apache MXNet on Windows 7

[Jim Jagielski]

IMO, either major or minor is fine, not just patch ;)

> On Aug 30, 2018, at 2:34 AM, Lv, Tao A  wrote:
> 
> If we really want to discontinue the support on Win7, maybe it should happen 
> in a major release like 2.0.0.
> 
> 
> -Original Message-
> From: dev-return-4003-tao.a.lv=intel@mxnet.incubator.apache.org 
> [mailto:dev-return-4003-tao.a.lv=intel@mxnet.incubator.apache.org] 
> Sent: Thursday, August 30, 2018 2:21 PM
> To: dev@mxnet.incubator.apache.org
> Subject: Re: Propose to discontinue supporting Apache MXNet on Windows 7
> 
> Hi Hagay,
> 
> To minimize the impact to existing customers, I suggest we support MXNe 1.3 
> installation on Windows but defer all the bug fix to Windows 10 version and 
> ask users to migrate. Then we officially discontinue the support on Windows
> 7 in the 1.4 release.
> 
> Thanks,
> 
> Lin
> 
> On Wed, Aug 29, 2018 at 1:29 PM Hagay Lupesko  wrote:
> 
>> +1 (non-binding)
>> Thanks for raising this Lin!
>> Are you suggesting to do it as part of MXNet 1.3?
>> 
>> On Wed, Aug 29, 2018 at 9:14 AM Srivastava, Rohit Kumar < 
>> srivastava@buckeyemail.osu.edu> wrote:
>> 
>>> +1
>>> 
>>> On 8/29/18, 8:39 AM, "sandeep krishnamurthy" <
>> sandeep.krishn...@gmail.com>
>>> wrote:
>>> 
>>>+1 Thanks for bringing this up.
>>> 
>>>On Wed, Aug 29, 2018 at 6:38 AM Marco de Abreu
>>> wrote:
>>> 
 +1
 
 On Wed, Aug 29, 2018 at 1:08 PM kellen sunderland <
 kellen.sunderl...@gmail.com> wrote:
 
> +1 (non-binding)
> 
> On Wed, Aug 29, 2018, 1:18 AM Anirudh Acharya < 
>>> anirudhk...@gmail.com>
> wrote:
> 
>> +1 for discontinuing.
>> 
>> On Tue, Aug 28, 2018 at 4:11 PM Naveen Swamy <
>> mnnav...@gmail.com
 
 wrote:
>> 
>>> +1 to stop supporting Win7
>>> 
>>> On Tue, Aug 28, 2018 at 3:54 PM Lin Yuan <
>> apefor...@gmail.com>
 wrote:
>>> 
 Dear Community,
 
 
 
 Currently, our MXNet installation guide for Windows 
>>> does
>> not
>>> work
 for
 Windows 7. e.g. Microsoft Visual Studio 2015 is not 
>>> supported on
>> Windows
>>> 7
 <
 
>>> 
>> 
> 
 
>>> 
>> https://visualstudio.microsoft.com/vs/support/vs2015/received-error-sp
>> ecified-program-requires-newer-version-windows/
> .
 In addition, MSFT ended “Mainstream” support for 
>>> Windows 7 in 2015
 (
 
>>> 
>> 
> 
 
>>> 
>> https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-
>> sheet
 ).
 Therefore, it is not possible for developers to build 
>>> MXNet and
> verify
>>> the
 fix on Windows 7 platform. Given that there have been
>> several
 issues
>>> about
 MXNet error on Windows 7 (issue#9271
 
>>> ,
>>> issue
 #8921
 
>>> ,
>>> issue
> #11163
 
>>> ),
>>> it will
>> even
 add
 more burden on developers in the future if we were to 
>>> continue
>> supporting
 Windows 7.
 
 
 
 I therefore would like to propose that we discontinue 
>>> the support
 of
>>> MXNet
 on Windows 7 in the next release.
 
 
 Specifically, this means the following required actions:
 
 1) state the discontinuation of Windows 7 support in 
>>> the release
 note
 
 2) update the MXNet webpage if Windows version is
>> mentioned.
 
 3) update the open Github issues related to Windows 7
 
 
 Please share your thoughts about this proposal and/or 
>>> suggest if
> there
>> is
 any other missing action item from the above.
 
 
 Best Regards,
 
 
 Lin
 
>>> 
>> 
> 
 
>>> 
>>> 
>>>--
>>>Sandeep Krishnamurthy
>>> 
>>> 
>>> 
>> 

Re: Propose to discontinue supporting Apache MXNet on Windows 7

[Timur Shenkao]

Hello guys,

In banks, fintech and other financial companies, governmental
organizations, people still "use" windows 7 as they have no choice of os.
Unfortunately they often don't have opportunity to  install C/C++ compiler,
visual studio as well.
They cannot build mxnet, install specific C/ C++ libraries.
So, their only rescue is to "conda install mxnet" if conda package contains
all C/C++ dependencies or use Wheel files from this repository:
https://www.lfd.uci.edu/~gohlke/pythonlibs/

Yes, eventually their work / code is moved into dev / qa / prod Linux
clusters but they have to "play" on their local machines first.

In case of MXNet is "installable" but not "importable": conda installation
of this package
https://anaconda.org/anaconda/mxnet/1.2.1/download/win-64/mxnet-1.2.1-h8cc8929_0.tar.bz2
is successful but import fails.



Yours sincerely, Timur