Comment 12 for bug 1761674

@IBM: Since this is a Stable Release Update Update (SRU) situation the SRU process as described here applies - especially the section about verification:
https://wiki.ubuntu.com/StableReleaseUpdates#Verification

For more details on the verification itself there is a separate Performing SRU Verificaton page:
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification

key points in a case like this are (in my opinion):
- Verification must be done in a software environment as close as is feasible to that which will exist after the package is copied to *-updates. Generally this will be with a system that is up to date from *-release, *-security, and *-updates, but not with other packages from *-proposed (except other packages built from the affected source package - they must be updated if generally installed) or *-backports.
* Verification feedback from bug reporters and subscribers is greatly appreciated, too, especially if the update is hardware specific. In this case we consider an update as verified if it has at least two positive, no negative testimonials in the bug report, and the verification team just checks whether the new version still works for the main use cases (to check for major regressions).
- Ensure all critical and high importance bugs are verified in a timely manner.
(See comment #10 usually 5 working days.)

Hence it's not only about the verification of a certain patch itself, but also about making sure to not introduce any regressions.

But I recommend a full reading of the above links.