> Thank you @saudet. You can take a look at > https://infra.apache.org/publishing-maven-artifacts.html for more information > on the Apache Software Foundation (ASF) maven artifact publishing process. > Summary: Release candidate artifacts are pushed to a staging area and can be > promoted after the release vote passed.
Thanks for the links! I've been publishing to the Maven Central Repository, I know how that works. > One thing to note is that ASF policies do not allow publishing unreleased > (nightly) artifacts to the general public. Those should be placed at special > location and only used by interested community members. You can take a look > at http://www.apache.org/legal/release-policy.html#publication and this FAQ > entry http://www.apache.org/legal/release-policy.html#host-rc > Do you have any suggestion how to best handle it with your Github Actions > script / Maven? It doesn't sound to me like they forbid publishing snapshots, just that it shouldn't be documented, which is weird, but whatever. It should be alright to deploy snapshots and keep it a "secret", no? They say we "should" do this and that, but if none of their services offers support for Maven artifacts, I suppose this means we can use something else, right? > As `libgfortran` has changed their ABI a few times over the years, you will > need to include `libgfortran.so` in the `jar` (which we can distribute under > AL2 License thanks to the [GCC Runtime Library > Exception](https://www.gnu.org/licenses/gcc-exception-3.1.en.html)). However, > you must not include `libquadmath.so` (dependency of `libgfortran.so`) as it > is GPL licensed. Yes, that's not a problem. However, if we don't have `libquadmath.so`, `libgfortran.so` isn't going to load, so is it still useful? > For the gpu version `mxnet-2.0-20201222.141246-19-linux-x86_64-gpu.jar`, > would it make sense to use `cu110` instead of `gpu` if built with cuda 11.0 > etc? I guess? :) In any case, that's not a problem either. However, it's becoming increasingly irrelevant to try to support multiple versions of CUDA given their accelerating release cycle. -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-mxnet/issues/17783#issuecomment-751142493
