Hi, As Adar recently found, both in Kudu 1.10.0 and Kudu 1.11.0 (due to be announced today) the kudu-binary artifact contains libnuma library which is under LGPL v.2.1, but it's against the ASF 3rd-party license policy: https://www.apache.org/legal/resolved.html#category-x
See https://issues.apache.org/jira/browse/KUDU-2990 for details. Apart from the technical discussion on how to resolve that, there are few process-related questions like: 1. How to address the issue in Kudu 1.11.0, which is de facto already out of the door? 2. Should we address the issue in upcoming Kudu 1.12.0 release (about 3-4 month in the future) or implement the solution and release it with Kudu 1.11.1 ASAP? 3. If choosing the latter option from the previous item, should the announcement of the new Kudu 1.11.0 release be postponed/muted, so we announce only when Kudu 1.11.1 is out with KUDU-2990 addressed? Given the timing and the fact that Kudu 1.11.0 artifacts are already published, I think one of the possible paths forward is to proceed with the announcement of Kudu 1.11.0 release as planned, but add an item about KUDU-2990 into the 'known issues' document, so it will be available at the Apache Kudu website: https://kudu.apache.org/docs/known_issues.html#_other_known_issues What do you think? Your feedback is appreciated. Best regards, Alexey
