nks!
> -Ciyong
>
> -Original Message-
> From: Zhao, Patric
> Sent: Monday, November 18, 2019 2:10 PM
> To: dev@mxnet.incubator.apache.org; d...@mxnet.apache.org
> Subject: RE: RE: MXNet 1.6.0 release
>
> Plan to cherry-pick below PR into 1.6. Please take a
PM
To: dev@mxnet.incubator.apache.org; d...@mxnet.apache.org
Subject: RE: RE: MXNet 1.6.0 release
Plan to cherry-pick below PR into 1.6. Please take a review.
https://github.com/apache/incubator-mxnet/pull/16837
> -Original Message-
> From: Tan, Jonathan
> Sent: Monday, November 18
Plan to cherry-pick below PR into 1.6. Please take a review.
https://github.com/apache/incubator-mxnet/pull/16837
> -Original Message-
> From: Tan, Jonathan
> Sent: Monday, November 18, 2019 9:43 AM
> To: d...@mxnet.apache.org
> Subject: Re: RE: MXNet 1.6.0 releas
; > From: Chaitanya Bapat mailto:ch...@gmail.com>>>
>
> > Sent: Friday, November 8, 2019 2:19 PM>
>
> > To: dev@mxnet.incubator.apache.org<mailto:dev@mxnet.incubator.apache.org>>
>
> > Cc: d...@mxnet.apache.org<mailto:d...@mxnet.apache.org>
below PR need to be backported to 1.6 for bugfix in large
> > tensor supports.
> > https://github.com/apache/incubator-mxnet/pull/16737
> >
> > --Patric
> >
> >
> > > -Original Message-
> > > From: Przemysław Trędak
> > > Sent: Fr
37
>
> --Patric
>
>
> > -Original Message-
> > From: Przemysław Trędak
> > Sent: Friday, November 8, 2019 5:46 AM
> > To: d...@mxnet.apache.org
> > Subject: Re: MXNet 1.6.0 release
> >
> > Dear MXNet Community,
> >
> > From talking
M
> To: d...@mxnet.apache.org
> Subject: Re: MXNet 1.6.0 release
>
> Dear MXNet Community,
>
> From talking to different Members of the Community, I realized there is a
> misunderstanding of what "code freeze" actually means. Let me try to clear
> this confusion in this ema
Dear MXNet Community,
>From talking to different Members of the Community, I realized there is a
>misunderstanding of what "code freeze" actually means. Let me try to clear
>this confusion in this email.
The code freeze does not mean "1.6 release is done, let's vote on it and ship
it as-is". A
Dear MXNet Community,
This morning I updated the 1.6.x branch and so the code freeze is in effect. I
would like to thank everyone who helped in preparing and reviewing pull
requests to meet this deadline.
Unfortunately, nightly tests do not currently pass (I created an issue about
this: [1]).
tric
> > Sent: Friday, November 1, 2019 12:13 PM
> > To: dev@mxnet.incubator.apache.org; d...@mxnet.apache.org
> > Subject: RE: RE: MXNet 1.6.0 release
> >
> > Sure, I will see the issue.
> >
> > > -Original Message-
> > > From: Przemysł
Since vast majority of the commits pushed to master since last Thursday were in
scope, I just updated 1.6.x branch to match master this morning. That commit is
included.
On 2019/11/02 00:55:11, "Lausen, Leonard" wrote:
> Hi Przemek,
>
> https://github.com/apache/incubator-mxnet/issues/16049 w
Hi Przemek,
https://github.com/apache/incubator-mxnet/issues/16049 was fixed in master
branch yesterday. Can we include it for the 1.6 release?
Thank you
Leonard
On Fri, 2019-10-25 at 14:24 +, Przemysław Trędak wrote:
> Dear MXNet Community
>
> Last night I updated 1.6.x branch to point to
t.apache.org
> Subject: RE: RE: MXNet 1.6.0 release
>
> Sure, I will see the issue.
>
> > -Original Message-
> > From: Przemysław Trędak
> > Sent: Friday, November 1, 2019 11:27 AM
> > To: d...@mxnet.apache.org
> > Subject: Re: RE: MXNet 1.6.0 release
Sure, I will see the issue.
> -Original Message-
> From: Przemysław Trędak
> Sent: Friday, November 1, 2019 11:27 AM
> To: d...@mxnet.apache.org
> Subject: Re: RE: MXNet 1.6.0 release
>
> Hi Patric,
>
> Actually the nightly tests show some problems with m
progress.
>
> Feel free to ping me if anything we can help.
>
> Thanks,
>
> --Patric
>
> > -Original Message-
> > From: Przemysław Trędak
> > Sent: Friday, October 25, 2019 10:25 PM
> > To: d...@mxnet.apache.org
> > Subject: Re: MXNet 1
25, 2019 10:25 PM
> To: d...@mxnet.apache.org
> Subject: Re: MXNet 1.6.0 release
>
> Dear MXNet Community
>
> Last night I updated 1.6.x branch to point to current master. The code freeze
> is now in effect.
>
> That said, since most of the features intended fo
ay, October 25, 2019 10:25 PM
> > To: d...@mxnet.apache.org
> > Subject: Re: MXNet 1.6.0 release
> >
> > Dear MXNet Community
> >
> > Last night I updated 1.6.x branch to point to current master. The code
> freeze is
> > now in effect.
> >
> > That
Message-
> From: Przemysław Trędak
> Sent: Friday, October 25, 2019 10:25 PM
> To: d...@mxnet.apache.org
> Subject: Re: MXNet 1.6.0 release
>
> Dear MXNet Community
>
> Last night I updated 1.6.x branch to point to current master. The code freeze
> is
> now in eff
Dear MXNet Community
Last night I updated 1.6.x branch to point to current master. The code freeze
is now in effect.
That said, since most of the features intended for 1.6 release are still not
fully finished (a few PRs for BERT GPU performance, multiple MKLDNN PRs,
multiple PRs tagged NumPy e
Thanks Tao,
I’m working closely with Jun to ensure the Numpy effort is included in the
release.
Sam
> On Oct 11, 2019, at 10:35 AM, Tao Lv wrote:
>
> Hi Przemek,
>
> Thank you for volunteering!
>
> I remember Jun (reminisce@github) has already been working on 1.6.0. You
> might need chec
Hi Przemek,
Thank you for volunteering!
I remember Jun (reminisce@github) has already been working on 1.6.0. You
might need check with him to avoid duplicate effort.
Thanks,
-tao
On Fri, Oct 11, 2019 at 8:00 AM Przemysław Trędak
wrote:
> Hi MXNet Community,
>
> As the 1.5.1 patch release is
21 matches
Mail list logo
