You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "xchwan (via GitHub)" <gi...@apache.org> on 2026/05/19 08:49:40 UTC

Re: [I] Add verification steps for NOTICE files to our release processes [airflow]

xchwan commented on issue #60540:
URL: https://github.com/apache/airflow/issues/60540#issuecomment-4486028780

   @potiuk  Excuse me, I have confuse your commons.
   issue said:
   Possibly we could explore using symbolic links instead of copying the NOTICE files in 200+ incarnation - or "maybe add a way to keep them all in sync automatically (prek hook)". 
   And then
   the notice file never changes - it can diverge. There is no point in syncing those, dfferent story with licence headers that are added to files and they are modified independently. 
   So if I understand correctly, since the NOTICE files rarely change and divergence is acceptable, we don’t need to implement the symbolic link or auto-sync/prek-hook approach anymore. Is that correct?
   


-- 
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: commits-unsubscribe@airflow.apache.org

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