Hi Yan Zhe,
Invite is sent. You can find the `mxnet` channel in the ASF workspace.
-tao
On Fri, May 31, 2019 at 3:15 PM 严哲 wrote:
> Dear MXNet community，
>
>
>
>
> I want to join the MXNet slack channel, can you allow me to join it ?
>
>
>
>
>
> Thanks & Best Regards,
>
> Yan Zhe
Hi Shuchun,
Welcome to the MXNet community!
Invite is sent. You will be added to the 'general' channel of ASF and you
can search for the 'mxnet' channel.
-tao
On Sun, May 5, 2019 at 5:38 PM shuchun liu wrote:
> thanks.
>
> --
> --
> --
> Best Regards,
> Liu
d, run, functionality and performance testing
> for
> > this release?
> >
> > Thanks,
> >
> > --Patric
> >
> > > -Original Message-
> > > From: Tao Lv
> > > Sent: Monday, August 12, 2019 8:59 PM
> > > To: dev@mxnet.incubator.apach
. MKLML license issue is pushed out to 1.6
release. But license issue for cub and pybind is still open.
Let me know if you any suggestion. Thanks for your support!
-tao
On Wed, Aug 7, 2019 at 11:03 PM Tao Lv wrote:
>
> Update:
>
> Thanks to wkcn's report, Issue #15774 [1] and the f
Hi community,
Thanks for the initiative from Sam (samskalicky@github), we already have a
discussion thread [1] on github about the defects and bugs exposed in the
1.5.0 release.
Shufan (juliusshufan@github) and I (TaoLv@github) would like to manage the
release of 1.5.1. This will be our first
, Aug 12, 2019 at 9:57 PM Zhao, Patric wrote:
> Thanks for the explanation, Marco & Tao. Sounds great!
>
> > -Original Message-----
> > From: Tao Lv
> > Sent: Monday, August 12, 2019 9:54 PM
> > To: dev@mxnet.incubator.apache.org
> > Subje
ch early next week
and start the vote subsequently.
Thanks,
-tao
[1]
https://github.com/apache/incubator-mxnet/commit/33f4de13d3909fc356ace8ff7a5c9665a651fc63
On Fri, Aug 30, 2019 at 5:31 PM Tao Lv wrote:
> Progress since the last update:
> 1. 2 more fixes [1] [2] were picked to v1.5.x;
://github.com/apache/incubator-mxnet/pull/15608
On Fri, Aug 30, 2019 at 7:16 AM Lai Wei wrote:
> Hi Tao,
>
> Just checked 1.5.x nightly build is passing, so 10 is not needed. I moved
> it so 1.6.0 scope.
>
> Thanks
>
>
> Best Regards
>
> Lai
>
>
> On Thu, Aug 29, 2
at 9:51 PM Tao Lv wrote:
>
> I drafted the release notes for 1.5.1 patch release:
> https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Notes
>
> Any comments or suggestions are highly appreciated!
>
> -tao
>
> On Mon, Sep 2, 2019 at 2:00 PM kellen su
gt; Might be useful to put in 1.5.1:
> > > https://github.com/apache/incubator-mxnet/pull/15762 ?
> > >
> > > Pedro.
> > >
> > > On Tue, Aug 20, 2019 at 7:49 AM Tao Lv wrote:
> > >
> > > > Hi dev,
> > > >
> > >
anything. But the changes are needed to make Julia setup more seamless.
>
> What "update" is needed?
>
>
> On Wed, Aug 28, 2019, 08:36 Tao Lv wrote:
>
> > @Pedro, seems the issue is still open on the master branch. Do you still
> > think we can have your fix
o master so you don't need to pick it.
> 6 probably, but there might be other PRs needed. I'd check out the branch
> and attempt the install across platforms to be sure.
>
> On Wed, Aug 28, 2019, 08:55 Tao Lv ta...@apache.org>> wrote:
>
> Hi Aaron,
>
> They were proposed to be
Hi Community,
Code freeze for 1.5.1 patch release will be 9/3 6pm PST (9/4 9am CST). If
you have any additional fix in progress and would like to include it in
this release, please assure they have been merged before code freeze.
Thanks for all your support and contribution.
-tao
rganizing the release Tao.
>
> On Sun, Sep 1, 2019, 5:53 PM Tao Lv wrote:
>
> > Hi Community,
> >
> > Code freeze for 1.5.1 patch release will be 9/3 6pm PST (9/4 9am CST). If
> > you have any additional fix in progress and would like to include it in
> > this rel
://cwiki.apache.org/confluence/display/MXNET/Release+Process
[2] https://github.com/apache/incubator-mxnet/releases/tag/1.5.1.rc0
On Wed, Sep 4, 2019 at 9:23 AM Tao Lv wrote:
>
> Code freezing!
>
> If you happen to be around github, please help to review the PR [1] for
> bumping
e language bindings
> are
> >> required for voting.
> >>
> >> Thanks,
> >>
> >> Lin
> >>
> >> On Tue, Sep 17, 2019 at 7:32 AM Tao Lv wrote:
> >>
> >> > Thanks for your help, Carin. Per step 1.14 of the release
Dear MXNet community,
This is the 3-day vote to release Apache MXNet (incubating) version 1.5.1.
Voting on dev@ will start September 17, 12:00pm (PST) and close on
September 20, 12:00pm (PST).
1) Link to release notes:
https://cwiki.apache.org/confluence/display/MXNET/1.5.1+Release+Notes
ity to
> > complete?
> >
> > Thanks,
> >
> > Lin
> >
> > On Fri, Sep 6, 2019 at 7:35 AM Tao Lv wrote:
> >
> > > Update:
> > >
> > > Artifacts of 1.5.1.rc0 have been uploaded to github and Apache dist.
> > Befor
Update:
Artifacts of 1.5.1.rc0 have been uploaded to github and Apache dist. Before
voting, we still need some time to build packages for Scala, Clojure and R.
Thank you for your patience.
-tao
On Thu, Sep 5, 2019 at 10:15 PM Tao Lv wrote:
>
> Following the release process [1],
Release Apache MXNet (incubating) 1.5.1.rc0
> > >
> > > +1 for Scala/Java test. Passed all tests for CPU/GPU build.
> > > Also tested build from source with static build.
> > >
> > > Thanks,
> > > Qing
> > > ___
> [3] https://github.com/apache/incubator-mxnet/issues/15374
> >
> > Best Regards
> >
> > Lai
> >
> >
> > On Wed, Jul 31, 2019 at 8:04 AM Tao Lv wrote:
> >
> > > Hi community,
> > >
> > >
> > >
> &
/incubator-mxnet/issues/15613#issuecomment-518430120
[2] https://github.com/apache/incubator-mxnet/issues/15737
[3] https://github.com/apache/incubator-mxnet/pull/15692
On Thu, Aug 1, 2019 at 4:24 PM Tao Lv wrote:
> Hi Sandeep/Lai,
>
> Thank you for the prompt response!
>
> htt
AM Marco de Abreu
wrote:
> We only need a mentors vote on general, but it certainly would be
> appreciated especially considering the licensing issues we're constantly
> encountering. One part of graduation is having a number of releases that
> went without issues.
>
> -Marco
&
Dear MXNet community,
I'm happy to announce the results of the vote.
This vote passes with 9 +1 votes (4 binding), no 0 votes, and 0 -1 vote.
+1 votes
* Qing Lan (binding)
* Patric Zhao
* Lin Yuan
* Chaitanya Bapat
* Anirudh Subramanian (binding)
* Sandeep Krishnamurthy (binding)
* Lai
Hi dev,
I'm glad to say that the rc0 of 1.5.1 patch release has passed the vote on
general@. Please find the voting thread at:
https://lists.apache.org/thread.html/282f7911768dab61ddf8f70adcce34ef0afb285046093b3ff0bafb7e@%3Cgeneral.incubator.apache.org%3E
Now I'm proceeding the release process
* For pypi, we can use mirrors.
On Tue, Dec 3, 2019 at 9:28 PM Tao Lv wrote:
> As we have many users in China, I'm considering the accessibility of S3.
> For pip, we can mirrors.
>
> On Tue, Dec 3, 2019 at 3:24 PM Lausen, Leonard
> wrote:
>
>> I would like to r
As we have many users in China, I'm considering the accessibility of S3.
For pip, we can mirrors.
On Tue, Dec 3, 2019 at 3:24 PM Lausen, Leonard
wrote:
> I would like to remind everyone that lazy consensus is assumed if no
> objections
> are raised before 2019-12-05 at 05:42 UTC. There has been
samples/sec a 13.3% regression in
> training
> > > speed for a resnet18 training benchmark on a C5.18xlarge EC2 instance
> > (with
> > > 72 cores). Rebuilding with MKL BLAS showed an increase in performance
> to
> > > 1600 samples/sec in the 1.6.0 branch.
> > &g
Invitation sent to jd...@amazon.com. Welcome to the community!
-tao
On Fri, Dec 13, 2019 at 11:40 PM Desai, Jay
wrote:
> Hi please add me on slack, I have high interest in mxnet for contribution
> and research. Thanks
>
Hi Guanxin,
To subscribe the dev@ mail list, you need send request to
dev-subscr...@mxnet.apache.org .
More details here:
https://mxnet.incubator.apache.org/community/contribute#mxnet-dev-communications
Thanks,
-tao
On Fri, Dec 13, 2019 at 11:40 PM Qiao, Guanxin
wrote:
> Hi,
>
> I am Guanxin
Regarding the cases listed by Marco:
- AMD CPU
>From my architecture knowledge, what works on C4 instances (with AVX2
support) should also work well on m5a, right? I think mxnet-mkl and
mxnet-cuxxmkl packages have been fully validated on AVX2 machines.
Also, we didn't perform any validation on AMD
ository.apache.org/content/repositories/staging/org/apache/mxnet/contrib/clojure/clojure-mxnet-linux-gpu/1.5.1/
>
> https://repository.apache.org/content/repositories/staging/org/apache/mxnet/contrib/clojure/clojure-mxnet-osx-cpu/1.5.1/
>
> On Tue, Sep 17, 2019 at 2:21 PM Tao Lv wrote:
&
> > +1
> > > >
> > > > Build from source with cmake and ran unittest for gluon and amp.
> > > >
> > > > Noticed that test_sync_batchnorm fails on p3.8xlarge (hidden by
> > the CI
> > > > because passes on machines with 1 or 2 gpus
Sure. Really appreciate your help, Mike.
-tao
On Fri, Sep 20, 2019 at 10:48 PM Michael Wall wrote:
> Tao,
>
> I can take a look tonight if you want to wait.
>
> Mike
>
> On Fri, Sep 20, 2019 at 10:45 AM Tao Lv wrote:
>
> > Thank you all for the support!
&g
h
> > is the first result of my Google search for 'install mxnet'.
> >
> > Mike
> >
> > On Tue, Sep 24, 2019 at 1:26 AM Tao Lv wrote:
> >
> >> Thank you Mike! I'm sorry for missing your vote on dev@.
> >>
> >> To other MXNet mentors,
Okay, looks like there is no objections. I will send the announcement to
announce@ and general@ soon.
Thanks,
-tao
On Wed, Oct 9, 2019 at 10:35 AM Tao Lv wrote:
> Dear community,
>
> This is to review the announcement for 1.5.1 release according to the
> section 3.4 in rel
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
Hi all,
The Apache MXNet (incubating) community is happy to announce Apache MXNet
(incubating) version 1.5.1!
Apache MXNet (incubating) is a deep learning framework designed for both
efficiency and flexibility. It allows you to mix symbolic and imperative
programming to maximize efficiency and
I just sent out the announcement of 1.5.1 release for review. But still not
sure how to change http://mxnet.incubator.apache.org/get_started and
http://mxnet.incubator.apache.org/get_started/download to accommodate.
Can anyone help on that?
thanks,
-tao
On Wed, Oct 9, 2019 at 10:24 AM Zhao,
Dear community,
This is to review the announcement for 1.5.1 release according to the
section 3.4 in release process.
===
The Apache MXNet (incubating) community is happy to announce Apache MXNet
(incubating) version 1.5.1!
Apache MXNet (incubating) is a deep learning framework designed for
Nice. It's an essential step towards MXNet 2.0. Curious to know that do we
still encourage contributors to create PR against the master branch? And in
what strategy we need pick a commit to branch 1.x? Or they need create two PRs
against two branches simultaneously?
--
You are receiving this
What about those v1, v2 APIs?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-mxnet/issues/17676#issuecomment-591754890
move/modify the script appropriately.
> >
> > Sam
> >
> > > On Jan 12, 2020, at 5:41 PM, Tao Lv wrote:
> > >
> > > Thank you for the effort, Sam. One minor suggestion: can we sort and
> put
> > > the latest build at the top of the
We have `v1` and `v2` APIs like:
https://mxnet.incubator.apache.org/api/python/docs/search.html?q=v1
https://mxnet.incubator.apache.org/api/python/docs/search.html?q=v2
Do we need cover them in the RFC? How to deprecate or unify these APIs?
--
You are receiving this because you authored the
It seems the src tar and signature are missing from the tag.
On Fri, Jan 31, 2020 at 11:09 AM Przemysław Trędak
wrote:
> Dear MXNet community,
>
> This is the vote to release Apache MXNet (incubating) version 1.6.0.
> Voting starts today and will close on Monday 2/3/2020 23:59 PST.
>
> Link to
pache.org/repos/dist/dev/incubator/mxnet/1.6.0.rc2/ and
> draft of the release on GitHub have them.
>
> Thank you
> Przemek
>
> On 2020/02/01 14:23:11, Tao Lv wrote:
> > It seems the src tar and signature are missing from the tag.
> >
> > On Fri, Jan 31, 2020 at 11
+1
I tested below items:
1. download artifacts from Apache dist repo;
2. the signature looks good;
3. build from source code with MKL-DNN and MKL on centos;
4. run fp32 and int8 inference of ResNet50 under /example/quantization/.
thanks,
-tao
On Sun, Feb 2, 2020 at 11:00 AM Tao Lv wrote:
>
Hi Rahul,
Invite is sent to rahulbhal...@protonmail.com. Welcome to the community and
looking forward to your contribution.
-tao
On Mon, Feb 10, 2020 at 1:10 PM Rahul
wrote:
> Hello,
>
> As per the conversation with [Pedro Larroy](https://twitter.com/plarroy)
> on [Twitter
Can someone educate me how to re-trigger a single test suite in CI?
On Thu, Feb 13, 2020 at 5:10 AM Lausen, Leonard
wrote:
> Hi Denis,
>
> pipeline may be the wrong word, job may be the correct one. For example,
> commiters can currently access a job page like
>
>
gt; Pypi, that person shall please go ahead and propose it in a
> > separate
> > discussion thread.
> >
> > Currently we don't have generally working nightly builds to Pypi
> > and
> > as a
> > matter of fact we know that we can't have them due to Pypi's pol
> 3.1. C-API Clean-up
C-API is the foundational API in MXNet that all language bindings depend on.
@szha I'm looking at the item 3.1.2. Could you please explain the scope of
C-API? Do you mean those APIs sit in the src/c_api/ folder?
--
You are receiving this because you were mentioned.
Reply
+1 for using master branch for 2.0 development. I think we need 3 branches at
least:
1. master branch: for 2.0 development
2. v1.x: for 1.x development and maintenance
3. v1.7.x: for 1.7.x release
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on
Is it possible for re-triggering a single job to be abused? For example,
the author spends two days re-triggering a flaky job to make it pass. But
other jobs which have passed the validation may be broken by other commits
during the two day without being noticed. And finally the PR is merged with
Hi dev,
Because we have master branch for 2.0 development and v1.x branch for 1.x
development, please make sure your new features, bug fixes and improvements
are properly picked to v1.x branch before the code rebase, if you want them
to be included into v1.7 release.
thanks,
-tao
On Tue, Apr 7,
+1 (binding)
- Untar the source code package;
- Build from source code with makefile, USE_BLAS=mkl, USE_MKLDNN=1;
- Check mx.__version__;
- Run benchmark_score.py under examples/image-classification.
On Wed, Jul 22, 2020 at 3:13 PM Patrick Mu wrote:
> + 1
>
> Test custom operators: all
+1 (binding)
I did:
- Verify the key and signature;
- Untar the source code package;
- Build from source code with makefile, USE_BLAS=mkl, USE_MKLDNN=1;
- Check mx.__version__;
- Run benchmark_score.py under examples/image-classification.
-tao
On Fri, Jul 10, 2020 at 2:18 PM Chen, Ciyong
+1
On Sat, Jun 20, 2020 at 7:01 AM Sheng Zha wrote:
> Hi,
>
> I'd like to propose that we turn on branch protection and CI check
> enforcement that's consistent with our master branch for all release
> branches and v1.x. So far we only have branch protection and enforce CI
> checks on master
57 matches
Mail list logo
