sbp commented on issue #851: URL: https://github.com/apache/tooling-trusted-releases/issues/851#issuecomment-4407809423
In this proposal, `blocker` and `exception` are not renamed, `failure` usually becomes `concern`, and the one `warning` that we still have becomes `suggestion`. Some of the checks should be reclassified instead, not just renamed: | Label | Current | Description | Proposed | |---|:---:|---|:---:| | Compare Source Trees | `failure` | Clone or rsync or comparison tooling failed | `exception` (needs to be split) | | Hashing Check | `failure` | Missing referenced artifact | `blocker` (needs to be split) | | License Files | `failure` | Invalid `LICENSE` text | `blocker` (`NOTICE` goes to `concern`, needs to be split) | | License Files | `failure` | Cache or extracted archive unavailable | `exception` | | Paths Check Errors | `failure` | `.sha1`, `.sha`, discouraged or odd metadata suffix | `suggestion` | | Rat Check | `failure` | RAT process or JAR or Java or XML failure | `exception` | | Signature Check | `failure` | Verifying key lacks ASF UID | `blocker` | | Targz Structure | `failure` | Root mismatch, multiple or no roots, npm package name mismatch | `suggestion` | | Targz/Zipformat Structure | `failure` | Extracted archive tree unavailable | `exception` | | Zipformat Structure | `failure` | Root mismatch, root files, multiple or no roots, npm package name mismatch | `suggestion` | Some other notes: * There might be a bug in `KEYS` where it can produce two types. * For hashing, a malformed checksum file deserves `blocker`, not `exception`. * We might be able to remove the RAT `warning` entirely. It's not clear whether it's even active. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
