Re: [I] Preparing v1.1.0-incubating release [texera]

["bobbai00 (via GitHub)" <gi...@apache.org>]

bobbai00 commented on issue #4080:
URL: https://github.com/apache/texera/issues/4080#issuecomment-4262516458

   I would like to summarize the current roadmap of making the release compliance in terms of license. There are in total 3 steps:
   
   ## Step 1 — Use compliant libraries in Texera itself
   
   Every direct dependency declared in Texera's build files must be Category A or Category B.
   
   The problematic package is `mysql-connector-java`, which is GPLv2 and
   is currently declared as a dependency of the MySQL source operator. 
   
   This is tracked by #4393 
   
   ## Step 2 — Ensure proper licensing for Texera's own jars
   
   Texera produces 12 jars. Each jar's `META-INF/LICENSE` must describe
   what is inside that specific jar, not what is in the full source tree. 
   
   This is tracked by #4394.
   
   ## Step 3 — Make release artifacts compliant
   
   Texera releases Docker images as convenience binaries. A Docker image
   bundles roughly 450 third-party dependency jars alongside Texera's own
   jars, plus system packages from the base OS layer. Per ASF policy, the
   `LICENSE` file shipped inside each Docker image must describe everything
   it contains, not just Texera's own jars. 
   
   This is tracked by #4396
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org