2 phased patch roll-out and need to restrict phase 2 patches to mirror earlier phase 1 patching

Latest response

I am running Satellite 5.8. We have a need to roll out patches on the Test servers 10 days before pushing them to production.
I am trying to find a way to lock in the patches that will get pushed to production to be the same as the ones that were installed on the Test boxes.
My concern is that in the time between the Phase 1 (Test) and the Phase 2 (Prod) roll-out some new patches/errata could be released. I don't want to include those in the Production patching.
Is there any way to "approve" patches for installation or to lock in a set of patches for future installation?

Responses