Catching up on some old e-mail. On Wed, 15 Apr 2026, Don Marti wrote:
Even if some "AI" will eventually be able to make the QA and patching process faster, there is still a big window of opportunity where security issues can be discovered much faster than fixes can be coded, tested, and deployed.
Eventually, the answer will be to use AI bug-finders during development instead of after. In the mean time, I suspect the thing to do is to select a low-level bug, i.e. a bug that has no bug below it in the call DAG, and fix it. Rinse and repeat. Recursion would convert the DAG into a digraph with cycles. Potentially once could have two bugs "below" each other. If a module is allowed to fail, then the fastest fix might be to just test for the problem situation and, if necessary, return failure. -- Michael [email protected] "SCSI is NOT magic. There are *fundamental technical reasons* why it is necessary to sacrifice a young goat to your SCSI chain now and then." -- John Woods -- _______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
