Thank you all for the valuable feedback, and apologies for dropping
the ball on this. I should have been more diligent despite the WIP
disclaimer, I did not fully understand the implications.
Since those artifacts have already been published to Maven Central and
cannot be removed, what would be th
Hello,
I have addressed the issues mentioned in the previous email:
1. Fixed the Keys link address.
2. Changed the artifact download address to match the closer.lua style.
3. The docker latest image has been rolled back to the old version.
I look forward to your further feedback.
Best regards,
Good point Justin about the importance of checking for problematic licenses.
That fat jar is 600Mb and includes the kitchen sink in terms of classes.
One set of classes is from OpenJDK JOL and this is GPL-2.0 licensed.
This seems like a big problem to me, especially because the artifact has
alrea
Hi,
> Thanks for sharing LEGAL-469 Justin. I have seen it at some point but
> as time passed I forgot its existence.
>
> The DISCLAIMER-WIP contains the following snippet:
> Some of the incubating project’s releases may not be fully compliant
> with ASF policy. For example, releases may have inco
Thanks for sharing LEGAL-469 Justin. I have seen it at some point but
as time passed I forgot its existence.
The DISCLAIMER-WIP contains the following snippet:
Some of the incubating project’s releases may not be fully compliant
with ASF policy. For example, releases may have incomplete or
un-revi
Hi all,
The Apache Fury(incubating) community is pleased to announce
that Apache Fury(incubating) 0.7.1 has been released!
Apache Fury(incubating) - A blazingly fast multi-language serialization
framework powered by JIT and zero-copy.
The release notes are available here:
https://github.com/apac
