[ 
https://issues.apache.org/jira/browse/YUNIKORN-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17567042#comment-17567042
 ] 

Wilfred Spiegelenburg commented on YUNIKORN-1256:
-------------------------------------------------

The LICENSE files in the release repo are using a different line-ending. If we 
need to merge and compare LICENSE files for a release then this will cause 
issues:
{code:java}
../yunikorn-web/LICENSE: ASCII text
../yunikorn-k8shim/LICENSE: ASCII text
../yunikorn-k8shim/yunikorn-release/LICENSE: ASCII text, with CRLF line 
terminators
../yunikorn-k8shim/yunikorn-release/release-top-level-artifacts/LICENSE: ASCII 
text, with CRLF line terminators
../yunikorn-release/LICENSE: ASCII text, with CRLF line terminators
../yunikorn-release/release-top-level-artifacts/LICENSE: ASCII text, with CRLF 
line terminators
../yunikorn-scheduler-interface/LICENSE: ASCII text {code}
Replace the two in the release repo with just plain ASCII text versions

> License issue with deployments examples
> ---------------------------------------
>
>                 Key: YUNIKORN-1256
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1256
>             Project: Apache YuniKorn
>          Issue Type: Task
>          Components: community
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Wilfred Spiegelenburg
>            Priority: Major
>
> License of tfjb files should be mentioned as 3rd party as they are copyright 
> by the Tensorflow authors.
> Files impacted are part of the k8shim repo:
>  * deployments/examples/tfjob/dist_mnist.py
>  * deployments/examples/tfjob/Dockerfile
> Update to LICENSE file required for the k8shim repo and the change needs to 
> be added to the release LICENSE file also or we need to pick that up from the 
> k8shim repo during the release build...



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to