In this SRU the autopkgtests were already green, but release readiness stayed blocked because pending-sru was still consuming verification tags that had not moved to done.
For the actual release decision, is pending-sru intended to be the authoritative machine-readable closure over package/version, autopkgtests, manual verification and aging, or do SRU reviewers still have to reconstruct readiness across Launchpad, tags, queues/excuses and comments? If a read-only verifier returned a bounded READY | BLOCKED | STALE | UNKNOWN result bound to the exact source package/version/series plus the evidence references, would that remove review work, or would it mostly duplicate native SRU state that should be improved instead? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2120204 Title: [SRU] MariaDB 11.4.8, 10.11.14, 10.6.23 in all maintained Ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb/+bug/2120204/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
