Hi,

I agree with most of this. Writing down what we learn and putting it into 
shared tooling is what the Policy MCP and the Magpie release skill are for, and 
Paul's examples show it works. If a miss comes from a gap in the tools or docs, 
we should fix it once for everyone.

Where I disagree is "if you can articulate it, it can be automated". The rule 
is easy to articulate: know where everything in the release came from and under 
what licence. Applying it needs information that isn't in the release.

- A bundled dependency declares a licence, but that declaration can be wrong, 
dual-licensed as OR or AND, changed between versions, or only cover part of 
what's bundled. Paul's jQuery Treeview example is one of these.

- What NOTICE needs depends on what the upstream NOTICE files say and what's 
actually been copied, not on whether a NOTICE file exists.

- A file copied from a third-party project with an ASF header added passes RAT 
and every header check. Nothing in the file tells you it came from somewhere 
else. You find it because someone recognises it, searches for it, or asks where 
it came from.

This is also already written down. Every release vote on this list records what 
was checked and what was found, and we've analysed about 1,600 of those vote 
threads from 2015 to 2025 [1]. Checklists and automation removed mechanical 
problems like bundled binaries, bad signatures, and checksum mismatches. What's 
left in most -1 votes now are legal and provenance issues, each in a different 
file in a different project, and those still need a person. Tools find more of 
them than they used to, and I'm all for that, but they usually flag things for 
someone to look at - they don't give a pass.

Kind regards,
Justin

1. 
https://cwiki.apache.org/confluence/spaces/INCUBATOR/pages/393677685/Release+Vote+Insights

Reply via email to