Congratulations Sam!
Those are great features to MXNet.
-Original Message-
From: Zhao, Patric
Sent: Thursday, July 30, 2020 8:40 AM
To: dev@mxnet.incubator.apache.org
Subject: RE: [Announcement] New Committer - Sam Skalicky
Congratulations, Sam, thanks all of your great works in MXNet
Hi Justin,
We're doing 1.7.0 source release recently, and the vote on dev@ was passed,
vote thread [1], result thread[2].
Seems the discussion on mshadow donation is still not finalized, may I know if
you have any concern to proceed the current release under DISCLAIMER-WIP?
Thanks,
-Ciyong
[1
; Markus Weimer
; Michael Wall
Subject: Re: [RESULTS] [VOTE] Release Apache MXNet (incubating) version
1.7.0.rc1
Thanks! Please don't forget the release vote on incubator.
-Marco
On Thu, Jul 23, 2020, 9:37 AM Chen, Ciyong wrote:
> Dear MXNet community,
>
> I'm happy to announce
Dear MXNet community,
I'm happy to announce the results of the vote.
This vote passes with 10 +1 votes (3 binding) and no 0 or -1 votes.
+1 votes
* Sheng Zha / binding
* Tao Lv / binding
* Zhi Zhang / binding
* Aston Zhang
* Patric Zhao
* Skalicky Sam
* Karan Jariwala
* Chaitanya Bapat
* Kshitij
tor.apache.org
> Cc: d...@mxnet.apache.org; Bob Paulin ; Henri Yandell
> ; Jason Dai ; Markus Weimer
> ; Michael Wall
> Subject: Re: [VOTE] Release Apache MXNet (incubating) version
> 1.7.0.rc1
>
> +1
> Passed d2l-en v0.14.1:
> https://github.com/d2l-ai/d2l-en/releases/tag/v0.14.1
Dear MXNet community,
This is the vote to release Apache MXNet (incubating) version 1.7.0. Voting
will start 16th July 23:59:59 PST and close on 19th July 23:59:59 PST.
Link to release notes:
https://cwiki.apache.org/confluence/display/MXNET/1.7.0+Release+notes
Link to release candidate:
https:
18700
[3] https://github.com/apache/incubator-mxnet/pull/18703
Thanks,
-Ciyong
-Original Message-----
From: Chen, Ciyong
Sent: Tuesday, July 14, 2020 10:13 AM
To: dev@mxnet.incubator.apache.org; d...@mxnet.apache.org
Subject: RE: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc0
Tha
ce on CPU and those regression was not
> caught.
>
> My 2-cent is it might not be a blocker for the release, and we can have
room
> for improvement for upcoming 2.0 and 1.7.1 if necessary
>
> Ziyi
>
> On 2020/07/13 08:40:32, "Chen, Ciyong" w
issue for 1.7.
Thanks,
Ziyi
On 2020/07/13 02:19:28, "Chen, Ciyong" wrote:
> Hi Ziyi, Xingjian,
>
> Thanks for reporting the issues from GluonCV/AutoGluon perspective.
> I just did a quick try by reverting the
> https://github.com/apache/incubator-mxnet/pull/18358, then t
existing models and various
> customer
> >> models.
> >>>
> >>> So my 2-cents is reverting this PR in 1.7, and try patching the PR
> >>> in
> >> 1.x and 2.0, meaning that the 1.7 won't have memory usage optimized
> >> by
> that
> >&g
in 1.x
and 2.0, meaning that the 1.7 won't have memory usage optimized by that feature.
I'd like to hear what you think about this issue.
Thanks,
Ziyi
On 2020/07/10 06:18:02, "Chen, Ciyong" wrote:
> Hi Community,
>
> I would like to
ou've tried with the
pre-release code bases, thanks!
Best regards,
Ciyong
-Original Message-----
From: Chen, Ciyong
Sent: Monday, July 6, 2020 10:48 PM
To: d...@mxnet.apache.org
Cc: Bob Paulin ; Henri Yandell ; Jason Dai
; Markus Weimer ; Michael Wall
Subject: RE: [VOTE] Release Ap
Chen
-Original Message-
From: Chen, Ciyong
Sent: Monday, July 6, 2020 10:39 PM
To: d...@mxnet.apache.org
Cc: Bob Paulin ; Henri Yandell ; Jason Dai
; Markus Weimer ; Michael Wall
Subject: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc0
Dear MXNet community,
This is the vote
Dear MXNet community,
This is the vote to release Apache MXNet (incubating) version 1.7.0. Voting
will start July 6, 23:59:59 PST and close on July 9, 23:59:59 PST.
Link to release notes:
https://cwiki.apache.org/confluence/display/MXNET/1.7.0+Release+notes
Link to release candidate:
https://gi
marking numpy operators being marked as experimental and going
with v1.7 given numpy is still in progress and mainly targeted beginning v2.0.
And, v1.7 has several significant features such as accelerator APIs.
On Mon, 29 Jun 2020, 7:51 pm Chen, Ciyong, wrote:
> Hi Chai,
>
> We've fi
0 at 06:32, Chen, Ciyong wrote:
> Hi Leonard,
>
> Thanks for your confirmation on the build issue. As it's not a blocker
> for
> 1.7 release now, then we can consider to backport the fix to 1.7.x
> branch when it's ready.
> The only remaining item is how to deal with
add Apache Headers to Third Party Code [WAS] Re:
[MENTORS] PPMC case-by-case decision for major modifications of third-party
work guidance
Hi Ciyong,
the consensus passed, so we should proceed according to the consensus.
Thank you
Leonard
On Tue, 2020-06-23 at 09:04 +, Chen, Ciyong wrote
Hi all,
I'm wondering if there's any further concerns for this "72 hours lazy
consensus"?
Shall we continue with the option of "I believe PPMC would prefer to put the
ASF header on top of the file (ie. 2 headers)"
Thanks,
-Ciyong
-Original Message-
From: Leonard Lausen
Sent: Tuesday,
+1, as v1.x and release branches are still moving forward
-Ciyong
-Original Message-
From: Tao Lv
Sent: Monday, June 22, 2020 12:55 PM
To: dev@mxnet.incubator.apache.org
Subject: Re: [Lazy consensus] Turn on Branch Protection for Release branches
and v1.x
+1
On Sat, Jun 20, 2020 at 7
anks!
>1) Numpy License Headers Only
> 2) Apache Header with Numpy License Header (keep the license header as is now)
Best Regards,
-Ciyong
From: Bob Paulin
Sent: Monday, June 15, 2020 11:38 PM
To: dev@mxnet.incubator.apache.org; Chen, Ciyong ;
lau...@apache.org; d...@mxnet.apache.org; gene...
Hi Bob, Leonard,
Thanks for the elaboration/guideline on the dual license issue.
May I have the conclusion as below based on Bob’s direction/suggestion:
* If there’s no any different opinion or objection, keep either origin
Numpy license or ASF license but not dual, which depends on how MX
o: dev@mxnet.incubator.apache.org
> Subject: Re: RE: Updates for 1.7.0 minor release
>
> Hey Ciyong,
>
> Since the last discussion, the GPU memory regression PR has been reverted.
> Is there any update for when the rc0 for 1.7 will be cut?
> Can the community help exped
mmunity help expedite the process in any way?
Thanks
Chai
On Wed, 13 May 2020 at 18:28, Chen, Ciyong wrote:
> Hi Ziyi,
>
> Thanks for reaching me for the known/found issue in the upcoming
> release, let's fix all these potential issues before dropping the rc0
> tag 😊
> I&
.0, but we should revert this in 1.x and 1.7
branches. I have made a reverting PR on 1.x
https://github.com/apache/incubator-mxnet/pull/18309.
I am thinking if you can help to merge the reverting into 1.x and 1.7 before
making the rc0 tag?
Thanks,
Ziyi
On 2020/05/12 00:58:22, "Chen, Ciyong
Hello Ciyong,
With the https://github.com/apache/incubator-mxnet/pull/18261 merged, nightly
pipeline passes for 1.7.x So as far as the 2 nightly test pipelines are
concerned [NightlyTests and NightlyTestsForBinaries] 1.7.x is good to go!
Thanks,
Chai
On Sun, 10 May 2020 at 04:53, Chen, Ciyong
ps://github.com/apache/incubator-mxnet/pull/18220
[4] https://github.com/apache/incubator-mxnet/pull/18237
[5]
http://jenkins.mxnet-ci.amazon-ml.com/job/NightlyTestsForBinaries/job/v1.7.x/2/execution/node/232/log/
[6] https://github.com/apache/incubator-mxnet/pull/18261
-Original Message-
Hi MXNet Community,
Code freeze for 1.7.0 minor release is in effect (last commit: 38e6634)!
Which means there're no more NEW features going to be accepted for this release.
Many thanks to everyone who helped submitting/back porting/reviewing the PRs
targeting this release.
I've created a draft
ssage-
From: Chen, Ciyong
Sent: Saturday, April 18, 2020 8:23 PM
To: dev@mxnet.incubator.apache.org
Cc: d...@mxnet.apache.org
Subject: RE: RE: [Announce] Upcoming Apache MXNet (incubating) 1.7.0 release
Hi dev,
Please note that v1.7.x branch is rebased to the latest v1.x branch (4cf2ad39b)
ow if you
need a time extension.
Can I get some help from CI team to help creating the
NightlyTests/NightlyTestForBinaries task for v1.7.x branch? Thanks!
Thanks,
-Ciyong
-Original Message-
From: Chen, Ciyong
Sent: Thursday, April 16, 2020 10:11 AM
To: dev@mxnet.incubator.apache.org
release!
Sam
On Apr 10, 2020, at 7:54 PM, Chen, Ciyong
mailto:ciyong.c...@intel.com>> wrote:
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you can confirm the sender and know the
content is safe.
Hi Prezmek and all,
Su
e ops to the 1.7 scope, but will need a
small extension - the PR should be ready to merge to master and cherry-picked
to 1.7 early next week.
Thanks
Przemek
On 2020/04/09 08:27:58, "Chen, Ciyong" wrote:
> Hi dev,
>
> Just a remainder for you to do the backport of new
driving 1.7.0 release!
> Looking forward to collaboration.
>
> Cheers,
> Chai
>
> On Mon, 6 Apr 2020 at 02:51, Chen, Ciyong wrote:
>
> > Hi MXNet Community,
> >
> >
> >
> > As the 1.6.0 release is done (many thanks to Przemek) for a while,
&
Hi MXNet Community,
As the 1.6.0 release is done (many thanks to Przemek) for a while, it's time to
prepare for the next minor release of MXNet 1.7.0.
Thanks to Patric (pengzhao-intel@github) who had created the GitHub issue[1] to
discuss and collect the major features for 1.7.0. Please ad
+1
Build from source on CentOS 7.6 with GCC 4.8.5 with MKLDNN.
Unit tests passed and imagenet examples (with MKL-DNN subgraph backend) looked
good on performance and accuracy in both FP32 and INT8 mode, RNN training
worked.
Thanks,
-Ciyong
-Original Message-
From: Lai Wei
Sent: Wedne
is to keep the number of them down to less than five or six.
- What about making performance a Key Feature and highlighting that on the
main page? I'd switch it with Tools & Libraries since Ecosystem is the next
thing below.
Cheers,
Aaron
On Thu, Dec 19, 2019 at 2:03 AM Chen, Ciyo
Hi MXNet community,
While doing search for MXNet from the official
website[https://mxnet.incubator.apache.org/], it's not that convenient to get
the recent/latest performance data, besides there's some mismatch between the
link and description in the current websites.
We can also add some new c
Appreciate Tredak to push out voting for 1.6 release.
+1 as we've done lots of tests with expected performance in many different
scenarios including both single-node and multi-node (horovod based), both FP32
and INT8 precision on many topologies.
-Ciyong
-Original Message-
From: Zhao,
Really great features, it will provide a more convenient way for deployment.
BTW, does it support backward ops too?
-Ciyong
-Original Message-
From: Marco de Abreu
Sent: Sunday, December 8, 2019 2:56 AM
To: dev@mxnet.incubator.apache.org
Subject: Re: Custom C++ Operators
Awesome projec
Many thanks @ Przemek for leading 1.6 release process!
Can you share the latest status of 1.6 release as we don't see any updates for
a while.
Any plan or ETA for the following voting?
Thanks!
-Ciyong
-Original Message-
From: Zhao, Patric
Sent: Monday, November 18, 2019 2:10 PM
To: dev
atch 199, Speed=452.790825 Epoch 1, Duration=130.199421 Epoch 1,
> > Training
> > accuracy=0.183863 Epoch 1, Validation accuracy=0.237079 Epoch 2,
> > Batch 199, Speed=451.406559 Epoch 2, Duration=126.320823 Epoch 2,
> > Training
> > accuracy=0.214844 Epoch 2, Validation accu
Hi Pedro,
I'm looking at this case, and using the script of
"incubator-mxnet/example/image-classification/train_cifar10.py" to get
the timing data, but seems there's not much difference between mxnet 1.4.1.rc0
and 1.5.0.rc1 on C5.18xlarge.
Not sure if there's any difference in the python script
41 matches
Mail list logo
