For an MRE request or claim, it is the requester who has to provide evidence that the package meets the criteria defined in the SRU documentation you linked. Such an SRU would then a) make that claim, and then b) list the evidence to back it up, including, but not limited to: - upstream release notes - statement that there is no known backwards incompatible change or another potential source of regression (some upstreams highlight these quite well, when they exist) - what testing has been done by upstream (link to upstream test results for that release perhaps) - what testing will be done in the SRU (build-time tests, autopkgtests, and/or manual tests foo and bar)
There have been MREs that were once granted, but while inspecting the upstream release notes for a particular release, backwards incompatible changes were found (bind9 comes to mind). How does that sound to you? And thanks for bringing this up, and working in mariadb! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2086527 Title: New upstream microreleases: MariaDB 11.4.4 et al To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb/+bug/2086527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
