potiuk opened a new issue, #60540: URL: https://github.com/apache/airflow/issues/60540
We are curently not verifying our NOTICE filles in our generated packages for content. while those files are there it might be that the NOTICE files are wrong (what does not help is that due to monorepo approach and having independent subproject, the NOTICE files come from different places in the repo. We want to verify it during our verification procedures - all those that are in `dev/README_RELEASE*` and add an extra step of verification for content: * whether required ASF notice is there (in generated artifacts - not only in sources) * whether the (C) end range year is current (2026 today) * 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) Note. that **some** of those NOTICE files are different in different distributions - for example fab provider NOTICE contains also Flask App Builder notice because we vendored-in part of the Flask App Builder in our code. So whatever we come up with as "syncing" solution has to deal with that. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
