Comment 16 for bug 1935082

Hi,
now everything is complete except the QA via testing.
We have amended the MIR rules to better clarify as this is one of the cases that is hard to autopkgtest/build-test but some QA should happen still.

The new rule is:
"The package must include a non-trivial test suite, and if there is no obvious reason why it cannot work during build (e.g. it needs root privileges or network access), it should be run during package build, and a failing test suite should fail the build. The package should, but is not required to, also contain non-trivial autopkgtest(s). If no build tests nor autopkgtests are included, and/or if the package requires specific hardware to perform testing, the subscribed team must provide a written test plan in a comment to the MIR bug, and commit to running that test either at each upload of the package or at least once each release cycle. In the comment to the MIR bug, please link to the codebase of these tests (scripts or doc of manual steps) and attach a full log of these test runs. This is meant to assess their validity (e.g. not just superficial)"

Therefore I'd ask to add to the bug:
- the test plan / code / guide (whatever you have of that)
- logs of a successful run thereof.
- the written commitment to do (regularly)