RE: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc1

2020-08-17 Thread Chen, Ciyong 
Hi Michael,

Thank you for your time to review and vote.

Regarding your questions:
> - Does anything with mshadow need to change now that it has passed clearance.
From source code release perspective, I don't think there's anything we need to 
change as mshadow is already in the code base with the correct license header. 
CC @Sheng to see if any comments.

> - I tried running tests a couple of ways after the build I build but they 
> just hung for 15 min before I control-c'd them.  Maybe I didn't wait long 
> enough, but there was no indication anything was running.
The test suite contains lots of test cases which will be very time consuming, " 
ctest -vv" doesn't enable the verbose output thus looks like it hung as no 
output on the terminal. 
By using "ctest --verbose" which turns on the verbose and will give more 
details for all the test cases. 
Currently, the entire test suite will run through many different configurations 
of hardware and docker image via CI pipeline.

Thanks,
-Ciyong

-Original Message-
From: Michael Wall  
Sent: Tuesday, August 18, 2020 9:54 AM
To: general@incubator.apache.org
Subject: Re: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc1

+1 from me

Checked
- signatures
- incubating in name
- License, Notice and Disclaimer
- Compiled from source with CPP bindings using 
https://mxnet.apache.org/versions/1.6/get_started/build_from_source#install-mxnet-for-python,
https://mxnet.apache.org/versions/1.6/get_started/cpp_setup and 
https://github.com/apache/incubator-mxnet/blob/1.7.0.rc1/config/linux.cmake

Couple of questions
- Does anything with mshadow need to change now that it has passed clearance.
- I tried running tests a couple of ways after the build I build but they just 
hung for 15 min before I control-c'd them.  Maybe I didn't wait long enough, 
but there was no indication anything was running.

Here is the run

```
[0/1] Running tests...
Test project 
/home/mikewall/Desktop/mxnet-1.7.0/apache-mxnet-src-1.7.0.rc1-incubating/build
Start 1: AllTestsInmxnetUnitTests
^Cninja: build stopped: interrupted by user.
```

And here is my history fwiw

```
sudo apt-get install -y build-essential git ninja-build ccache libopenblas-dev 
libopencv-dev cp config/linux.cmake config.cmake rm -rf build cmake -S. -Bbuild 
-DUSE_CPP_PACKAGE=1 -DCMAKE_BUILD_TYPE=Release -GNinja cmake --build build 
cmake --build build --target test cd build && ctest -vv ```

On Mon, Aug 17, 2020 at 2:27 PM Sheng Zha  wrote:
>
> Hi Justin,
>
> Since the blocking issue has been resolved, would you mind changing your 
> vote? Thanks.
>
> Regards,
> Sheng
>
> On 2020/07/26 01:27:39, Justin Mclean  wrote:
> > Hi,
> >
> > -1 (binding) as this release contains code that hasn’t gone though IP 
> > clearance (mshadow).
> >
> > I checked:
> > - incubating in name
> > - disclaimer exists
> > - LICENSE and NOTICE have improved but I did not do an exhaustive 
> > check
> > -  No unexpected binary file
> > - ASF files have ASF headers
> > - unable to compile from source
> >
> > It also seems that this code may have been released before the 
> > PPMC/IPMC vote is over see [1][2][3][4] There are also branding and 
> > trademark issue with this site [5] This is in addition to the issues 
> > previously noted with releases, branding and trademarks.[6]
> >
> > Thanks,
> > Justin
> >
> >
> > 1. https://sourceforge.net/projects/apache-mxnet.mirror/
> > 2. 
> > https://repo.gradle.org/gradle/simple/repo/ai/djl/mxnet/mxnet-native
> > -mkl/1.7.0-b/ 3. https://mvnrepository.com/artifact/ai.djl.mxnet
> > 4. 
> > https://aur.archlinux.org/packages/?O=0&SeB=nd&K=mxnet&SB=v&SO=d&PP=
> > 50&do_Search=Go
> > 5. https://djl.ai
> > 6. https://jira.apache.org/jira/browse/INCUBATOR-253
> > 
> > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache IoTDB 0.10.1

2020-08-17 Thread Christofer Dutz 
Hi all,

TL/DR:
+1 binding

Longer version:
I started evaluating. As usual the IoTDB release candidate is in very good 
shape. 

Here some super minor things I noticed:

- It seems the ".plan" templates in 
server/src/assembly/resources/tools/logVisualize/plans support comments, then 
they should contain the Apache headers.
- The karaf feature is referencing a SNAPSHOT version and not even the version 
in this release 0.10.0.SNAPSHOT
- The Dockerfile is also referencing an older SNAPSHOT version 0.10.0-SNAPSHOT
- The mvnw.sh file doesn't seem to be executable
- In the README perhaps point out that you can a) download the source bundle 
from one of the mirrors or you can clone from gitbox or github ... what you're 
describing in the README is actually not downloading, but cloning the repo. I 
would probably base the documentation on downloading a release archive and put 
the cloning in the developer part of the documentation. Reason is: Only for the 
source-bundles can we really ensure this is what was voted on ... tags in 
Github can be changed.

[OK] Download all staged artifacts under the url specified in the release vote 
email into a directory we’ll now call download-dir. 
[OK] Verify the signature is correct: Additional Apache tutorial on how to 
verify downloads can be found here. 
[OK] Check if the signature references an Apache email address.
[OK] Verify the SHA512 hashes:
[OK] Unzip the archive:
[OK] Verify the existence of DISCLAIMER, LICENSE, NOTICE, README, RELEASE_NOTES 
files in the extracted source bundle.
[OK] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the 
extracted source bundle.
[OK] Verify the staged source README, RELEASE_NOTE files correspond to those in 
the extracted source bundle.
[MINOR] Run RAT externally to ensure there are no surprises.
[MINOR] Search for SNAPSHOT references:
[OK] Search for Copyright references, and if they are in headers, make sure 
these files containing them are mentioned in the LICENSE file.
[MINOR] Build the project according to the information in the README.md file.

Great job folks,

Chris



Am 18.08.20, 05:42 schrieb "Xiangdong Huang" :

Hi IPMCs,

We are still looking forward to getting votes from you...

Many thanks!

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Xiangdong Huang  于2020年8月14日周五 上午9:59写道：

> Hello all,
>
> This is a call for vote to release Apache IoTDB (Incubating) version
> 0.10.1, which is a bug-fix version of 0.10.0.
>
> The Apache IoTDB community has voted on and approved a proposal to 
release Apache
> IoTDB (Incubating) version 0.10.1 (with 12 +1 votes).
>
> We now kindly request the Incubator PMC members review and vote on this 
incubator
> release.
>
> Apache IoTDB (incubating) (Database for Internet of Things) is an
> integrated data management engine designed for timeseries data.
>
> IoTDB community vote and result thread:
>
> Result:
>
>
> 
https://lists.apache.org/thread.html/r3d2081bac4aed5217820a4587383150dc7b6471828675d9b6eeacf5e%40%3Cdev.iotdb.apache.org%3E
>
>
> Vote:
>
>
> 
https://lists.apache.org/thread.html/r94e5dcac19d5f2ba9990a95cc1fb5232074702de9f1c326d27eebfe3%40%3Cdev.iotdb.apache.org%3E
>
>
> The release candidates (RC3):
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.10.1/rc3/
>
> Git tag for the release (RC3):
> https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.10.1
>
> Hash for the release tag:
> 023fb84e0b76c0ac64b7a9ac098c640f26795a25
>
>
> Release Notes:
>
> 
https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.10.1/rc3/RELEASE_NOTES.md
>
>
> The artifacts have been signed with Key: 2206EF8F64C35889, which can be 
found
> in the keys file:
>
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS
>
> Look at here for how to verify this release candidate:
>
> 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
>
> The vote will be open for at least 72 hours.
>
>
> The vote will be passed if there are at least 3 IPMC +1 votes and there is
> no -1 vote.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Xiangdong Huang
> Apache IoTDB (incubating)
>
>
>


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache YuniKorn (Incubating) 0.9.0

2020-08-17 Thread Felix Cheung 
+1 (binding)

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers

- didn't try - compile from source


On Mon, Aug 17, 2020 at 9:12 PM Wilfred Spiegelenburg 
wrote:

> Hello IPMC
>
>
>
> The Apache YuniKorn community has voted and approved the release Apache
>
> YuniKorn (incubating) 0.9.0. We now kindly request the IPMC members review
>
> and vote in this release.
>
>
>
> YuniKorn is a standalone, universal resource scheduler that can support
>
> both long-running and batch workloads. The current release provides a fully
>
> functional resource scheduler for K8s.
>
>
>
> YuniKorn community vote thread:
>
>
> https://lists.apache.org/thread.html/rcb63f4de161439e90b47b53388028119c35f8137f78847405f6a2d4d%40%3Cdev.yunikorn.apache.org%3E
>
>
>
> Vote result thread:
>
>
> https://lists.apache.org/thread.html/ra20372465b758b8f9bb3271ec6b4483774eb07af5df83712e7d5ecf7%40%3Cdev.yunikorn.apache.org%3E
>
>
>
> Issues included in this release:
>
> https://issues.apache.org/jira/projects/YUNIKORN/versions/12347799
>
>
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.9.0/
>
>
>
> This release has been signed with a PGP available here:
>
> https://dist.apache.org/repos/dist/release/incubator/yunikorn/KEYS
>
>
>
> Git tag for the release:
>
>   - https://github.com/apache/incubator-yunikorn-core/tree/v0.9.0
>
>   - https://github.com/apache/incubator-yunikorn-k8shim/tree/v0.9.0
>
>   -
>
>
>
>
> https://github.com/apache/incubator-yunikorn-scheduler-interface/tree/v0.9.0
>
>   - https://github.com/apache/incubator-yunikorn-web/tree/v0.9.0
>
>
>
> The vote will be open for at least 72 hours or until the necessary number
>
> of votes is reached.
>
>
>
> Please vote accordingly:
>
>
>
> [ ] +1 Approve the release of Apache YuniKorn (Incubating) 0.9.0
>
> [ ] +0
>
> [ ] -1 Do not approve (please specify the reason)
>
>
>
> Thanks,
>
> Wilfred Spiegelenburg
>
> Apache YuniKorn (Incubating)
>
>

[VOTE] Release Apache YuniKorn (Incubating) 0.9.0

2020-08-17 Thread Wilfred Spiegelenburg 
Hello IPMC

The Apache YuniKorn community has voted and approved the release Apache
YuniKorn (incubating) 0.9.0. We now kindly request the IPMC members review
and vote in this release.

YuniKorn is a standalone, universal resource scheduler that can support
both long-running and batch workloads. The current release provides a fully
functional resource scheduler for K8s.

YuniKorn community vote thread:
https://lists.apache.org/thread.html/rcb63f4de161439e90b47b53388028119c35f8137f78847405f6a2d4d%40%3Cdev.yunikorn.apache.org%3E

Vote result thread:
https://lists.apache.org/thread.html/ra20372465b758b8f9bb3271ec6b4483774eb07af5df83712e7d5ecf7%40%3Cdev.yunikorn.apache.org%3E

Issues included in this release:
https://issues.apache.org/jira/projects/YUNIKORN/versions/12347799

The release candidate:
https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.9.0/

This release has been signed with a PGP available here:
https://dist.apache.org/repos/dist/release/incubator/yunikorn/KEYS

Git tag for the release:
  - https://github.com/apache/incubator-yunikorn-core/tree/v0.9.0
  - https://github.com/apache/incubator-yunikorn-k8shim/tree/v0.9.0
  -

https://github.com/apache/incubator-yunikorn-scheduler-interface/tree/v0.9.0
  - https://github.com/apache/incubator-yunikorn-web/tree/v0.9.0

The vote will be open for at least 72 hours or until the necessary number
of votes is reached.

Please vote accordingly:

[ ] +1 Approve the release of Apache YuniKorn (Incubating) 0.9.0
[ ] +0
[ ] -1 Do not approve (please specify the reason)

Thanks,
Wilfred Spiegelenburg
Apache YuniKorn (Incubating)

Re: [VOTE] Release Apache IoTDB 0.10.1

2020-08-17 Thread Xiangdong Huang 
Hi IPMCs,

We are still looking forward to getting votes from you...

Many thanks!

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Xiangdong Huang  于2020年8月14日周五 上午9:59写道：

> Hello all,
>
> This is a call for vote to release Apache IoTDB (Incubating) version
> 0.10.1, which is a bug-fix version of 0.10.0.
>
> The Apache IoTDB community has voted on and approved a proposal to release 
> Apache
> IoTDB (Incubating) version 0.10.1 (with 12 +1 votes).
>
> We now kindly request the Incubator PMC members review and vote on this 
> incubator
> release.
>
> Apache IoTDB (incubating) (Database for Internet of Things) is an
> integrated data management engine designed for timeseries data.
>
> IoTDB community vote and result thread:
>
> Result:
>
>
> https://lists.apache.org/thread.html/r3d2081bac4aed5217820a4587383150dc7b6471828675d9b6eeacf5e%40%3Cdev.iotdb.apache.org%3E
>
>
> Vote:
>
>
> https://lists.apache.org/thread.html/r94e5dcac19d5f2ba9990a95cc1fb5232074702de9f1c326d27eebfe3%40%3Cdev.iotdb.apache.org%3E
>
>
> The release candidates (RC3):
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.10.1/rc3/
>
> Git tag for the release (RC3):
> https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.10.1
>
> Hash for the release tag:
> 023fb84e0b76c0ac64b7a9ac098c640f26795a25
>
>
> Release Notes:
>
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.10.1/rc3/RELEASE_NOTES.md
>
>
> The artifacts have been signed with Key: 2206EF8F64C35889, which can be found
> in the keys file:
>
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS
>
> Look at here for how to verify this release candidate:
>
> https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
>
> The vote will be open for at least 72 hours.
>
>
> The vote will be passed if there are at least 3 IPMC +1 votes and there is
> no -1 vote.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Xiangdong Huang
> Apache IoTDB (incubating)
>
>
>

Re: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc1

2020-08-17 Thread Michael Wall 
+1 from me

Checked
- signatures
- incubating in name
- License, Notice and Disclaimer
- Compiled from source with CPP bindings using
https://mxnet.apache.org/versions/1.6/get_started/build_from_source#install-mxnet-for-python,
https://mxnet.apache.org/versions/1.6/get_started/cpp_setup and
https://github.com/apache/incubator-mxnet/blob/1.7.0.rc1/config/linux.cmake

Couple of questions
- Does anything with mshadow need to change now that it has passed clearance.
- I tried running tests a couple of ways after the build I build but
they just hung for 15 min before I control-c'd them.  Maybe I didn't
wait long enough, but there was no indication anything was running.

Here is the run

```
[0/1] Running tests...
Test project 
/home/mikewall/Desktop/mxnet-1.7.0/apache-mxnet-src-1.7.0.rc1-incubating/build
Start 1: AllTestsInmxnetUnitTests
^Cninja: build stopped: interrupted by user.
```

And here is my history fwiw

```
sudo apt-get install -y build-essential git ninja-build ccache
libopenblas-dev libopencv-dev
cp config/linux.cmake config.cmake
rm -rf build
cmake -S. -Bbuild -DUSE_CPP_PACKAGE=1 -DCMAKE_BUILD_TYPE=Release -GNinja
cmake --build build
cmake --build build --target test
cd build && ctest -vv
```

On Mon, Aug 17, 2020 at 2:27 PM Sheng Zha  wrote:
>
> Hi Justin,
>
> Since the blocking issue has been resolved, would you mind changing your 
> vote? Thanks.
>
> Regards,
> Sheng
>
> On 2020/07/26 01:27:39, Justin Mclean  wrote:
> > Hi,
> >
> > -1 (binding) as this release contains code that hasn’t gone though IP 
> > clearance (mshadow).
> >
> > I checked:
> > - incubating in name
> > - disclaimer exists
> > - LICENSE and NOTICE have improved but I did not do an exhaustive check
> > -  No unexpected binary file
> > - ASF files have ASF headers
> > - unable to compile from source
> >
> > It also seems that this code may have been released before the PPMC/IPMC 
> > vote is over see [1][2][3][4] There are also branding and trademark issue 
> > with this site [5] This is in addition to the issues previously noted with 
> > releases, branding and trademarks.[6]
> >
> > Thanks,
> > Justin
> >
> >
> > 1. https://sourceforge.net/projects/apache-mxnet.mirror/
> > 2. 
> > https://repo.gradle.org/gradle/simple/repo/ai/djl/mxnet/mxnet-native-mkl/1.7.0-b/
> > 3. https://mvnrepository.com/artifact/ai.djl.mxnet
> > 4. 
> > https://aur.archlinux.org/packages/?O=0&SeB=nd&K=mxnet&SB=v&SO=d&PP=50&do_Search=Go
> > 5. https://djl.ai
> > 6. https://jira.apache.org/jira/browse/INCUBATOR-253
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Giving our PMs and contributors triage rights on GitHub

2020-08-17 Thread Maxime Beauchemin 
Thank you for the comments Julian and Jarek.

A few related thoughts:

- the "triage" GitHub role is very limited (labeling, open/closing, assign,
kanban)
and
I don't think it can be abused. Ideally it should be easy for us to give
this role to contributors that are not-yet-committers that want to help
with labeling, flagging duplicates, ... Can someone think of any way that
this can be abused? Rogue-labeling? Bulk-closing/opening issues?
- PMs (project, product and program managers) have aligned interests with
contributors towards the success of the project, I don't think of them as
"business people". In our community, they've been the connective tissue
between individuals and across organizations, facilitating collaboration
across boundaries and at scale. They do so much that's invisible to the
ASF's traditional way of thinking, like interviewing users, doing
competitive research, running surveys, analyzing issues, bridging with
designers, ...
- the chicken & egg problem is a thing where it absolutely makes sense for
PMs to build context while triaging. Currently they can comment but they
cannot label, reopen, pin issues, manage milestones, which means it's hard
to add value while ramping up
- voting them in as committers is time consuming, error-prone and slow

I think it's pretty clear that to build a great project and community, it
takes much more than just software engineers, especially for projects
"up-the-stack"! It takes all sorts of people with diverse skills and roles
to make a project like Superset successful. Diversity is key, and being
welcoming and inclusive to different types of contribution is super
important.

Last thought: I don't have data on this, but I think the ASF could be doing
better at diversity (see the ApacheCon picture 
as anecdotal evidence). Being inclusive of a wider range of roles and
offering diverse paths to "committerhood" could really help with this. For
Superset and many other projects, finding ways to involve and empower PMs
and designers to partake in the open source process is vital.

Max

On Fri, Aug 14, 2020 at 5:17 AM Jarek Potiuk  wrote:

> Few comments, needs of the Apache Airflow project.
>
> In short: big +1 on enabling the "triage role".
>
> On 2020/08/13 18:43:06, Julian Hyde  wrote:
> > By PM, I presume that you mean either Product Manager or Program
> Manager. I’ve worked at a few companies that practiced “commercial open
> source”, and there is inherent tension in the relationship with the
> “business” people.
>
> I read that as Project Manager as well. I think when there are many issues
> in a project, it is often useful that the teams working on a project also
> have a Project Manager that helps the team to remove obstacles (this is, I
> think the main role of great Project Manager). This is the case, where
> several companies have whole teams dedicated to improve the OSS project.
> The developers still act as sole contributors on the OSS project, but they
> are paid by another organisation to do so and the Project Manager is there
> to make sure the teams work well together as well as individuals. We have
> some great example of that in our company where we have teams of
> contributors (also committers and PMCs) working on Apache Airflow and
> Apache Beam projects (among others) and there are PMs for those projects.
> What's more - those PMs are not there to provide "Business direction" but
> to make people working "well" together and there are some good example of
> people like that who learned how to do it in the
>  open-source cases. Quite recently at the Airflow Summit, our PM Karolina
> - gave (together with our CTO) great talk about it and explained the
> challenges and benefits of having a PM in such team:
> https://www.youtube.com/watch?v=KIEMEYM2PEs&list=PLGudixcDaxY3RGLSlWoN_cEEXhIT1OPmj&index=37
> . I can heartily recommend the talk to everyone who is interested in the
> subject!
>
> What's more - if you have great PMs who are really part of the team, they
> are super happy to contribute to the whole OSS project - and being able to
> help with the teamwork (for example by organixing issues and helping with
> tracking the progress) might be a huge help for both - the teams and the
> project. I think we are really blessed by having such people in our
> company, but I think there are more people like that.
>
> > The key questions are whether a PM can participate in the community
> (which means being active on the dev list), make contributions of value to
> the project (‘earn merit’), and can put aside their professional
> affiliation and act solely in the interests of the project. This is
> precisely what we require committers to do.
>
> Yes. It's possible and I think it's the same for different people.
> Actually this statement makes me quit

Re: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc1

2020-08-17 Thread Sheng Zha 
Hi Justin,

Since the blocking issue has been resolved, would you mind changing your vote? 
Thanks.

Regards,
Sheng

On 2020/07/26 01:27:39, Justin Mclean  wrote: 
> Hi,
> 
> -1 (binding) as this release contains code that hasn’t gone though IP 
> clearance (mshadow). 
> 
> I checked:
> - incubating in name
> - disclaimer exists
> - LICENSE and NOTICE have improved but I did not do an exhaustive check 
> -  No unexpected binary file
> - ASF files have ASF headers
> - unable to compile from source
> 
> It also seems that this code may have been released before the PPMC/IPMC vote 
> is over see [1][2][3][4] There are also branding and trademark issue with 
> this site [5] This is in addition to the issues previously noted with 
> releases, branding and trademarks.[6]
> 
> Thanks,
> Justin
> 
> 
> 1. https://sourceforge.net/projects/apache-mxnet.mirror/
> 2. 
> https://repo.gradle.org/gradle/simple/repo/ai/djl/mxnet/mxnet-native-mkl/1.7.0-b/
> 3. https://mvnrepository.com/artifact/ai.djl.mxnet
> 4. 
> https://aur.archlinux.org/packages/?O=0&SeB=nd&K=mxnet&SB=v&SO=d&PP=50&do_Search=Go
> 5. https://djl.ai
> 6. https://jira.apache.org/jira/browse/INCUBATOR-253
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org